On Dec 22, 5:07 pm, Michael Bayer <[EMAIL PROTECTED]> 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?
--
Andres
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
