Has anyone used MultiDb with Ruby 1.9.2?

[scottpersinger]

We've been using MultiDb for a long time with Ruby 1.8.6 and Rails 2.3.2. We're currently upgrading to Rails 2.3.11 and Ruby 1.9.2, and we're seeing some kind of horrible error out of the gem:

ArgumentError (wrong number of arguments (1 for 0)):
/usr/lib/ruby/gems/1.9.1/gems/schoefmax-tlattr_accessors-0.0.3/lib/tlattr_accessors.rb:55:in block in current=' app/models/user_setting.rb:2:inclass:UserSetting'
app/models/user_setting.rb:1:in `<top (required)>'

Has anyone else seen these errors? Or has anyone run successfully with ruby 1.9.2?

[schoefmann]

My tlattr_accessor gem seems to be to blame here. Looks like Object finalizers behave slightly different in 1.9 - the error can be reproduced in the specs of tlattr_accessor when running 1.9.2.

[scottpersinger]

Awesome....so, any chance for a cure?

[avocade]

Wondering this as well, as we're about to deploy with this gem. Currently on 1.8.7, but going to upgrade to 1.9.2 as soon as rails 3.1.1 is out.

[scottpersinger]

I did end up having to hack the tl_accessors code. I'm really sorry but that is the best that I can recall - we stopped using the multidb gem a while back.

[avocade]

Interesting, what are you using instead?

[scottpersinger]

I believe we ended up monkey patching the tl_accessors code itself to work under 1.9. It wasn't a complicated patch as I recall.