activerecord-jdbc-adapter: Rails 5.1 Breaks postgres adapter

I get this error on startup of my server after upgrading to rails 5.1 I presume its from an activerecord change somewhere

web_1 | Bundler::GemRequireError: There was an error while trying to load the gem 'activerecord-jdbcpostgresql-adapter'.
web_1 | Gem Load Error is: uninitialized constant ActiveRecord::ConnectionAdapters::PostgreSQL::ColumnDefinition
web_1 | Backtrace for gem load error is:
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/lib/arjdbc/postgresql/adapter.rb:1527:in `<class:PostgreSQLAdapter>'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/lib/arjdbc/postgresql/adapter.rb:1490:in `<module:ConnectionAdapters>'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/lib/arjdbc/postgresql/adapter.rb:1478:in `<main>'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/lib/arjdbc/postgresql.rb:1:in `<main>'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/lib/arjdbc/postgresql.rb:2:in `<main>'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/activerecord-jdbcpostgresql-adapter/lib/activerecord-jdbcpostgresql-adapter.rb:1:in `require'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/activerecord-jdbcpostgresql-adapter/lib/activerecord-jdbcpostgresql-adapter.rb:1:in `block in (root)'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/activerecord-jdbcpostgresql-adapter/lib/activerecord-jdbcpostgresql-adapter.rb:3:in `each'
web_1 | /usr/local/bundle/bundler/gems/activerecord-jdbc-adapter-395443eef4db/activerecord-jdbcpostgresql-adapter/lib/activerecord-jdbcpostgresql-adapter.rb:3:in `block in (root)'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:1:in `each'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:1:in `(root)'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:91:in `require'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:86:in `<main>'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:75:in `require'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:75:in `block in require'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler.rb:106:in `tap'
web_1 | /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler.rb:106:in `require'
web_1 | /usr/src/app/config/application.rb:9:in `(root)'
web_1 | /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/commands/server/server_command.rb:1:in `(root)'
web_1 | /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/commands/server/server_command.rb:128:in `perform'
web_1 | /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/commands/server/server_command.rb:125:in `perform'
web_1 | /usr/local/bundle/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
web_1 | /usr/local/bundle/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `<main>'
web_1 | bin/rails:4:in `require'
web_1 | bin/rails:4:in `<main>'
web_1 | Bundler Error Backtrace:
web_1 | 
web_1 |   block in require at /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:95
web_1 |               each at org/jruby/RubyArray.java:1733
web_1 |   block in require at /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:86
web_1 |               each at org/jruby/RubyArray.java:1733
web_1 |            require at /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler/runtime.rb:75
web_1 |            require at /opt/jruby/lib/ruby/gems/shared/gems/bundler-1.13.7/lib/bundler.rb:106
web_1 |             <main> at /usr/src/app/config/application.rb:9
web_1 |            require at org/jruby/RubyKernel.java:961
web_1 |    block in (root) at /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/commands/server/server_command.rb:1
web_1 |                tap at org/jruby/RubyKernel.java:1747
web_1 |            perform at /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/commands/server/server_command.rb:128
web_1 |            perform at /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/commands/server/server_command.rb:125
web_1 |                run at /usr/local/bundle/gems/thor-0.19.4/lib/thor/command.rb:27
web_1 |     invoke_command at /usr/local/bundle/gems/thor-0.19.4/lib/thor/invocation.rb:126
web_1 |           dispatch at /usr/local/bundle/gems/thor-0.19.4/lib/thor.rb:369
web_1 |            perform at /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/command/base.rb:63
web_1 |             <main> at /usr/local/bundle/gems/railties-5.1.0.rc1/lib/rails/command.rb:44
web_1 |            require at org/jruby/RubyKernel.java:961
web_1 |             <main> at bin/rails:4

<bountysource-plugin>

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 20 (7 by maintainers)

Commits related to this issue

First pass at fixing JRuby tests See https://github.com/jruby/activerecord-jdbc-adapter/issues/780. Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org> — committed to killbill/killbill-admin-ui by pierre 7 years ago
.travis: Allow failures: jruby postgres Rails 5.1 Failure is due to: https://github.com/jruby/activerecord-jdbc-adapter/issues/780 — committed to glebm/order_query by glebm 6 years ago
.travis: Allow failures: jruby postgres Rails 5.1 Failure is due to: https://github.com/jruby/activerecord-jdbc-adapter/issues/780 — committed to Good725/ruby_order by Good725 6 years ago

Most upvoted comments

@kares Can you help me understand why this is not a serious issue? I may be missing something, but doesn’t it make JRuby unusable with Rails 5.1 and Postgres?

keithrbennett on May 19, 2017

@keithrbennett simply because there’s no one to do it (personally trying to do maintenance of the stable line and some house-keeping/perf.work on master when I have time, the rest of JRuby team already tried doing the AR 5.x update but did not yet deliver fully) … there are attempts but its a task that needs focused men power (AR-JDBC supports a lot of adapters and also accumulated some debt). have tried asking for support to speed things up (personally have no need to chase the Rails 5.x dragon yet) but no one cared much.

simply said this is OSS. its a bit demotivating explaining this over-and-over (esp. when someone expects volunteers to have a certain sense of “seriousness”) and communicating false hopes over private e-mail with occasional “supporters” that always go silent 😥

kares on May 21, 2017

Firstly, thank you for the time and effort you’ve contributed. It’s totally understandable that you have your own life and priorities, and are already contributing heavily, and no one can fault you for that. I was not complaining, I was just confused because I inferred that you believed that the issue was not important. Now I understand that you are not questioning the importance but just explaining that there is not enough manpower to address the issue. Thanks also for the explanation.

keithrbennett on May 22, 2017

@abevoelker there was a lot of broken tests from 50 to 51 on postgresql. I think several of those have been fixed now so we should consider that even if it is not perfect.

enebo on Jan 11, 2018