search

microsoft / ODBC-Specification

Microsoft ODBC Specification
Other
121 stars 40 forks source link

Should numeric overflow also be handled by SQL_ATTR_LENGTH_EXCEPTION? #42

Closed mikepizzo closed 6 years ago

mikepizzo commented 8 years ago

Today SQL_ATTR_LENGTH_EXCEPTION allows the app to retrieve the remainder of the data using SQLGetData. Numeric data can't be retrieved in parts, so it doesn't make sense to retrieve the remainder, but should we still use data_at_fetch in order to rebind or call SQLGetData on the entire numeric value? Would that cause the driver to cache the value, or would they likely either have it in a raw form anyway or know the required precision/scale ahead of time?

mikepizzo commented 6 years ago

Already handled by metadata changed, so probably don't need to add anything here.

mikepizzo commented 6 years ago

Propose: not do anything at this point. We can add a SQL_ATTR_NUMERIC_PRECISION_EXCEPTION in the future, if necessary.