On Oct 13, 2008, at 2:21 PM, David Clements wrote:
I think it is very valuable and have used something similar on two
different projects.
I didn't read all your code, but I also had an idea that you could
use this during model prototyping and then when you believe you have
the correct data model you could generate a migration that would add
the properties directly to the table backing the propertied object.
dave
right. i'm also thinking of modeling relationships in the same
generic fashion: a relationships table to allow any object to be the
parent(s) or child(children) of any other object(s).
the static nature of dbs is a constant time suck for me - esp in the
early phases of data modeling.
cheers.
a @ http://codeforpeople.com/
--
we can deny everything, except that we have the possibility of being
better. simply reflect on that.
h.h. the 14th dalai lama
_______________________________________________
Bdrg-members mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/bdrg-members
