if you use my method above I would do something like this: rename file to .err and send an email to an admin with as much detail as possible while possibly saving said error information in a separate file in case the email doesn't come through. The main concern here would be whether or not the records already inserted can be wrapped in a transaction and rolled back on error. I am guessing no. Which means you will need to manually figure out what the problem with the insert was, fix it, remove all the records that were already inserted, and then rename .err file to .csv for the worker thread to pick it up again.
On Jun 11, 10:20 pm, Contact 42 <[EMAIL PROTECTED]> wrote: > Jonathan Vanasco wrote: > > write to a .txt log in some sort of standardized format , when it hits > > 10k lines run a batch query > > what happens if an insert fails ? > > hd --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
