Posted on 08-07-2008
Filed Under (Code) by Cody

Rails has come a long way quickly, but one of the biggest problems with our favorite MVC framework is support for multiple databases.

Sure you can use self.table_name and/or establish_connection to force a model to point to a table in a different db, but try running a freaking test with fixtures for the offshoot models, and you'll see what I'm talking about.

Even more depressing is SQLite3's lack of cross-database query join support, making this statement impossible:

has_and_belongs_to_many :blocked_users,
:class_name => 'User', :join_table => :blocked_users,
:foreign_key => "user_id", :association_foreign_key => "blocked_user_id"

Here's the kicker: All of our apps are multi-database apps, so that means no more SQLite allowed for us, and I really loved it until now.

If I'm wrong, let me know. I'd love to go back to using SQLite for local development. Same for an easy way to load fixtures.

    Read More   

Comments

Karmen on 9 July, 2008 at 6:23 pm #

This may be of some help. Just came out today: http://blog.fiveruns.com/2008/7/9/introducing-data_fabric


Bryan Zug on 10 July, 2008 at 5:52 pm #

Apologies for the off topic, but I was curious about a flash app someone told me about on espn.com that had a mini-tutorial on start that walked folks through how to use it.

Am gathering design examples of things like that and would love to track that down.

Could any of you here point me toward such a thing?


Cody on 10 July, 2008 at 6:05 pm #

Hey Bryan. I think MyESPN does this for first time users (http://myespn.go.com).

Not sure if that’s what you’re talking about, but that’s all I know of.


Post a Comment
Name:
Email:
Website:
Comments: