Skip to content

Commit 2a06e1c

Browse files
committed
Chore: Fix test test_statement_with_error_trace
The test case validates the `error_trace` feature. However, the offending query became valid now, so it needed to be changed.
1 parent cd63abf commit 2a06e1c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

tests/test_error_handling.py

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ def test_statement_with_error_trace(cratedb_service):
1111
engine = sa.create_engine(cratedb_service.database.dburi, connect_args={"error_trace": True})
1212
with engine.connect() as connection:
1313
with pytest.raises(sa.exc.ProgrammingError) as ex:
14-
connection.execute(sa.text("CREATE TABLE foo AS SELECT 1 AS _foo"))
14+
connection.execute(sa.text("CREATE TABLE foo AS SELECT 1 AS _id"))
1515
assert ex.match(
16-
re.escape('InvalidColumnNameException["_foo" conflicts with system column pattern]')
16+
re.escape('InvalidColumnNameException["_id" conflicts with system column]')
1717
)
1818
assert ex.match(
1919
"io.crate.exceptions.InvalidColumnNameException: "
20-
'"_foo" conflicts with system column pattern'
20+
'"_id" conflicts with system column'
2121
)

0 commit comments

Comments
 (0)