Date: 2014-04-08 17:11:07 +0200
From: a.mckinley
To: SQL devs <>
Version: 11.17.13 (Jan2014-SP1)
CC: @njnes

Last updated: 2014-05-22 09:52:30 +0200

Comment 19734

Date: 2014-04-08 17:11:07 +0200
From: a.mckinley

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36
Build Identifier:

If you create a local temporary table in a user session, close the session and then open a new one, it is not possible to create a table of the same name.

Reproducible: Always

Steps to Reproduce:

Execute the following python script twice in a row to reproduce.

import monetdb.sql
import sys

dbh = monetdb.sql.Connection(port=int(sys.argv[1]),database=sys.argv[2],hostname=sys.argv[3],autocommit=True)
cursor = dbh.cursor()

cursor.execute('create local temporary table input (term int, p float) on commit preserve rows;');
cursor.execute('insert into input values ( 1,0.1);');

dbh.close()

Actual Results:

monetdb.exceptions.OperationalError: 42S01!CREATE TABLE: name 'input' already in use

Expected Results:

The local temporary table name should be re-usable in a new session.

Comment 19735

Date: 2014-04-09 12:49:22 +0200
From: @njnes

bug was fixed. At transaction destroy (called at the end of a session) we now properly cleanup all local temporary tables