I'd like to confirm another bug in the InformixDictionary that cropped up sometime between 1.2.2 and 2.0 beta.
If you ask the InformixDictionary to find a table's imported keys via its getImportedKeys() method ( http://openjpa.apache.org/builds/latest/docs/javadoc/org/apache/openjpa/jdbc/sql/DBDictionary.html#getImportedKeys%28java.sql.DatabaseMetaData,%20org.apache.openjpa.jdbc.identifier.DBIdentifier,%20org.apache.openjpa.jdbc.identifier.DBIdentifier,%20org.apache.openjpa.jdbc.identifier.DBIdentifier,%20java.sql.Connection,%20boolean%29), then each ForeignKey that comes back reports that its schema is, for example: "informix " instead of (as I'd expect): informix That is, the quotes and the space padding are part of each foreign key's getSchemaIdentifier() return value's getName() return value. This causes all sorts of problems downstream. Consequently, things like DBIdentifier.trimToNull() on such identifiers don't work--since the trailing quote is actually part of the identifier, the space padding is not trimmed. Consequently, the SchemaGenerator tool never reports there being any foreign keys for a table that actually has them, because its associated SchemaGroup cannot find any Schema with a DBIdentifier whose name is: "informix " ...when that SchemaGenerator has been asked to generate schemas from, for example, new DBIdentifier[] { DBIdentifier.newTable("informix.foobar_table") }. I am not sure where the best place is to make a fix. I will file a bug for this. I've discovered several bugs in the reverse mapping toolchain, and have mentioned them on this list, and have filed JIRAs for them, but haven't seen any activity on this list or on JIRA to indicate that they've been put in or sent to the right place. Is this the right list to report such issues? Thanks, Laird
