Skip to content
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

Permit retrieval of unicode data in VAR/CHAR columns #553

Merged
merged 4 commits into from
Mar 28, 2023

Conversation

detule
Copy link
Collaborator

@detule detule commented Mar 25, 2023

This fixes #369 #437 #489 #524

There are some more details about the issue here

The short summary is: This work helps us better support

  • Some unorthodox use-patterns: unicode data in VAR/CHAR columns.
  • Back-ends where character data types are synonymous ( Snowflake ).

This comes at the cost of larger memory allocations. However these memory allocations are transient ( created/destroyed with each query ), and do not scale, for example, with the size of the data set ( number of rows ). From that perspective, I expect marginal impact - but worth keeping an eye out.

@detule detule requested a review from hadley March 25, 2023 19:10
@@ -102,6 +102,16 @@
#endif
#endif

#if defined(NANODBC_OVERALLOCATE_CHAR)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we diverging from nanodbc here, or did you get this merged upstream?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks for all your work on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants