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
I noticed that the type inference code for read_database mentioned the possibility of driver-specific knowledge & lookups being needed for further refinement.
I've implemented similar logic at my day job, and I'm happy to build out that functionality here.
Before I put in the time to put together a PR, is that something that would be considered?
Before I put in the time to put together a PR, is that something that would be considered?
I have been preparing a large commit to address this area in more depth; you can take an early look on the branch linked below. Should be ready to land it soon, but want to run it through even more testing first (think I just found a bug in the main MSSQL driver where their string and tz-aware datetime type codes get conflated, and there doesn't appear to be a workaround for it, ouch...)
Description
Hi,
I noticed that the type inference code for
read_database
mentioned the possibility of driver-specific knowledge & lookups being needed for further refinement.I've implemented similar logic at my day job, and I'm happy to build out that functionality here.
Before I put in the time to put together a PR, is that something that would be considered?
https://github.com/pola-rs/polars/blob/8facee942a036f3f875a5f49a51a6fc0b7611895/py-polars/polars/io/database/_executor.py#L319C9-L319C83
The text was updated successfully, but these errors were encountered: