Skip to content
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

consistent behaviour of BinaryBulkLoad #3326

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

consistent behaviour of BinaryBulkLoad #3326

monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels
enhancement New feature or request SQL

Comments

@monetdb-team
Copy link

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:

  1. 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.

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.

@monetdb-team monetdb-team added enhancement New feature or request SQL labels Nov 30, 2020
@sjoerdmullender sjoerdmullender added this to the Ancient Release milestone Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request SQL
Projects
None yet
Development

No branches or pull requests

2 participants