skip to main content
Getting Started : Supported Features
 

Try DataDirect Cloud Now

Supported Features

To take full advantage of the DataDirect Cloud Driver for ODBC, it will be helpful for you to know that it supports the following features (among others):
*Secure Communication
All communication between the driver and the DataDirect Cloud connectivity service, including user IDs and passwords, is encrypted using Secure Sockets Layer (SSL). SSL is an industry-standard protocol for sending encrypted data over connections. It secures the integrity of your data by encrypting information and providing client/server authentication.
In addition, you have the option of storing the credentials for your cloud data store securely in the Cloud Data Source, or of managing it yourself in the ODBC data source.
*Unicode Support
Multilingual ODBC applications can be developed on any operating system using the driver to access both Unicode and non-Unicode enabled data stores. The driver is fully Unicode enabled. On UNIX and Linux platforms, the driver supports both UTF-8 and UTF-16. On Windows platforms, the driver supports UCS-2/UTF-16 only.
The driver supports the Unicode ODBC W (Wide) function calls, such as SQLConnectW. This allows the Driver Manager to transmit these calls directly to the driver. Otherwise, the Driver Manager would incur the additional overhead of converting the W calls to ANSI function calls, and vice versa.
See Internationalization, Localization, and Unicode for related details.
*Safe Threading
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 DataDirect Cloud for ODBC 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.
*Number of Connections and Statements Supported
The driver supports multiple connections and multiple statements per connection.
*Parameter Metadata Support
The driver supports returning parameter metadata for all types of SQL statements and stored procedure arguments.