You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when an application is in Update's mode with Postgres, if a table with the same name exists in other schema, the table is not create in the schema of the application.
For example, an application uses a schema called "schemaa" with a table called "tablea",
"tablea" is well created in the "schemaa".
Another application is launched on the same database but with a different schema called "schemab" and with a table called "tablea".
Hibernate thinks that the table exists in the "schemab" but it only exists in "schemaa".So it does not create the table in the "schemab".
I think in update's mode, when hibernate check if the table exists, it does not specify the schema.
Hi all!
when an application is in Update's mode with Postgres, if a table with the same name exists in other schema, the table is not create in the schema of the application.
For example, an application uses a schema called "schemaa" with a table called "tablea",
"tablea" is well created in the "schemaa".
Another application is launched on the same database but with a different schema called "schemab" and with a table called "tablea".
Hibernate thinks that the table exists in the "schemab" but it only exists in "schemaa".So it does not create the table in the "schemab".
I think in update's mode, when hibernate check if the table exists, it does not specify the schema.
dataSource.url=jdbc:postgresql://myserver:5432/mydatabase?searchpath=myschema
dataSource.driverClassName=org.postgresql.Driver
hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect
hibernate.hbm2ddl.auto=update
driver postgres's version : 9.1-903.jdbc4
regards
Jean-Sébastien
The text was updated successfully, but these errors were encountered: