[jira] Commented: (OPENJPA-483) config for openjpa.jdbc.Schemas not applied to SQL (HSQL)

["David Beer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENJPA-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770963#action_12770963 ] 

David Beer commented on OPENJPA-483:
------------------------------------

I am experiencing the same issue with openjpa 1.2.1

It seems that when you connect for the first time that openjpa seems to ignore the schema property.  openjpa then proceeds to create the tables in the default schema PUBLIC.

After some discussion on the mailing list, Kevin Sutter recons this may be to do with the DBDictionary not having the righ methods to detect the openjpa schema property.


> config for openjpa.jdbc.Schemas not applied to SQL (HSQL)
> ---------------------------------------------------------
>
>                 Key: OPENJPA-483
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-483
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>         Environment: Java JDK 1.5.0_12, Linux, Hypersonic DB
>            Reporter: Adam Hardy
>         Attachments: schemabug.zip, schemabug2.zip
>
>
> OpenJPA should be able to see and access schemas but doesn't. 
> I configured this with openjpa.jdbc.Schema=DEV (my schema name) 
> I also tried putting the schema name everywhere possible in the metadata, i.e. in the <schema>DEV</schema> tags and in table tags, and in:
>   <persistence-unit-metadata>
>     <xml-mapping-metadata-complete />
>     <persistence-unit-defaults>
>       <schema>DEV</schema>
>     </persistence-unit-defaults>
>   </persistence-unit-metadata>
> I will include a zipped up test project illustrating the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.