[jira] Created: (OPENJPA-115) Bottleneck(s) with using OpenJPA in a Container-managed environment

Bottleneck(s) with using OpenJPA in a Container-managed environment --- Key: OPENJPA-115 URL: https://issues.apache.org/jira/browse/OPENJPA-115 Project: OpenJPA Issue Type: Bug

[jira] Commented: (OPENJPA-115) Bottleneck(s) with using OpenJPA in a Container-managed environment

[ https://issues.apache.org/jira/browse/OPENJPA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468408 ] Craig Russell commented on OPENJPA-115: --- Kevin opined: Within a Container-managed environment, the Container

[jira] Commented: (OPENJPA-115) Bottleneck(s) with using OpenJPA in a Container-managed environment

[ https://issues.apache.org/jira/browse/OPENJPA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468429 ] Patrick Linskey commented on OPENJPA-115: - Recall that we do have a 1.4-compatible concurrent collection at

[jira] Created: (OPENJPA-116) EntityManager.getDelegate should throw an IllegalStateException

EntityManager.getDelegate should throw an IllegalStateException Key: OPENJPA-116 URL: https://issues.apache.org/jira/browse/OPENJPA-116 Project: OpenJPA Issue Type: Bug

SchemaCase setting in org.apache.openjpa.jdbc.sql.SQLServerDictionary

Hi folks, I met a problem when running OpenJPA on a case-sensitive MS SQL Server database. Schematool reported below error. Exception in thread main com.microsoft.sqlserver.jdbc.SQLServerException: The database name component of the object qualifier must be the name of the current

Re: SchemaCase setting in org.apache.openjpa.jdbc.sql.SQLServerDictionary

William- I didn't know it was an option to have a SQL Server instance be case- sensitive. Anyway, you can just specify this behavior by setting the following property: openjpa.jdbc.DBDictionary: schemaCase=preserve Let us know if the problem still occurs after you try this setting.