File: test_create_drop_conflict.test

package info (click to toggle)
duckdb 1.5.1-2
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 299,196 kB
  • sloc: cpp: 865,414; ansic: 57,292; python: 18,871; sql: 12,663; lisp: 11,751; yacc: 7,412; lex: 1,682; sh: 747; makefile: 558
file content (30 lines) | stat: -rw-r--r-- 654 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
# name: test/sql/transactions/test_create_drop_conflict.test
# description: Test a conflict with create/drop across transactions
# group: [transactions]

load __TEST_DIR__/broken.db

statement ok
CREATE SCHEMA foo;

statement ok con2
START TRANSACTION;

# Drop the schema in con2
statement ok con2
DROP SCHEMA IF EXISTS foo CASCADE;

# Create a table on the schema we're dropping
# This should succeed because the schema drop isn't committed yet
statement ok con1
create table foo.bar as select 42;

# This now fails because the 'create table' was committed
statement error con2
COMMIT;
----
Could not commit DROP

statement ok
DROP SCHEMA foo CASCADE;