On Jun 27, 2008, at 10:12 AM, Paul-Michael Agapow wrote:

>
> But, I have a situation where I don't want FooCollection to actually
> contain the actual Foos, just a list of their keys. That is, Foos and
> FooCollections have to be handled separately.  Obviously it will
> involve more paperwork, but how can I make the "members" attribute
> just contain the keys? Is a mapper extension required, or is there a
> simpler way?


we have a class-level extension called "associationproxy" thats used  
for this:

http://www.sqlalchemy.org/docs/05/plugins.html#plugins_associationproxy



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to