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
Describe the bug
When querying a table with nullable fields in clickhouse (postgres doesn't have this behavior), the result prints the pointer address instead of the value. After some debugging it looks like clickhouse is using pointer types to represent nullability.
To Reproduce
Steps to reproduce the behavior:
Setup a clickhouse instance
Create a table with a nullable column
Insert data into table
Select table (you will now see pointer addresses instead of the values)
Expected behavior
Pointers should be resolved, if they are not nil
Versions (please complete the following information):
Some databases (e.g. clickhouse) is using pointer values to represent
nullable values when querying from the database. The current logic to
transform values to strings when querying data, does not handle this
correctly. It will simply transform the pointer to a string, which
results in the pointer address being printed.
To handle this, the value reported from the sql driver will now tried to
be extracted, if it is a pointer. This means the value of the pointer
will then be transformed to a string, instead of the pointer directly.
Additionally, some cases where this was causing issues in the clickhouse
implementation have been fixed.
Fixessqls-server#151
Describe the bug
When querying a table with nullable fields in clickhouse (postgres doesn't have this behavior), the result prints the pointer address instead of the value. After some debugging it looks like clickhouse is using pointer types to represent nullability.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Pointers should be resolved, if they are not nil
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: