[CAY-2024] check for AUTO_PK_TABLE should respect current schema

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: Undefined future
• Assignee: Andrus Adamchik
• Reporter: Tore Halset
• Created: 04/Sep/15 07:17
• Updated: 27/Sep/15 10:24

Description

The create/delete/insert/update of AUTO_PK_TABLE should respect the schema in the model. There are other older issues covering this.

When a schema is not defined in the model, the create/delete/insert/update of AUTO_PK_TABLE in the default schema works fine. However, the check for AUTO_PK_TABLE in JdbcPkGenerator#autoPkTableExists are currently looking in all schemas. But it should only check in the current schema.

I discovered this when trying to run several instances of one cayenne application on different schemas in the same database.

In java 7, they added java.sql.Connection#getSchema that should return the current schema. However, cayenne 4 seem to be at java 6. To make getSchema work also jdbc drivers and connection pools must be updated. Do we need to create our own getSchema(Connection), or do we already have it, or are cayenne 4 going to be java 7+?