Re: what is best way to get the latest libpq version.

________________________________

From: Joel Fradkin [mailto:jfradkin(at)wazagua(dot)com]
Sent: 21 July 2005 14:12
To: Dave Page; pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] what is best way to get the latest libpq
version.

OK I grabbed Connection, Qresult, Results, And convert off csv.

Does that get me up to date using the snapshot as the original
source (also it converted to .net when I opened it and is compiling ok,
so I must of mucky-mucked it up trying to create the project in .net).

Use a CVS client (I use TortoiseCVS) to keep up to date. It's the only
way you know for sure you are up to date. Also, compile from the command
line using the win32.mak makefile e.g. " nmake /f win32.mak ". Doing it
in the GUI will be more tricky as you won't necessarily get the build
settings right (even I didn't when I tried the other day). You may need
to run vcvars32.bat to setup the VC++ environment. Finally, use VC++ 6
if you have it. .NET may make you dependent on newer versions of the
runtime libraries that we haven't tested.

/D

On my freshly compiled libpq version, is debug=1 supposed to be working?

Any clue where I should look to see why I always get a catastrophic error
when I enable it?

Catastrophic failure is returned from my connection object with a connection
string of:

DRIVER={PostgreSQL};DATABASE=wazuni;SERVER=192.168.123.252;PORT=5432;UID=pos
tgres;PWD=1brain;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=0;RowV
ersioning=0;ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSi
zes=0;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debug=1;CommLog=0;Optimizer
=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;Bool
sAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;LFConversion=
1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarB
inary=0;UseServerSidePrepare=0

Works ok without debug, but I am trying to isolate errors in my app.

Joel Fradkin

Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305

jfradkin(at)wazagua(dot)com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.

-----Original Message-----
From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
Sent: Thursday, July 21, 2005 9:24 AM
To: Joel Fradkin; pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] what is best way to get the latest libpq version.

_____

From: Joel Fradkin [mailto:jfradkin(at)wazagua(dot)com]
Sent: 21 July 2005 14:12
To: Dave Page; pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] what is best way to get the latest libpq version.

OK I grabbed Connection, Qresult, Results, And convert off csv.

Does that get me up to date using the snapshot as the original source (also
it converted to .net when I opened it and is compiling ok, so I must of
mucky-mucked it up trying to create the project in .net).

Use a CVS client (I use TortoiseCVS) to keep up to date. It's the only way
you know for sure you are up to date. Also, compile from the command line
using the win32.mak makefile e.g. " nmake /f win32.mak ". Doing it in the
GUI will be more tricky as you won't necessarily get the build settings
right (even I didn't when I tried the other day). You may need to run
vcvars32.bat to setup the VC++ environment. Finally, use VC++ 6 if you have
it. .NET may make you dependent on newer versions of the runtime libraries
that we haven't tested.

/D