11 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Making it possible t...
FromSent OnAttachments
andresj22 Dec 2007 15:38 
Michael Bayer22 Dec 2007 17:07 
andresj22 Dec 2007 17:59 
Michael Bayer22 Dec 2007 18:48 
andresj22 Dec 2007 19:37 
andresj02 Jan 2008 16:56 
Michael Bayer02 Jan 2008 17:27 
andresj02 Jan 2008 17:52 
Michael Bayer02 Jan 2008 18:39 
andresj02 Jan 2008 20:08 
andresj03 Jan 2008 12:13 
Subject:[sqlalchemy] Re: Making it possible to use custom properties in query.filter expressions.
From:andresj (andr@gmail.com)
Date:12/22/2007 05:59:38 PM
List:com.googlegroups.sqlalchemy

On Dec 22, 5:07 pm, Michael Bayer <mike@zzzcomputing.com> wrote:

a synonym() is used so that your attributes are properly available in filter(). This functionality has been vastly improved in the current SVN trunk which resolves all the issues you outline above, and will be available in release 0.4.2. If you checkout the SVN trunk, you can do:

class MyAddress(object): def _set_email(self, email): self._email = email def _get_email(self): return self._email email = property(_get_email, _set_email)

mapper(MyAddress, addresses_table, properties = { 'email':synonym('_email', map_column=True) })

which automatically maps the column to the "_email" attribute, and also instruments the "email" property with the SQL comparator methods.

Thank's for the info, but is SVN ready for production use (kinda like Django's SVN, which is recommended by Django)? I mean, can I use it for my real-world projects without fearing that in any moment it will not work? And in any case, do you know when is 0.4.2 scheduled to come?