Greetings JRubyists,
the AR-JDBC (JRuby) Team would like to inform you that
activerecord-jdbc-adapter 1.2.8 has been released. We did not plan any
more
1.2.x releases but since the double bind issue (which has been the
regression behind the previous 1.2.7 release) was still present when
“raw”
connection CRUD methods were being used we decided it’s better to get
another 1.2 release out.
Thanks Chris Kimpton for reproducing and reporting … you can find the
code that affects 1.2.7 at the bottom of the issue thread
When you use SQL bind params where you are binding a string with a question mark, the adapter creates an invalid SQL statement · Issue #322 · jruby/activerecord-jdbc-adapter · GitHub …
Please also note, that this release does not contain all the fixes and
updates done lately on master (due refactorings that are already there)
which will end up as 1.3.0.
We should have a first beta starting the 1.3 line soon (master as is is
pretty stable as well).
But a few backports made it into 1.2.8, here’s the changelog :*
*- [derby] (native) types review & cleanup, externalize AR patch-ing
- [h2] correct schema dump (jdbc detected sql types)
- [hsqldb] correct schema dump (jdbc detected sql types)
- cleanup H2 / HSQLDB adapter - HSQLDB should not know about H2
- [mssql] [oracle] [db2] [derby] remove_column 3.x compatibility
- [sqlite3] setup native types + make sure tables accepts table_name as
well - [mysql] version + support_“feature” (as Rails)
- jdbc_connection unwrap parameter for unwrapping (pooled) connections
- (native) connection #columns #columns_internal expects string
table_name - [postgres] no need to clear_query_cache after insert on AR-2.3’s
#insert_sql - there’s still a double bind when “raw” crud methods used (re-closing
#322)
We’ve also released updated drivers today, namely jdbc-mysql 5.1.24 and
jdbc-derby 10.9.1.0 …
Enjoy and stay tunned for more !
– AR-JDBC Team