The ODBC specification mandates that all drivers must be thread-safe, that is, drivers must not fail when database requests are made on separate threads. The ODBC 3.0 specification does not provide a method to find out how a driver services threaded requests, although this information is useful to an application.
The Hybrid Data PipelineforODBC driver provides this information to the user through the SQLGetInfo information type 1028, returning a value of 1. A return value of 1 denotes that the session is restricted at the connection level, that is, one thread per connect.
Sessions of this type are fully thread-enabled when simultaneous threaded requests are made with statement handles that do not share the same connection handle. In this model, if multiple requests are made from the same connection, the first request received by the driver is processed immediately and all subsequent requests are serialized.
