[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-238?page=co... ] Emmanuel Bernard commented on EJB-238: -------------------------------------- Older versions of MySQL did not support schema -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-238?page=co... ] Bryan Hunt commented on EJB-238: -------------------------------- I've debugged this a bit more using the latest MySQL and here is an update. If you specify a schema using @Table (schema = "my_schema") and your connection url does not use my_schema as the database ie: jdbc:mysql://localhost/test, there is an exception thrown inside hibernate that says you don't have create permission. The only way for this to work is if the schema matches the database ie: @Table(schema = "clients") jdbc:mysql://localhost/clients This becomes non-portable when you move to a database that supports schemas within a database such as DB2. In the case of DB2, the following works as expected: @Table(schema = "clients") jdbc:db2://localhost:50001/store_database -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira