[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-1194) hibernate.hbm2ddl.auto=update works with multiple oracle schemas

Raoul Kaltenhäuser (JIRA) noreply at atlassian.com
Wed May 9 06:25:11 EDT 2012


    [ https://hibernate.onjira.com/browse/HBX-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46576#comment-46576 ] 

Raoul Kaltenhäuser commented on HBX-1194:
-----------------------------------------

This happens also with Postgres.
Even if hibernate.default_schema is set to a specific schema,
the update looks into every schema that is accessible by the given database user.
CREATE-DROP seems to respect the schema that is configured in hibernate.default_schema.


> hibernate.hbm2ddl.auto=update works with multiple oracle schemas
> ----------------------------------------------------------------
>
>                 Key: HBX-1194
>                 URL: https://hibernate.onjira.com/browse/HBX-1194
>             Project: Hibernate Tools
>          Issue Type: Bug
>         Environment: <org.hibernate.core.version>3.6.8.Final</org.hibernate.core.version>
> 		<org.hibernate.entitymanager.version>3.6.8.Final</org.hibernate.entitymanager.version>
> 		<org.hibernate.validator.version>4.0.2.GA</org.hibernate.validator.version>
>            Reporter: Vyacheslav
>
> if privileges are set hbm2ddl schema update searches for created tables in all db schemas which can be accessed, not only in current one. Don't create tables needed in current schema and fails to alter them.
> http://community.jboss.org/thread/175353?tstart=0
> info level log viewing says during schema update that:
>  
> table found: REALTY.DATA_EXCH_LOG
> table found: REALTY_NEW.FILES_AUD
> table found: SYSTEM.PROPERTIES_AUD
> table found: SYSTEM.REVISIONS
>  
> Script see different database schemas and creating AUD tables in one schema scanning others:
>  
> table found: REALTY.REF_RSR_ORDER_TYPES
> table found: REALTY_NEW.REF_RSR_ORDER_TYPES_AUD
>  
> After hbm2ddl cannot find tables created in other schemas:
>  
> Unsuccessful: alter table PROPERTIES_AUD add BASE_TYPE_ID number(10,0) not null
>  
> Current schema is REALTY_NEW
>  
> Very strange behaviour.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the hibernate-issues mailing list