Bug 6137 - ALTER TABLE qname ADD COLUMN ncołumn COPY [BINARY] FROM 'external_file'
Summary: ALTER TABLE qname ADD COLUMN ncołumn COPY [BINARY] FROM 'external_file'
Status: NEW
Alias: None
Product: SQL
Classification: Unclassified
Component: all (show other bugs)
Version: 11.23.13 (Jun2016-SP2)
Hardware: Other All
: Normal enhancement
Assignee: SQL devs
Depends on:
Reported: 2016-12-02 07:50 CET by daniel.zvinca
Modified: 2016-12-02 08:00 CET (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description daniel.zvinca 2016-12-02 07:50:51 CET
User-Agent:       Mozilla/5.0 (Linux; Android 6.0.1; SM-T810 Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.85 Safari/537.36
Build Identifier: 

As a column store engine, MonetDB should be able to add or change directly values from external files in natural order. A similar syntax for bulk update makes also sense. UPDATE qname SET (ucolumn1, ucolumn2, ...) COPY [BINARY] FROM 'csvfile'|('binfile1', 'binfile2')

Reproducible: Always

Actual Results:  
Even if is not at all standard SQL, a full replacement of a column with some late computed values in other environments is a common action. Inserting binary into a temporary table and then updating the target column using a row_number() like join  does not look reasonable. Using a common primary key for both target dataset and temporary table would introduce even more unnecessary overhead, yet it looks to me the only safe approach I could come up with.