Thanks. I guess I'm still a bit confused. The problem I've been trying to solve happens to involve inserting records into a table. In my real application, the list of records can contain millions of dicts. The name, "bulk_insert_mappings" sort of sounds like it's going to use BULK INSERT types of statements under the covers (though I realize there's certainly no guarantee of that, and I may well be reading more into the name than I should).
Like most database applications, this is got some updating, but most database operations involve working with data already in the database. Is it reasonable to adopt an ORM stance w.r.t. most of the application code, then throw it over for more straightforward Core constructs when data needs to be (in this case, bulk) updated? Or is it expected that any given application should live at one level or the other? Skip -- 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.
