Hi guys,
I've been really frusterated with fixtures as of late. As wonderful as
migrations are (allowing me to develop, test and deploy on different
systems) being able to support multiple databases isn't nearly as cool
when my tests don't work on all the systems the codebase does due to
non db agnostic fixtures.

I'm working with some code to make a ruby fixture markup similar to
the migrations code. The approach I think might work is to allow each
adapter to define to_datatype methods in a fixtures module which tells
the code how to translate the data held in fixtures to be placed in
the db. So how to place true and false (1 and 0, 't' and 'f' etc) or
Date values or what have you.

Does anyone have suggestions/comments to that end?

Kev
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to