Rails 3.0.3 breaks arjdbc?

Hey Folks,

I am seeing an odd problem here. I upgraded to Rails 3.0.3 and all of
the sudden the arjdbc gem isn’t selecting the correct adapter code
anymore… I’m using DB2 and it’s using the generic jdbc adapter instead
of the db2 adapter. A symptom of which is “LIMIT” being used (generic
jdbc) instead of “FETCH FIRST ROW ONLY” (db2/adapter.rb).

I’ve verified this with a new Rails 3.0.3 app… generic jdbc is used.
Switched Rails to 3.0.0 in Gemfile, bundle install’ed and volla
adapter/db2.rb is correctly being used again.

Has anyone else seen this problem?

Thanks!
- nick

Hi Nick,

See

The next release should fix this. If I can get a couple of Oracle bugs
fixed, maybe that will be later today.

/Nick

Hi Nick,

Ah… ARel 2 problems then? Fun!

So with this commit (using up through de66a6e now actually), running
rake test_db2 I still get alot of errors :frowning:

    40 tests, 26 assertions, 0 failures, 22 errors

Here is a sample (hint: it’s still using LIMIT w/3.0.3, killing most
tests):

I’ll poke around a bit, but ARel 2 and this visitor concept is quite new
to me.

Thanks!
- nick

It would be great if you can help get DB2 green again on 3.0.3. I
tried to port the logic from the add_limit_offset! function, but
apparently wasn’t quite succesful.

/Nick