openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laird Nelson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1537) SchemaGenerator interacts poorly with InformixDictionary (regression from 1.2.2)
Date Thu, 25 Feb 2010 18:05:28 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838449#action_12838449
] 

Laird Nelson commented on OPENJPA-1537:
---------------------------------------

Interestingly, the workaround I describe--brute force removing the delimiters, essentially,
by saying the DBDictionary doesn't support them, and by supplying a DBIdentifierUtil that
trims incoming names in its fromDBName() method--doesn't work for names that are, for example,
numbers.

I have some indices in my Informix database whose names are, e.g., 378_8804.

These show up in my XML schema files--after my workaround, which gets around most instances
of this bug--like this:

            <index name="&quot;378_8804&quot;" unique="true">

Note the &quot; bits, even though my DBDictionary is reporting that it does not support
delimited identifiers.

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


Mime
View raw message