When issuing a SchemaUpdate, it does not respect the schema given by the mappings. If the schema is something other than the logged in schema, SchemaUpdate doesn't recognize that indexes are created/does not create the indexes in the correct schema.
Possibly related to this hibernate bug: https://hibernate.onjira.com/browse/HHH-5918
Possibly also related to a bug where sequences were not recognized for different schema for Oracle.
This might only apply to different dialects (tried on Oracle with the .NET provider).
Major
When issuing a SchemaUpdate, it does not respect the schema given by the mappings. If the schema is something other than the logged in schema, SchemaUpdate doesn't recognize that indexes are created/does not create the indexes in the correct schema.
Possibly related to this hibernate bug: https://hibernate.onjira.com/browse/HHH-5918
Possibly also related to a bug where sequences were not recognized for different schema for Oracle.
This might only apply to different dialects (tried on Oracle with the .NET provider).