Date: 2012-01-18 15:23:28 +0100
From: sco <>
To: clients devs <>
Version: 11.5.9 (Aug2011-SP3) [obsolete]

Last updated: 2012-01-26 15:31:57 +0100

Comment 16779

Date: 2012-01-18 15:23:28 +0100
From: sco <>

User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
Build Identifier: v11.5.7 "Aug2011-SP2"

After having tried to import a CSV file into the database, the file can not be written from any text editor. I guess a reboot or session closing is necessary to be able to write to the CSV file again.

Command line used :

c:\Program Files\MonetDB\MonetDB5\bin>mclient -u monetdb -lsql --database=demo -
s "COPY INTO cr_epoch FROM 'e:\synthesis\cr_all_yyyy_mm_dd.csv' USING DELIMITERS
';','\n';"
password:
SQLException:importTable:value 'Timestamp' from line 1 field 1 not inserted, exp
ecting type timestamp(7)
failed to import table

Reproducible: Always

Steps to Reproduce:

1. Create a table with a timestamp element.
2. Create CSV file with an invalid timestamp at first and single column
3. Import with c:\Program Files\MonetDB\MonetDB5\bin>mclient -u monetdb -lsql --database=demo -
   s "COPY INTO cr_epoch FROM 'e:\synthesis\cr_all_yyyy_mm_dd.csv' USING DELIMITERS
   ';','\n';"

Actual Results:

The file cr_all_yyyy_mm_dd.csv can not be written (although acecss rights are set to all from write rights)

Expected Results:

File is saved normally

Since it can be huge files, using temporary copies that can be modified and imported again can be difficult, hence major severity.

Platform : PC
OS : Windows 7 64 bits (sorry, the bigzilla refuses these items to be set...)

Comment 16797

Date: 2012-01-20 09:49:39 +0100
From: @sjoerdmullender

I can see that the server in the Aug2011 releases keep the file open, but this has been fixed in the upcoming Dec2011 release.
Can you try the release candidate at http://dev.monetdb.org/downloads/testings/Windows/ and report back?

Comment 16803

Date: 2012-01-20 14:35:42 +0100
From: @sjoerdmullender

I believe this is fixed, but please reopen if it wasn't.

Comment 16816

Date: 2012-01-26 15:31:57 +0100
From: @sjoerdmullender

The Dec2011 version has been release, so declaring this bug as FIXED.