Forum: JRuby [ANN] AR-JDBC 1.3.0.rc1 released

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Caa2df9372ffa0a9e95b2bab1e8fea34?d=identicon&s=25 Karol Bucek (Guest)
on 2013-08-05 09:10
(Received via mailing list)
Happy new week JRuby-ists,

I'm happy to announce that the first (and hopefully last) RC has been
reached on our journey towards 1.3.0.

The change-log is yet again quite long (this should change soonish as
wild refactoring nights are now over). Some final API tunings went in
our Java API should be stable now for potential extensions. This is also
the main reason why it took so long since prepared statement support
out quite time consuming but most adapters are rolling fine with it and
major differences between JDBC driver vendors (we support) should be
For the previous beta PS did not handle all type mappings and only
with `exec_query`, now `exec_update` and `exec_insert` are covered as

Some other (besides prepared-statements) features in this release
include :
- return date/time in custom SELECTs e.g. *SELECT CURRENT_TIME() ...*
- (un-official :) support for MS' official driver for SQLServer
- minor micro "performance-improvements" (mostly speed-up) for a few

Full change-log (including 1.3.0 betas) might now be found at our
repository :

As usual, install using : `gem install activerecord-jdbc-adapter --pre`
or point your *Gemfile* at : `gem 'activerecord-jdbc-adapter',

AR-JDBC 1.3.0 line aims to support ActiveRecord 2.3/3.x/4.0 from a
gem on JRuby 1.7.x (as well as 1.6.8).

Please give it a try (esp. with Rails 4.0) and do let us know how it

p.s. There's a prepared-statement issue with PostgreSQL's arrays that
not make it in.

<3 Team AR-JDBC
This topic is locked and can not be replied to.