FreeTDS API
Loading...
Searching...
No Matches
info.c File Reference

SQLGetInfo and SQLGetFunctions implementation. More...

#include <config.h>
#include <stdio.h>
#include <freetds/utils.h>
#include <freetds/odbc.h>
#include <odbcss.h>
Include dependency graph for info.c:

Macros

#define API3_(n)
#define API3_(n)
#define API3X(n)
#define API3X(n)
#define API__(n)
#define API__(n)
#define API_X(n)
#define API_X(n)
#define IVAL   out_len = sizeof(SQLINTEGER), *((SQLINTEGER *) rgbInfoValue)
#define SIVAL   out_len = sizeof(SQLSMALLINT), *((SQLSMALLINT *) rgbInfoValue)
#define UIVAL   out_len = sizeof(SQLUINTEGER), *((SQLUINTEGER *) rgbInfoValue)
#define ULVAL   out_len = sizeof(SQLULEN), *((SQLULEN *) rgbInfoValue)
#define USIVAL   out_len = sizeof(SQLUSMALLINT), *((SQLUSMALLINT *) rgbInfoValue)

Functions

static void odbc_log_unimplemented_type (const char function_name[], int fType)
 Log a useful message about unimplemented options Defying belief, Microsoft defines mutually exclusive options that some ODBC implementations #define as duplicate values (meaning, of course, that they couldn't be implemented in the same function because they're indistinguishable.
SQLRETURN odbc_SQLGetInfo (TDS_DBC *dbc, SQLUSMALLINT fInfoType, SQLPOINTER rgbInfoValue, SQLSMALLINT cbInfoValueMax, SQLSMALLINT FAR *pcbInfoValue _WIDE)
SQLRETURN ODBC_PUBLIC ODBC_API SQLGetFunctions (SQLHDBC hdbc, SQLUSMALLINT fFunction, SQLUSMALLINT FAR *pfExists)
SQLRETURN ODBC_PUBLIC ODBC_API SQLGetInfo (SQLHDBC hdbc, SQLUSMALLINT fInfoType, SQLPOINTER rgbInfoValue, SQLSMALLINT cbInfoValueMax, SQLSMALLINT FAR *pcbInfoValue)

Detailed Description

SQLGetInfo and SQLGetFunctions implementation.

Macro Definition Documentation

◆ API_X [1/2]

#define API_X ( n)
Value:
case n:

◆ API_X [2/2]

#define API_X ( n)
Value:
if (n >= 0 && n < 100) pfExists[n] = SQL_TRUE;

Function Documentation

◆ odbc_log_unimplemented_type()

void odbc_log_unimplemented_type ( const char function_name[],
int fType )
static

Log a useful message about unimplemented options Defying belief, Microsoft defines mutually exclusive options that some ODBC implementations #define as duplicate values (meaning, of course, that they couldn't be implemented in the same function because they're indistinguishable.

Those duplicates are commented out below.