[
https://issues.apache.org/jira/browse/OPENJPA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839740#action_12839740
]
Jeremy Bauer commented on OPENJPA-1537:
---------------------------------------
Hi Laird. Identifiers aren't necessarily equal if delimiters are removed. It
depends on how they are stored in the DB (mixed, upper, or lower case). With
DB2, for example, "informix" != informix, since the delimited name will
actually be stored in lower case (mixed, actually) and will require delimiters
in the SQL to indicate the proper identifier. The good news is that the
DBIdentifier code is reasonably flexible/configurable so my hope is that these
Informix issues can be fixed by flipping a few switches.
If you could supply small test cases that would really help. I just about have
my informix system back up and running and will be looking at these issues
shortly.
> SchemaGenerator interacts poorly with InformixDictionary (regression from
> 1.2.2)
> --------------------------------------------------------------------------------
>
> Key: OPENJPA-1537
> URL: https://issues.apache.org/jira/browse/OPENJPA-1537
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc, sql
> Affects Versions: 2.0.0-beta
> Reporter: Laird Nelson
> Assignee: Jeremy Bauer
>
> If you ask the SchemaGenerator to generate schemas like this:
> sg.generateSchemas(new DBIdentifier[] {
> DBIdentifier.newTable("informix.foobar_table") });
> ...then identifiers within the SchemaGenerator--whether of tables, primary
> keys, foreign keys, what have you--contain quotes.
> Quoted identifiers are then subsequently not trimmed, because the space
> padding occurs inside the quotes.
> This means the SchemaGroup will, for example, never find the Schema
> identified by the user at generateSchemas()-call-time. Consequently no
> foreign keys will be generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
