Oracle Sequence mappings ignored

Just tried Mysql - forget that idea, I just realised Mysql doesn't have named sequences. What else has them? Postgres?

Any ideas where the problem might be? I currently cannot deploy to production so my only other option is to downgrade all my stuff to 1.1 - which is going to create lots of pain later when I have to upgrade again. If someone can point me in the direction of the fix - I am happy to submit a patch.

I'm also happy to pay a bounty if someone out there can fix it quick.

Steve,

Try explicitly assigning a sequence generator for this class. It's unclear whether the native generator actually accepts a sequence name or not.

You mean just using id generator: 'sequence'?

I tried this with same effect.

The only reason we were using native is that it let's the code work seamlessly on mysql too.

I've traced through and can't see anything obvious.

Does it still happen when you don't have the default mapping there?

Yes - I originally had it without default mapping, just added that as it was then easier to change sequence mode on global level. It's a pain that this only happens on Oracle - so hard to debug without having it installed. I'm going to try it with Postgres - I think they have named sequences.

Is this still targeted for 1.2.2? If not - I think I am going to have to bite the bullet and downgrade everything to 1.1 tomorrow

I'll look and see if it's straightforward to implement but in the meantime you can create a custom dialect. See this thread for a Postgres example: http://n4.nabble.com/One-hibernate-sequence-is-used-for-all-Postgres-tables-td1351722.html

The Oracle version is nearly identical; I originally wrote it for Oracle but converted to Postgres for that email. You'll need to subclass whatever Oracle dialect you're using now instead of PostgreSQLDialect, and change the table-to-sequence naming logic.

Thanks Burt - yes I had considered that before as it gives me much more flexibility over foreign keys and other things. If it's just subclassing I might give that a go today.

Just tried Burt's workaround and it works a treat, might actually use this solution long term anyway as we have quite a few other things we would like to customize to avoid a lot of the mapping we have to do in our domain objects to fit our DB naming standard.

btw. If anyone needs to recreate the original problem but they don't have Oracle - you don't need to actually run against Oracle to recreate. Just get the Oracle JDBC driver and run a schema-export.

Burt since you volunteered to look into the problem I'm assigning to you

Since there is a workaround feel free to downgrade to a minor issue

Closing as Won't Fix since there's not much that can be done on the Grails side. The issue is in the Hibernate Dialect and it depends on the version of Oracle you're using so the custom dialect approach referenced in the comments is the workaround.