On Oct 14, 2013, at 2:52 PM, Jeremy Evans <[email protected]> wrote:
> On Monday, October 14, 2013 11:32:11 AM UTC-7, GregD wrote: > > On Oct 14, 2013, at 2:10 PM, Jeremy Evans <[email protected]> wrote: > > > > > jruby -r sajdbc4.jar ... > > RUBYOPT=-rsajdbc4.jar jruby ... > > > > The issue with requiring specific jar names is it requires that they be > > stored at the root of one of the ruby load paths. These jars can be stored > > in subdirectories or outside the ruby load path, so Sequel does not require > > the .jar files automatically (it will require the jdbc-* gem automatically > > for the subadapters that can be used with jdbc-* gems, since that is just > > normal gem loading). > > > > Okay that worked. But, should we provide jdbc-sqlanywhere gem that will load > the jars? I'm not following. > > I don't think that is necessary. If one is created, making Sequel use it is > a one-line change. But unless you plan to maintain the gem and issue new > versions when new versions of SQLAnywhere are released, I don't think it's a > good idea. The other jdbc-* gems that Sequel supports are managed by the > JRuby team, who do a pretty good job of maintaining them. > > Requiring the jar file manually is how the other jdbc subadapters that don't > have jdbc-* gems works, and I don't think there is a good reason to make an > exception for SQLAnywhere. Thanks for the explanation. -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.
