On Oct 17, 2:40 pm, Will Gorman <[email protected]> wrote: > Are there changes that relate to automatically obtaining new sequence values > on insert for Oracle via JDBC?
Yes. The previous support was broken in the multithreaded case, as you weren't even guaranteed to use the same connection to get the sequence value as you used for the insert. > I have a plugin (https://gist.github.com/1293900) that executes a statement > in a > before_create hook to get the nextval from the sequence associated with the > dataset. When I use the current master branch, I get the following error > when that before_create hook runs: > > Sequel::DatabaseError: NativeException: java.sql.SQLException: ORA-02287: > sequence number not allowed here Full backtrace, code, and SQL log, please :) If you can put together a self contained example, even better. I'll try using your plugin to see if I can replicate. > I was wondering if there were changes for generated new sequence values for > Oracle from means other than a trigger that my plugin might be conflicting > with now? I'm not sure I'm parsing that correctly, but there were definitely changes in that area. Have you looked at the related commits? Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
