Karol Bucek

please could you also fill in your AR-JDBC gem and Rails 4.x version - might come handy for reproducing

thanks, sorry I haven't looked at the script first - assumed it to be the same as you initially posted on IRC. ... still one thing that isn't clear -...

MS-SQL is very low on :purple_heart: from our users ... the 4.2 support was done 'quickly' with no real-world testing. I am willing to look in detail into specific issues...

AR-JDBC 1.3 (**1-3-stable** branch) supports multiple AR versions from a single base (see .travis.yml). just run the suite before and after the change on 4.2 that will be most important...

yes, we will need to work on refactoring that part (it affects all not just Oracle) ... feel free to go for it!

tried reproducing but failed - all seems fine ;( ... would be great if ORA issues got reproducable samples. anyway, I think it's possible to work-around the issue if a...

`insert_returning: true` actually was not working ... but should be now 7b6432546bcb9136a3 there's also an option to turn [generated keys off](864efb722ea83c1e1eb8) ... but it's preferable to try `insert_returning: true`

@andfx first of all thanks, second maybe you really need to look into it than. the problem in resolving this is I was unable to reproduce so it must be...

does not seem like this was really a psych issue at all. its also (old) jruby-complete specific. if anyone land here report against JRuby using an up to date version.

interesting, I might have hoped Rails would at some point merge AR-JDBC but never thought of merging jruby-openssl :) just to double check, @zzak do you realize the JRuby version...