Bug 3327 - Transactional behaviour of BinaryBulkLoad
Summary: Transactional behaviour of BinaryBulkLoad
Status: NEW
Alias: None
Product: SQL
Classification: Unclassified
Component: all (show other bugs)
Version: -- development
Hardware: All All
: Normal enhancement
Assignee: SQL devs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-19 14:03 CEST by Ying Zhang
Modified: 2019-01-21 17:00 CET (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ying Zhang cwiconfidential 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 cwiconfidential 2019-01-21 17:00:46 CET
Since files are no longer deleted by COPY BINARY INTO, is this still a problem?