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
Something I have long wanted from ODBC is the ability to do indirect column binding (the way OLEDB can with its DBTYPE_BYREF).
Right now ODBC bindings must be 'flat', that is the memory must be present at the address calculated by adding any offset to the address passed to SQLBindCol//SQLBindParameter. It would be very useful if instead the buffer at the calculated address were itself a pointer and thus allowed structures with embedded pointers to be used when row-wise binding is in effect.
It is possible to perform such indirect binding by using data-at-exec but that is a complicated process for something that could be achieved far easier by the addition of new C target type values (the method I would prefer) or a descriptor attribute.
The text was updated successfully, but these errors were encountered:
Something I have long wanted from ODBC is the ability to do indirect column binding (the way OLEDB can with its DBTYPE_BYREF).
Right now ODBC bindings must be 'flat', that is the memory must be present at the address calculated by adding any offset to the address passed to SQLBindCol//SQLBindParameter. It would be very useful if instead the buffer at the calculated address were itself a pointer and thus allowed structures with embedded pointers to be used when row-wise binding is in effect.
It is possible to perform such indirect binding by using data-at-exec but that is a complicated process for something that could be achieved far easier by the addition of new C target type values (the method I would prefer) or a descriptor attribute.
The text was updated successfully, but these errors were encountered: