You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TestDuckDBJDBC#test_struct_with_bad_type failed with java.lang.Exception
java.lang.Exception
at org.duckdb.test.Assertions.assertTrue(Assertions.java:15)
at org.duckdb.test.Assertions.assertTrue(Assertions.java:10)
at org.duckdb.TestDuckDBJDBC.test_struct_with_bad_type(TestDuckDBJDBC.java:3510)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.duckdb.test.Runner.runTests(Runner.java:45)
at org.duckdb.TestDuckDBJDBC.main(TestDuckDBJDBC.java:4531)
The reason is that the assertion checks if the error message contains the string:
"Parser Error: syntax error at or near "TYPE""
But the actual error message returned by DuckDB is:
"Invalid Input Error: Value "BAD TYPE NAME" can not be converted to a DuckDB Type.
Possible examples as suggestions:
* BYTEA
* DATE
* DATETIME
* BIT
* TINYINT
The text was updated successfully, but these errors were encountered:
TestDuckDBJDBC#test_struct_with_bad_type fails with:
The reason is that the assertion checks if the error message contains the string:
"Parser Error: syntax error at or near "TYPE""
But the actual error message returned by DuckDB is:
The text was updated successfully, but these errors were encountered: