Repository navigation
JDBC appender loses track on certain sequences of unions and structs. #554
Description
I encountered something weird that seems like a bug in the JDBC appender. I have reproduced it in a relatively minimal test attached. The data is shaped like
a UNION(STRUCT, BOOLEAN), b STRUCTora UNION(BOOLEAN, STRUCT), b STRUCT
In the first case when you try and begin the struct for b you get an error which seems to indicate that it is expecting you to append the BOOLEAN to the union, despite the union being closed. Strangely if you append null in the union after appending the struct then it is happy.
In the second case everything works as I'd expect. Certainly if you try and append null in the analogous point it explodes.
The error message it gives is included in the test but I'll repeat it here if only for search fodder:-
Appender error, catalog: 'null', schema: 'main', table: 'TEST', message: invalid column type, expected one of: '[DUCKDB_TYPE_STRUCT]', actual: 'DUCKDB_TYPE_BOOLEAN'
Activity
Appender fix when UNION has members after STRUCT
staticlibs commentedon Feb 6, 2026
Hi, thanks for the report! Yes, the logic for
UNIONhandling was incomplete, I filed #556 to fix this. Going to include it into the 1.5.0.0 update next week.Appender fix UNION has members after STRUCT (1.4)
Appender fix UNION has members after STRUCT (1.5)
Appender fix UNION has members after STRUCT (1.5)
Appender fix UNION has members after STRUCT (1.4)
Appender fix when UNION has members after STRUCT