For the records:
> I would go the route of dumping things to files and then importing from files,
I just had to go the execute_for_fetch route for yet another project, and it's surprisingly fast, thanks for that! :)
But ...
> since that allows better granularity in the sense that either a table is imported completely or not at all.
When dealing with MySQL or MariaDB this depends on the engine used, since I get an array of potential errors returned from execute_for_fetch ...
On InnoDB I can then decide to either ->commit or ->rollback and this works fine.
But on MyISAM transactions and rollbacks are not supported.
There I have to go the route of using intermediate temporary tables to be safe(r).
|