Hi Mike,
On 05/25/13 17:59, Michael Bayer wrote:
Your primary key is far from useless. If your collection consists of unique
values, then that's your primary key. If your collection consists of
non-unique values, but are unique to their parent, then again, that's your
primary key (a composite). If your collection consists of non-unique values
within a single parent, then you can't manipulate that data correctly since you
can't target individual rows.
OK, just wanted to make sure.
In that case, it'd be best to store an array of primitives as native
postgres ARRAY objects if one wants to trade off the overhead of primary
keys for the overhead of re-writing the whole array on every update.
Another feature request for Spyne, I guess :)
So its simple and straightforward just to map to that primary key. SQLAlchemy
could someday provide some out of the box system that does the mapping and
association proxy for you but it's really not that big a deal to automate this
yourself.
I guess I've already done that automation. I do create the table, the
mapping and the association proxy automatically.
Thank you for your response.
Best,
Burak
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
