Given the ability of an application to sample the data themselves, do we need a standard way for an application to override the imposed schema?
The app can specify desired types (i.e., in select, where, orderby) using CONVERT.
Is there value in specifying that a column of a particular name should always be treated as a particular type (with a particular length/precision/scale)? Is there value in modifying the schema exposed through SQLColumns?
Or does this defining of schema “views” belong outside of ODBC?
Given the ability of an application to sample the data themselves, do we need a standard way for an application to override the imposed schema?
The app can specify desired types (i.e., in select, where, orderby) using CONVERT.
Is there value in specifying that a column of a particular name should always be treated as a particular type (with a particular length/precision/scale)? Is there value in modifying the schema exposed through SQLColumns?
Or does this defining of schema “views” belong outside of ODBC?