[hibernate-issues] [JIRA] (HHH-11455) When "schema" attribute is set explicitly, tables are identified by schema name even when underlying database doesn't support schemas

Chris Cranford (JIRA) jira at hibernate.atlassian.net
Sun Feb 26 23:42:40 EST 2017

Previous message: [hibernate-issues] [JIRA] (HHH-11455) When "schema" attribute is set explicitly, tables are identified by schema name even when underlying database doesn't support schemas
Next message: [hibernate-issues] [JIRA] (HHH-11521) Hibernate is not creating unique constraint specified in @JoinTable
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20170226/735c0c60/attachment.html

Previous message: [hibernate-issues] [JIRA] (HHH-11455) When "schema" attribute is set explicitly, tables are identified by schema name even when underlying database doesn't support schemas
Next message: [hibernate-issues] [JIRA] (HHH-11521) Hibernate is not creating unique constraint specified in @JoinTable
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the hibernate-issues mailing list