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

Re: changed behavior in libpq odbc driver

From: "Scot Loach" <sloach(at)sandvine(dot)com>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>,"Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: changed behavior in libpq odbc driver
Date: 2005-08-31 13:46:57
Message-ID: 71837C040963F748B9B94E123A289678664D91@mailserver.sandvine.com (view raw or flat)
Thread:
Lists: pgsql-odbc
My mistake, I tried it again and it does seem to be working now - I must not have updated properly for my last compile.

scot.


-----Original Message-----
From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
Sent: Wednesday, August 31, 2005 9:08 AM
To: Scot Loach; Anoop Kumar
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] changed behavior in libpq odbc driver


 

> -----Original Message-----
> From: Scot Loach [mailto:sloach(at)sandvine(dot)com] 
> Sent: 31 August 2005 13:52
> To: Anoop Kumar
> Cc: pgsql-odbc(at)postgresql(dot)org; Dave Page
> Subject: RE: [ODBC] changed behavior in libpq odbc driver
> 
> That didn't fix it, it still returns HY000.
> 
> This is the error message that comes back:
> 
> FATAL:  terminating connection due to administrator command
> server closed the connection unexpectedly
> This probably means the server terminated abnormally

Odd - it works for me:

	Successfully connected to DSN 'unicode'.
SQLGetInfo:
				In:
ConnectionHandle = 0x003B14B8, InfoType = SQL_DBMS_VER=18, InfoValuePtr
= 0x000A73A0, BufferLength = 600, StringLengthPtr = 0x000ADFD8, 
	
Information Value Type = SQL_C_WCHAR=-8
				Return:	SQL_SUCCESS=0
				Out:			*InfoValuePtr =
"08.01.0004 PostgreSQL 8.0.3 on i686-pc-mingw32, co...",
*StringLengthPtr = 173
SQLExecDirect:
				In:
Statementhandle = 0x003B16C0, StatementText = "SELECT version()",
Statementlength = 16
				Return:	SQL_ERROR=-1
				stmt:		szSqlState = "08S01",
*pfNativeError = 27, *pcbErrorMsg = 169, *ColumnNumber = -2, *RowNumber
= -2
	
MessageText = "Error while executing the query;
server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request."


What steps are you using to repeat the failure at your end? I'm doing:

1) Open connection
2) Call SQLGetInfo and doubly confirm we're connected.
3) Stop the server.
4) Execute a query.

Regards, Dave

pgsql-odbc by date

Next:From: Dave PageDate: 2005-08-31 14:16:31
Subject: Re: changed behavior in libpq odbc driver
Previous:From: Dave PageDate: 2005-08-31 13:08:10
Subject: Re: changed behavior in libpq odbc driver

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