That was indeed the issue. sequel-jdbc-as400 was loading ' adapters/jdbc/transactions' before 'adapters/jdbc'. Looks like they fixed this 4 months back but I had the wrong gem version. Thanks for the help!
On Monday, August 27, 2018 at 10:27:40 AM UTC-5, Jeremy Evans wrote: > > On Monday, August 27, 2018 at 7:52:42 AM UTC-7, Stephen Weil wrote: >> >> I am trying to connect to AS400 using Sequel 5.11.0 and sequel-jdbc-as400 >> gem on jruby (tried both 9.1.13.0 and 9.2.0.0). I am receiving errors like: >> >> NameError: uninitialized constant Sequel::JDBC::Transactions::JavaSQL >> Did you mean? Java >> >> I changed the constants in the jdbc/transactions.rb file to add Java:: >> namespace, for example: >> Java::JavaSQL::Connection::TRANSACTION_READ_UNCOMMITTED. >> Then, everything worked fine. >> >> Seems like this is probably not a bug and I am simply missing something >> else on my side. Unless perhaps this is a consequence of removing the AS400 >> code from Sequel 5, and something additional needs to be patched in the >> sequel-jdbc-as400 gem, rather than in Sequel itself. Any suggestion for >> what I might be missing, or has anyone else faced the same issue? >> > > The jdbc adapter defines Sequel::JDBC::JavaSQL. The db2, derby, h2, > hsqldb, oracle, and sqlanywhere jdbc subadapters all use the > jdbc/transactions.rb file for transaction support, and I haven't > experienced the issue you are describing with those adapters. > > Is the code loading sequel/adapter/jdbc/transactions.rb before loading > sequel/adapter/jdbc.rb? If so, that's probably the issue and that should > be fixed. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
