Per file?? Even if it's a really large file?? Is the only limit on transaction size available client memory or are their constraints on the server side as well?
Also, I think my example was over-simplified. There are many different types of attributes I need to accumulate and I'm having a hard time conceiving of a good IO model if I do what you suggest. I should mention that I'm a pretty experienced writer of stored procs, and I still don't like your idea. I think i'll noodle on this a bit longer but appreciate your feedback. Thx Dewey On Thursday, December 18, 2014 9:38:30 AM UTC-6, Jonathan Vanasco wrote: > > Based on your specs, I think it would be simplest to store the rows in the > DB then just run reports on them. You'd have a solution in minutes. You > should be doing a transaction per Excel file, not per row. You could > probably create a function or view that generates the record you want. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
