> Le 22 oct. 2017 à 23:17, Chuck Miller via 4D_Tech <[email protected]> a > écrit : > > Or you could use in error call and simply skip the bad records. I would also > try opening I. C/S and use sql to fill a me empty data file you can use same > on error stuff.
Finally I did like this: • repair "standart" check records in table before/after = one record lost in one table (a proof that a guardian angel for the unconscious exists) • export with SQL EXPORT DATA That's just one line of code, as Pat said. Tim, pictures and blob are exported this way. The whole result is a folder whith some sub folders and files, it's very very very fast. • import just a bit more than one line: loop through table numbers, if the export folder above references the table, import the corresponding sql instructions file with SQL EXECUTE SCRIPT. 4D writes the same SQL that 4D understands (which is not true for other DB's, BTW) •others, specific v12 Hopefully there is no object fields in that version… DISABLE TRIGGERS doesn't exist, so one may need some tool to "freeze" triggers (in case some "on insert" trigger refers to another table, due to the import order, it could cause errors). Moreover, executing triggers in such an import is out of interest. PAUSE INDEXES does not exist too, I suppose it may result in a faster import. Many thanks to all for your answers and comments! -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
