-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add full_match_handler.go to convert the query. #299
Conversation
@NoyException Is this issue the final obstacle to making the C# client functional? If so, we should consider enabling the test in this PR. |
I'll enable it. |
This is only the current obstacle, not the last one... |
…c once per statement.
# Conflicts: # pgserver/stmt.go
# Conflicts: # flightsqltest/driver_test.go
…7-ambiguous-reference
@fanyang01 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This PR resolves issues #297 and #316, addressing compatibility challenges with Npgsql in C#.
Issue 1: Real Data for PostgreSQL System Tables
In PostgresDatabaseInfo.cs, 4 hard-coded queries are executed, with the results accessed via
ReadNonNullableString
. To ensure compatibility and non-null results, real PostgreSQL system table data are mirrored in MyDuck Server. Additionally, all PostgreSQL system table queries are redirected to their corresponding__sys__.pg_xxx
tables in DuckDB.Issue 2: Discontinuous Data in Batches
As discussed in #316, query results are split into multiple batches and returned discontinuously due to each batch containing a separate
RowDescription
. This PR introduces a mechanism to ensure that only a singleRowDescription
is returned per statement execution, providing a continuous result stream for better compatibility with Npgsql.