Table conflict when the table name and fields are identical

[monetdb-team]

Date: 2016-02-06 00:18:32 +0100
From: Pierre Coustillas <>
To: SQL devs <>
Version: 11.21.13 (Jul2015-SP2)
CC: guillaume.savary, @njnes

Last updated: 2016-03-25 09:59:49 +0100

Comment 21772

Date: 2016-02-06 00:18:32 +0100
From: Pierre Coustillas <>

Welcome to mclient, the MonetDB/SQL interactive terminal (Jul2015-SP2)
Database: MonetDB v11.21.13 (Jul2015-SP2), 'mapi:monetdb://rd:50000/lemonde'
Type \q to quit, ? for a list of available commands
auto commit mode: on
sql>CREATE TABLE foo (bar_zzz int);
operation successful (2.979ms)
sql>CREATE TABLE foo_bar (zzz int);
CREATE TABLE: sys_foo_bar_zzz conflicts

Comment 21773

Date: 2016-02-08 15:07:48 +0100
From: Guillaume Savary <<guillaume.savary>>

It's not clear in what this bug is different than 3912

Comment 21774

Date: 2016-02-08 15:41:03 +0100
From: Pierre Coustillas <>

The two bugs are alike. In both cases 'underscore' seems bugue

With bug #3912 after a restart, the data is corrupted and no error message.

With no bug #3919 without restart. Error message on create table : CREATE TABLE: sys_foo_bar_zzz conflicts

The bugs are not related to the names of the table, I tried with another name. But in any case it is necessary to use underscore in the name of the tables and fields.

Comment 21814

Date: 2016-02-23 08:30:01 +0100
From: @njnes

currently we indeed use '_' to seperated schema/table/column names in the mapping to bats (sql storage/logger code). When this leads to problems (see 3912) we now also generate the error, ie to prevent storage corruption.

Comment 21976

Date: 2016-03-25 09:59:49 +0100
From: @sjoerdmullender

Jul2015-SP3 has been released.