The table below shows how SQLAPI++ maps its internal library types to SQL Anywhere API data types: SA_dtLongBinaryįor additional information see Getting Started - Handle Long/CLob/BLob. The SQLAPI++ data type you use for input markers determines what native API program types will be used for sending Long/Lob data to the server. When binding input data from your program the reverse mapping is taking place. The table below shows how SQLAPI++ maps SQL Anywhere server data types to Long/Lob library types: LONG BINARY The mapping determines which native APIs the library will use for fetching LOB data. When fetching data SQLAPI++ detects data types of the columns in the result set and maps those types to internal library types. Working with Long or Lob (CLob, BLob) data In addition to the SQL-92 levels, if you specify 'snapshot' isolation level, it will be mapped as: SA_Snapshot → SET TEMPORARY OPTION isolation_level = 3.įor more details see SAConnection::setIsolationLevel. SQLAPI++ maps different isolation levels on SQL Anywhere in the following way: SA_ReadUncommitted Serializable (the highest level, where transactions are completely isolated from one another).Read uncommitted (the lowest level where transactions are isolated just enough to ensure that physically corrupt data is not read).SQL-92 defines four isolation levels, all of which are supported by SQLAPI++: You can use this default value only if you have SAConnection::setAPI method with SAPI object initialized with SA_SQLAnywhere_Client constant beforeįor more details see Getting Started - Connect to Database, SAConnection object, SAConnection::Connect. SA_Client_NotSpecified – used by default if eSAClient parameter is omitted.SA_SQLAnywhere_Client – SQL Anywhere client.One of the following values from SAClient_t enum: A connection object is represented by SAConnection class. To connect to a database you need to initialize a connection object. Getting native connection related handles.Connection, command, parameter and field options.Working with Long or Lob (CLob, BLob) data.This guide covers specific information related to working with SQL Anywhere server using SQLAPI++ library in the following areas: But each server has some specific features which a developer has to know in order to leverage server's unique features and avoid potential errors.įor complete information on using SQLAPI++ check out Getting Started and Documentation. It provides unified API to access any database, keeping your code portable. SQLAPI++ allows to seamlessly work with a variety of SQL database servers. Oracle SQL Server DB2 Sybase MySQL / MariaDB PostgreSQL SQLite Informix InterBase / Firebird SQLBase SQL Anywhere ODBC SQL Anywhere Guide

Sql anywhere client download