Re: 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?
От | Dave Page |
---|---|
Тема | Re: 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? |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9445@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответы |
Re: debug=1 supposed to be working? Any clue where I should
Re: debug=1 supposed to be working? Any clue where I should |
Список | pgsql-odbc |
From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Joel Fradkin
Sent: 21 July 2005 15:18
To: pgsql-odbc@postgresql.org
Subject: [ODBC] 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?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=postgres;PWD=1brain;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debug=1;CommLog=0;Optimizer=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;LFConversion=1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;UseServerSidePrepare=0
Works ok without debug, but I am trying to isolate errors in my app.
Works for me. Does the user account under which your app is running have permission to create and write files to C:\ ?
Regards, Dave.
В списке pgsql-odbc по дате отправления: