Closed NoyException closed 3 days ago
This could be fixed by adding fallthrough
or using case tree.CopyFormatText, tree.CopyFormatCSV:
. Although the TEXT format is not fully compatible with CSV (see https://github.com/duckdb/duckdb/pull/14464 ), for common cases it should work well.
This could be fixed by adding
fallthrough
or usingcase tree.CopyFormatText, tree.CopyFormatCSV:
. Although the TEXT format is not fully compatible with CSV (see duckdb/duckdb#14464 ), for common cases it should work well.
I encountered this problem when executing the COPY in pg_dump
(see #130 ), and initially tried to add the fallthrough
keyword directly. But the txt format in pg_dump
is delimited by consecutive Spaces, so maybe I can try to match CSV with \s+
as the delimiter.
But the txt format in pg_dump is delimited by consecutive Spaces
Is it tab (\t
) but displayed in your editor as 4 spaces?
Is it tab (
\t
) but displayed in your editor as 4 spaces?
You're right. It should be a tab. It's just a 16-character column filled with spaces.
In
pgserver/connection_handler.go
, line 654:The text format is ignored, which makes
dataLoader
still nil after nil check and causes a nil reference error when executingCOPY FROM stdin;