Problems in ODBC driver - Mailing list pgsql-interfaces
From | richard clark |
---|---|
Subject | Problems in ODBC driver |
Date | |
Msg-id | 4.2.0.58.20000221144353.00cb5d20@pop.elysium.ltd.uk Whole thread Raw |
List | pgsql-interfaces |
Thanks in advance for any feedback.... I have just installed the latest version I can find of the ODBC driver for Windows for PostgreSQL 6.40.0008. I have tried accessing PostgreSQL on two machines. Version is 6.5.2 This is implemented on a Windows 98 second edition system - all the ODBC DLLs seem to be 3.510.3711. It apparently installs correctly, and I can specify a data source in the ODBC applet - the advanced options show up and can be changed. If I specify an incorrect database name or invalid username/pw I get the correct prompts. If I am not authenticated to use the database in pg_hba.conf, I am told so correctly. If I do have access to the database and everything is apparently correct then poof... a GPF... MSQRY32 caused a stack fault in module PSQLODBC.DLL at 017f:016b5247. Anyone got any ideas - this even happens with the Template1 default database. Below is the psqlodbc.log trace... conn=23986296, SQLDriverConnect( in)='DSN=PostgreSQL;', fDriverCompletion=1 DSN info: DSN='PostgreSQL',server='192.168.1.68',port='5432',dbase='mmsig',user='nobod y',passwd='' readonly='1',protocol='6.4',showoid='0',fakeoidindex='0',showsyst readonly='1',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='0' conn_settings='' translation_dll='',translation_option='' Global Options: Version='06.40.0008', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=8190 disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0 text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1 extra_systable_prefixes='dd_;', conn_settings='' conn=23986296, query=' ' conn=23986296, query='set DateStyle to 'ISO'' conn=23986296, query='set geqo to 'OFF'' conn=23986296, query='set ksqo to 'ON'' conn=23986296, query='select oid from pg_type where typname='lo'' the SQL.LOG file doesn't seem meaningful last few entries in it are.. msqry32 fff7d88f:fff60507 ENTER SQLAllocConnect HENV 0x00d3ff1c HDBC * 0x0060ed88 msqry32 fff7d88f:fff60507 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS) HENV 0x00d3ff1c HDBC * 0x0060ed88 ( 0x00c402f4) msqry32 fff7d88f:fff60507 ENTER SQLSetConnectOption HDBC 0x00c402f4 UWORD 103<SQL_LOGIN_TIMEOUT> UDWORD 45 msqry32 fff7d88f:fff60507 EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS) HDBC 0x00c402f4 UWORD 103 <SQL_LOGIN_TIMEOUT> UDWORD 45 msqry32 fff7d88f:fff60507 ENTER SQLDriverConnectW HDBC 0x00c402f4 HWND 0x0000079c WCHAR * 0x1f4be068 [ -3] "******\ 0" SWORD -3 WCHAR * 0x1f4be068 SWORD 8 SWORD * 0x00000000 UWORD 1 <SQL_DRIVER_COMPLETE> FWIW, I can access the database using the Zeus Windows app.....but a select * from users gives incorrect results in part of the table (a number of columns duplicate a userid column raher than containing the correct value). Selecting individual columns with a select column from table query works though.... Richard Clark: richard@elysium.ltd.uk Elysium Ltd, Crowborough, UK - JPEG Editor and WebMaster 'Let standard-authors, thus, like trophies borne - The Dunciad Appear more glorious as more hacked and torn' ;<{) - Alexander Pope (1688-1744)
pgsql-interfaces by date: