[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-371) MySQL tablenames incorrect if schema is specified (mismatch between create table and check table)

Tue Feb 13 20:27:33 EST 2007

     [ http://jira.jboss.com/jira/browse/EJBTHREE-371?page=all ]

Emmanuel Bernard resolved EJBTHREE-371.
---------------------------------------

    Resolution: Won't Fix
      Assignee: Emmanuel Bernard

Max is right

> MySQL tablenames incorrect if schema is specified (mismatch between create table and check table)
> -------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-371
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-371
>             Project: EJB 3.0
>          Issue Type: Bug
>         Environment: JBoss 4.0.3
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
> Linux Mandriva 2006 (Linux desktop 2.6.12-12mdksmp #1 SMP Fri Sep 9 17:43:23 CEST 2005 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz unknown GNU/Linux)
>            Reporter: Ramon Casha
>         Assigned To: Emmanuel Bernard
>
> I'm using entity EJB3s with JBoss4.0.3 and MySQL, and I'm specifying the schema in the EJBs via @Table(schema="xxx").
> Although the app works fine, each time I deploy it again or restart jboss it tries to check whether the tables exist, but it uses different names for the tables and does not find them, then tries to re-create them and finds they already exist and gives errors.
> This seems to be caused because the tables are created as SCHEMA_TABLENAME under mysql, but when jboss tries to check whether the tables exist, it searches for them as TABLENAME.
> Since I have the hibernate.hbm2ddl.auto property set to update, if I change an EJB property it doesn't find the table but doesn't manage to create it anew (since it already exists) so essentially it doesn't update the table definition.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira