Hi there, I am trying to use the Progress OpenEdge (11.1, openedge.jar) JDBC driver with Sequel but I am having some quite severe problems with it.
In a simple, standalone application using JRuby, it works - at least to the point where I can connect to the server and so forth. (Haven't tested the Sequel DSL and I suspect parts of it will be broken since there isn't any Progress JDBC adapter in Sequel at the moment). *But*, when I try to run inside an embedded application server powered by jruby-complete-1.7.4.jar, it fails quite miserably. I've been debugging the issue and it seems like the classical "skipping: java.sql.DriverInfo" error, which originates from this code line in the driver manager: http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7u40-b43/java/sql/DriverManager.java#272 The big question is just "how do I get around that"? :) It seems like the other drivers (e.g. jTDS) works much better, and I suspect that Sequel might have some clever tricks in there that handles this... or am I mistaken in that? (I got that impression from reading the DATABASE_SETUP code in the adapters/jdbc.rb file). So I could probably hack up an openedge adapter for Sequel, and it might be the best way to accomplish it, but do you have any other suggestions? Best regards, Per -- 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 http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
