New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Transactional behaviour of BinaryBulkLoad #3327

Closed

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Labels

Date: 2013-07-19 14:03:52 +0200
From: @yzchang
To: SQL devs <>
Version: -- development

Last updated: 2019-01-21 17:00:46 +0100

Comment 18927

Date: 2013-07-19 14:03:52 +0200
From: @yzchang

Triggered by thread "Must the file be deleted after "copy binary into table
from file"" on July 19, 2013:

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.