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
When writing to a datetime/datetime2 target, we use a fixed precision of three decimals to avoid needing to know the user-configurable precision of the datetime2 field.
However, when writing, we attempt to discover the target table column descriptions and pass these down to nanodbc via statement::describe_parameters. We do this to avoid (nanodbc) needing to call SQLDescribeParams for each of the individual columns/parameters when binding the data buffers.
If we already have the column descriptions, we could have nanodbc::statement expose these - see for example nanodbc::statement::parameter_size(int) that already does something similar. Then we can use this API endpoint in odbc_result to maybe deduce the parameter precision.
The text was updated successfully, but these errors were encountered:
Related to: #790 #208 #130
When writing to a datetime/datetime2 target, we use a fixed precision of three decimals to avoid needing to know the user-configurable precision of the datetime2 field.
However, when writing, we attempt to discover the target table column descriptions and pass these down to
nanodbc
viastatement::describe_parameters
. We do this to avoid (nanodbc) needing to callSQLDescribeParams
for each of the individual columns/parameters when binding the data buffers.If we already have the column descriptions, we could have
nanodbc::statement
expose these - see for examplenanodbc::statement::parameter_size(int)
that already does something similar. Then we can use this API endpoint inodbc_result
to maybe deduce the parameter precision.The text was updated successfully, but these errors were encountered: