Andy Jefferson added a comment - 21/Sep/10 01:51 PM - edited

Andy Jefferson added a comment - 21/Sep/10 01:51 PM - edited I have no such problems in creating indexes with Oracle. A testcase please. Also changing this in DatabaseAdapter means it has to work for *all* databases. Does it ?

Giambattista Bloisi added a comment - 21/Sep/10 02:38 PM

Giambattista Bloisi added a comment - 21/Sep/10 02:38 PM I'm going to prepare a test case for this. The patch has been used against hsqldb, mysql, sybase, ms sql server, and oracle. Though only on oracle I'm using the dbschema property. In this case anyway I'm not observing a failure when creating indexes: I'm just observing that tables are created in the provided dbschema, while indexes are created into the default system schema.

Giambattista Bloisi added a comment - 21/Sep/10 05:02 PM

Giambattista Bloisi added a comment - 21/Sep/10 05:02 PM This is the same sample as NUCRDBMS-442. Index is correctly created but in the wrong schema. I checked that with the statement reported below (_myclass_PK was created in ITDB schema as requested, while myclass_index was created into SYSTEM default schema for system user). SQL> select index_name, OWNER from all_indexes where index_name like '%myclass%'; INDEX_NAME -------------------------------------------------------------------------------- OWNER -------------------------------------------------------------------------------- _myclass_PK ITDB myclass_index SYSTEM

Andy Jefferson added a comment - 21/Sep/10 06:06 PM

Andy Jefferson added a comment - 21/Sep/10 06:06 PM Reproduced with the provided test (i.e default schema for the user being different from that specified with the "Schema" persistence property), and fix applied. Thx