openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Bauer (JIRA)" <>
Subject [jira] Commented: (OPENJPA-735) Provide dictionary support for SolidDB
Date Tue, 17 Aug 2010 02:09:15 GMT


Jeremy Bauer commented on OPENJPA-735:

I committed a simple fix under rev 986166 that allows for case insensitive delimited compares
for DB's that do not support mixed case delimited identifiers. This prevents two equivalent
column names from being added to the schema by the mapping tool - one from DB metadata, one
from entity metadata. Tested with SolidDB, Derby, MySQL, PostgreSQL, Oracle, & MSSQL 2008
and it looks good (so far).

> Provide dictionary support for SolidDB
> --------------------------------------
>                 Key: OPENJPA-735
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 1.3.0
>            Reporter: Kevin Sutter
>            Assignee: Fay Wang
>         Attachments: OPENJPA-735.patch
> 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.

View raw message