Michael Bayer wrote:
What do you mean exactly? Richer automatic discovery sounds good,
but I am not entirely sure what you are talking about :)
If I understand correctly from a conversation I had with Ben the
other day, he wants to tack on metadata information onto class
properties mostly for the purpose of providing clues to a view
layer about how to handle/display that object. this is an idea I
am largely uncomfortable with since the view is basically being
allowed to pollute the model. also, Python allows the "tacking
on" of whatever attributes you want onto any other object,
including class properties, so I am not sure what kind of changes
to SQLAlchemy or the declarative layer he would have in mind, that
cant be better accomplished by some externally provided feature,
like a special base class (ViewPollutedSQLAlchemyObject ? :) ) .
Eek. I think I am with Mike here. Use a specialized base class.
--
Jonathan LaCour
http://cleverdevil.org
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
