Oops, I missed the part about the bulk update. I suppose that would work as long as it's keying on the index. The documentation doesn't make it clear how it picks the index to query on... I assume it inspects the column properties and picks the best one to use behind the scenes? Normally you'd query on the id or something.
On Friday, August 10, 2018 at 4:21:32 PM UTC-5, James Couch wrote: > > I think I see what you mean. Do an inline query/update, maybe just query > by primary index for speed. I guess that won't add too much overhead, I'll > give it a shot. > > On Friday, August 10, 2018 at 1:43:51 PM UTC-5, Mike Bayer wrote: >> >> You need to copy the keyedtuples into some other data structure, like a >> dictionary, modify it, then send that data back into updates. Your best >> bet is to use the bulk update stuff once you have those dictionaries, see >> http://docs.sqlalchemy.org/en/latest/orm/session_api.html?highlight=bulk#sqlalchemy.orm.session.Session.bulk_update_mappings >> >> . >> >> >> -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- 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 https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
