On Jan 27, 2008 3:31 PM, Darryl Cousins <[EMAIL PROTECTED]> wrote: > On Sun, 2008-01-27 at 13:03 -0500, Stephan Richter wrote: > > On Friday 21 December 2007, Darryl Cousins wrote: > > > I find that when I map a class to a table I lose the auto-magic > > > vaidation provided by FieldProperty when setting attributes. > > > > I bet you that sqlalchemy does some evil class hacking. Actually, I > gotta > > check this out. :-) Yeah, from looking at the mapper.py module, I can > see > > that really weird things happen there. They overwrite attributes left > and > > right. Man, I love persistent! I wish they would have used it as a base > for > > their work. > > Hi Stephan, > > Thanks for your comment. > > Just yesterday I was looking at a couple of external sqlalchemy > projects: Elixir [1] and sqlalchemy-validations [2]. I only had a brief > look through the code but the way sqlalchemy-validations hooks itself > into Elixir seemed point to a way to hook zope fieldproperty in there. > Maybe. ;-) > > [1] http://elixir.ematia.de/trac/ > [2] http://code.google.com/p/sqlalchemy-validations/ >
forget to reply all to the list.. have a look at ore.alchemist property.py it wraps sqlalchemy descriptors with validation ones from zope3, for use with a new mapper function bind_mapper which adds in these validaton properties from an interface. cheers, kapil
_______________________________________________ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users