-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ArgumentError: wrong number of arguments (given 4, expected 1..3)
for activerecord-jdbcsqlite3-adapter
#1136
Comments
Facing similar issue for mysql adapter : JRuby 9.4.5.0, ActiveRecord 7.1.0, activerecord-jdbcmysql-adapter 70.1. Uncaught exception: wrong number of arguments (given 4, expected 1..3) /home/sam/Projects/SDKs/jruby-9.4.3.0/lib/ruby/gems/shared/gems/activerecord-jdbc-adapter-70.1-java/lib/arjdbc/abstract/core.rb:13:in `initialize' |
A year later, I have the opposite problem. I get this error:
My Gemfile contains:
My Gemfile.lock contains:
UPDATE: I have reverted to using Postgres so I no longer need an answer, but I will leave this here for informational purposes. |
@keithrbennett your problem is mostly due to the fact we do not support Rails 7.2. The thing we are not communicating well is that 70.x is Rails 7.0.x and when we support Rails 7.2 you will see a version 72.x come out for the adapters. It is good that postgresql is working but that is somewhat surprising since we have a lot of fixes coming in for 7.1 support. It is possible Rails 7.2 reverted something significant and the 70.x gems happen to work? |
@enebo Thanks for your reply. Sorry I didn't explain that clearly. It's not that Postgres works with Rails 7.2, it's just that I only tried to get it to work with Sqlite. This is a web site running on C Ruby in production, but I was hoping to make it JRuby compatible. I will defer that with Postgres until a future time. |
I saw similar issues, but
sqlite3
adapter seems to not be updated for years.JRuby 9.4.3.0, ActiveRecord 7.0.7,
activerecord-jdbcsqlite3-adapter
70.1.The text was updated successfully, but these errors were encountered: