Thanks for this information. I am working on a program to store csv data into a database. As several csv files can be handled at the same time, I want to achieve that in the case of an error there will be a complete rollback of all data already inserted (either all of the data form all files is inserted or none).
Using transactions would be the best choice to achieve this behavior, but as the program is supposed to work with different databases, including MySQL, and as I have no influence on the user's database setup, I am afraid I have to come up with a different solution. Therefore I now consider to first run a test input (followed by a delete) on all data and only proceed with a final insert if no error occurred with any of the data during the "simulation". However, as this doubles the workload I would be glad if anyone could point me to a more elegant solution. Stefan -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/Wjw_uf_IMc4J. 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/sequel-talk?hl=en.
