You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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 26825
Date: 2019-01-21 17:00:46 +0100
From: @sjoerdmullender
Since files are no longer deleted by COPY BINARY INTO, is this still a problem?
The text was updated successfully, but these errors were encountered: