On Oct 14, 2013, at 12:43 PM, Jeremy Evans <[email protected]> wrote:
> On Thursday, October 10, 2013 12:05:34 PM UTC-7, Jeremy Evans wrote: > From my brief review, this looks good. It might take me a little while to > get it fully reviewed and merged, but it will definitely happen before the > next release. Thank you very much for your work on this. > > I've just merged the SQLAnywhere support into Sequel. Please review the > changes I've made and test it and let me know how it works for you. Note > that I changed how the sqlanywhere adapter connection strings work, to make > them more similar to other Sequel connection strings, so you'll probably need > to adjust those connection strings when you test. Yes, thank you for fixing that. I got it to connect and I did not evaluate the code very closely after that. MRI rubies are all working. :-) I notice the changes to how the jdbc drivers are loaded and I can not get connected via jdbc anymore. Where or how do I require the jar? CLASSPATH was how jruby did it before and the code tried the require for various jar files that ship with different SqlAnywhere releases. From the command line, how do I require that jar? -GregD -- 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/groups/opt_out.
