openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fay Wang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-735) Provide dictionary support for SolidDB
Date Thu, 12 Aug 2010 22:20:15 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Fay Wang updated OPENJPA-735:
-----------------------------

    Attachment: OPENJPA-735.patch

The test on SolidDB expose a bug in Delimiter identifier. For SolidDB, the delimitedCase is
SCHEMA_CASE_UPPER. However, the static method DBIdentifier.toUpper(DBIdentifier) assumes the
case is preserved and does not convert the column name to uppercase based on the back-end,
resulting in extra column being added to the table.

> 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.


Mime
View raw message