Skip site navigation (1) Skip section navigation (2)

Re: BoolsAsChar

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Matt Clark" <mclark(at)rushe(dot)aero(dot)org>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: BoolsAsChar
Date: 2002-12-13 08:30:18
Message-ID: 03AF4E498C591348A42FC93DEA9661B8128D61@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: Matt Clark [mailto:mclark(at)rushe(dot)aero(dot)org] 
> Sent: 12 December 2002 23:39
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] BoolsAsChar

Hi,

> 1 - apparently there is a problem with the flag "ksqo", which 
> 7.3 does not 
> recognize.  I found a patch in the archives which apparently 
> just comments out 
> the SQLExecDirect call which sets the flag.  The patch 
> doesn't match the code in 
> connection.c, however....

In connection.c here (on the machine that built the distribution) I
have:

	/* KSQO (not applicable to 7.1+ - DJP 21/06/2002) */
	if (ci->drivers.ksqo && PG_VERSION_LT(self, 7.1))
	{
		result = PGAPI_ExecDirect(hstmt, "set ksqo to 'ON'",
SQL_NTS);
		if ((result != SQL_SUCCESS) && (result !=
SQL_SUCCESS_WITH_INFO))
			status = FALSE;

		mylog("%s: result %d, status %d from set ksqo\n", func,
result, status);

	}

What do you have in connection.c?

Regards, Dave.

pgsql-odbc by date

Next:From: Eric HallanderDate: 2002-12-13 14:57:02
Subject: Re: BoolsAsChar
Previous:From: HanDate: 2002-12-13 06:55:18
Subject: Re: Bug in psqlodbc7.03.0001

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group