|Summary:||Transactional behaviour of BinaryBulkLoad|
|Product:||SQL||Reporter:||Ying Zhang <y.zhang>|
|Component:||all||Assignee:||SQL devs <bugs-sql>|
Description Ying Zhang 2013-07-19 14:03:52 CEST
Triggered by thread "Must the file be deleted after \"copy binary into table from file\"" on July 19, 2013: 3) In case the copy into file, e.g., due to a failing sanity check after the file is moved, that data is factually lost, i.e., the files are gone, but no data is loaded into the database; we need to either document this clearly, or make the implementation behave like a transaction. For now, we should document this behaviour. But a long term solution is to implement the transactional behaviour.
Comment 1 Sjoerd Mullender 2019-01-21 17:00:46 CET
Since files are no longer deleted by COPY BINARY INTO, is this still a problem?