[jboss-jira] [JBoss JIRA] (WFLY-9739) JPA / Hibernate: There is already an object named 'x' in the database

[Scott Marlow (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13524891#comment-13524891 ] 

Scott Marlow commented on WFLY-9739:
------------------------------------

Hi, does the database contain a table called "ANIMAL"?  Or perhaps "animal"?  I'm not sure if there is a bug or not in Hibernate but it sounds like Hibernate may be getting a list of tables from JDBC DatabaseMetaData that contains "Animal" with a different case than expected.  

We will soon reject this issue, since there is no bug to fix in the WildFly project (as far as I can tell).  If there is a Hibernate bug, that can be reported via [https://hibernate.atlassian.net/browse/HHH].  

If you want to let us know the exact case of the ANIMAL table name, that could be helpful.



> JPA / Hibernate: There is already an object named 'x' in the database
> ---------------------------------------------------------------------
>
>                 Key: WFLY-9739
>                 URL: https://issues.jboss.org/browse/WFLY-9739
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 11.0.0.Final
>         Environment: Windows 10 64 bits / Windows Server 2012 R2 64 bits
> Java version: 1.8.0_151
> SQL Server 2014
>            Reporter: Eric SantAnna
>            Assignee: Scott Marlow
>         Attachments: sqljdbc4.jar, wildfly11-migration.zip
>
>
> I'm getting an Exception as a warning in the server.log when a database object already exists an my persistence.xml has the property "hibernate.hbm2ddl.auto" set to "update".
> This doesn't happen in my tests with 10.1.0.Final.
> Appearently, despite these Exceptions, all my applications are running ok.
> I saw this behaviour while I was migrating my application from JBoss 7.1.1.Final to Wildfly. I'm deciding between Wildfly 10.1 and 11.
> This behaviour isn't good cause, I'm flooding the logs and it doesn't seem reliable for my manager.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)