On Sep 12, 2013, at 2:35 PM, Jonathan Vanasco <jonat...@findmeon.com> wrote:
> I just spend 30mins with pdb; I was wrong ; I think it would be way too hard > to get it into the ORM. The way MutableDict seems to be currently > integrated, the entire value is updated for the key , and the original value > seems to be obliterated. > > Outside of the ORM -- do you have any references for the update & insert ? > do you think it would be possible to implement this in select ? this stuff should work completely in core, if you look at the examples in the 0.8 migration for ARRAY, that should give a feel for it, the same types of things should all work for HSTORE : http://docs.sqlalchemy.org/en/rel_0_8/changelog/migration_08.html#enhanced-postgresql-array-type > > Our HSTORE data is small now, but growing -- we're using it to store revision > history. I've been experimenting with using `deferred` columns to keep them > from being loaded on the main query, then accessing only when needed. If we > can only pull out and update the relevant KV-pairs, there would be even > smaller overhead. > > -- Sorry if i'm hijacking this thread, Philip. From your example usage > though, I think we have the same concerns/issue ; I've just been approaching > it from a slightly different standpoint. > > -- > 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. > For more options, visit https://groups.google.com/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
