[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5276) Table REVINFO created in the default schema even if the property is otherwise set

Lukasz Antoniak (JIRA) noreply at atlassian.com
Sat Apr 16 12:50:59 EDT 2011


    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42063#action_42063 ] 

Lukasz Antoniak commented on HHH-5276:
--------------------------------------

Pull request submitted: https://github.com/hibernate/hibernate-core/pull/67
Workaround: Create custom revision entity ({{@org.hibernate.envers.RevisionEntity}}) and specify different database schema with {{@javax.persistence.Table(schema="mydb_aud")}}. See documentation chapter 11.3. "??Changes to the revision entity??" (http://docs.jboss.org/hibernate/envers/3.6/reference/en-US/html_single/#migrations-revisionlog).

> Table REVINFO created in the default schema even if the property is otherwise set
> ---------------------------------------------------------------------------------
>
>                 Key: HHH-5276
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5276
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: envers
>    Affects Versions: 3.5.2
>         Environment: Hibernate 3.5.2
> Mysql (Ver 14.14 Distrib 5.1.37, for debian-linux-gnu (i486))
> mysql-connector version 5.1.12
> java version "1.6.0_0"
> OpenJDK Runtime Environment (IcedTea6 1.6.1) (6b16-1.6.1-3ubuntu3)
> OpenJDK Server VM (build 14.0-b16, mixed mode)
>            Reporter: Pascal-Eric Servais
>
> This issue was first related here : http://community.jboss.org/message/545287 but here is a copy.
> Partial configuration :
> [META-INF/persistence.xml]
>  
> <persistence version="2.0"
>   <persistence-unit name="party" transaction-type="RESOURCE_LOCAL">
>   ...
>   <properties>
>     <property name="hibernate.hbm2ddl.auto" value="update" />
>     <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" />
>     <property name="javax.persistence.jdbc.url" value="jdbc:mysql://localhost/MODEL?useUnicode=true&amp;characterEncoding=UTF-8" />
>     <property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.Driver" />
>     <property name="javax.persistence.jdbc.user" value="root" />
>     <property name="javax.persistence.jdbc.password" value="" />
>     ...
>     <property name="org.hibernate.envers.default_schema" value="AUDIT"/>
>   ...
>   <!-- All EventListeners Are Defined -->
> </persistence-unit>
>  
> [META-INF/orm.xml]
>  
> <entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_2_0.xsd"
>   version="2.0">
>   <access>FIELD</access>
>   <entity class="com.company.model.Party">
>     <table name="PARTY" schema="MODEL" />
>     ...
>    </entity>
>    ...
> </entity-mappings>
>  
> As expected, the PARTY table is created into the MODEL schema and the audit table PARTY_AUD is created into the AUDIT schema. But the REVINFO table is created into the MODEL schema. According to the property "org.hibernate.envers.default_schema", it should be created into the AUDIT 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list