[
https://issues.apache.org/jira/browse/OPENJPA-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898305#action_12898305
]
Jeremy Bauer commented on OPENJPA-735:
--------------------------------------
Yep. Looks like a bug. Please hold off on committing the patch. IIRC, The
default delimitedCase for MySQL on Windows is SCHEMA_CASE_LOWER and that works
OK. There may just be a simple bug in the normalizer logic preventing db's
with SCHEMA_CASE_UPPER from working properly. I'd rather not introduce the
dictionary into DBIdentifier unless absolutely necessary. I'll take a look and
post what I find...
> Provide dictionary support for SolidDB
> --------------------------------------
>
> Key: OPENJPA-735
> URL: https://issues.apache.org/jira/browse/OPENJPA-735
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 1.3.0
> Reporter: Kevin Sutter
> Assignee: Fay Wang
> Attachments: OPENJPA-735.patch
>
>
> SolidDB (http://www-01.ibm.com/software/data/soliddb/) is an in-memory
> relational database from IBM. Supposedly, it's JDBC compliant and, thus,
> shouldn't be a major effort to create a dictionary.
> Besides drumming up JPA support for existing SolidDB customers, this database
> may also prove fruitful from our own junit regression testing. Using an
> in-memory database may help speed up our junit bucket over the current usage
> of Derby.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
