On Thursday, October 4, 2012 6:53:02 PM UTC+2, Joel VanderWerf wrote: > > > Hi, all, > > As documented, sequel supports transaction isolation levels for some > databases (including postgres) and not others. On oracle: > > >> DB.supports_transaction_isolation_levels? > => false > > And a little experimentation shows that transactions are not isolated to > the level of serializable. > > This is with sequel-3.40.0 and ruby-oci8-2.1.2. > > Does anyone have any thoughts about making this work? > > Would it be any different on jruby with the jdbc adaptor? >
Not currently. The setting is usually done in the shared adapters. It's disabled by default and not enabled in the oracle shared adapter. However, the oracle and jdbc/oracle adapters use separate transaction implementations (jdbc/oracle uses the jdbc transaction support), so it doesn't make sense to implement it in the oracle shared adapter. I'm not opposed to adding support for this, but I haven't looked up how to set the transaction isolation levels on Oracle. For the jdbc/oracle adapter, if there is a JDBC way to set up transaction isolation levels, then that should probably be added to the jdbc transaction support so that all adapters that use the jdbc transaction support could benefit. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/S2JVBm2EV74J. 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.
