Randy and I spent some time tackling this on Friday.
First off, I should note, use_db "is a piece of crap. Don't use it"...this according to its project page on github: http://github.com/jcnetdev/use_db/tree/master.
In the databuilder project, we use the ML db as the primary and configured use_db for to use aardvark database for shared models. While fixtures for aardvark database located in test/fixtures seem to work, transaction fixtures do not. We poked around in the use_db library and couldn't find where it went wrong. After 20 mins, we gave up.
So AFAWK, use_db doesn't adequately support transactional fixtures on the secondary database.
Subscribe to:
Post Comments (Atom)
Posts
I think we realized that it attempts to but fails. I'm guessing that it simple replaces fixture methods, but those replacements are no longer used (or have been renamed) in rails 2.2.
ReplyDelete