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:
The actual behavior currently differs between data types; for numerical
types, the user-provided files are moved as explained above; for stings, the
files are read and processed, i.e., the used-provided file remains in place
as-is. We need to consider unifying this behavior, e.g., by deleting also the
user provided files for strings once they have been processed/loaded.
I'd vote for deleting the files containing strings as well, for reasons of storage.
Date: 2013-07-19 14:00:37 +0200
From: @yzchang
To: SQL devs <>
Version: -- development
Last updated: 2019-01-21 16:59:51 +0100
Comment 18926
Date: 2013-07-19 14:00:37 +0200
From: @yzchang
Triggered by thread "Must the file be deleted after "copy binary into table
from file"" on July 19, 2013:
types, the user-provided files are moved as explained above; for stings, the
files are read and processed, i.e., the used-provided file remains in place
as-is. We need to consider unifying this behavior, e.g., by deleting also the
user provided files for strings once they have been processed/loaded.
I'd vote for deleting the files containing strings as well, for reasons of storage.
Comment 26824
Date: 2019-01-21 16:59:51 +0100
From: @sjoerdmullender
This has been fixed in the sense that files are never deleted anymore when using COPY BINARY INTO.
The text was updated successfully, but these errors were encountered: