Received: from golem.jpl.nasa.gov (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.1/8.9.1) with ESMTP id VAA17877 for ; Thu, 14 Jan 1999 21:26:35 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost [127.0.0.1]) by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id CAA07199; Fri, 15 Jan 1999 02:26:15 GMT Sender: tgl@mythos.jpl.nasa.gov Message-ID: <369EA745.BA3B2E5C@alumni.caltech.edu> Date: Fri, 15 Jan 1999 02:26:14 +0000 From: "Thomas G. Lockhart" Organization: Caltech/JPL X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.30 i686) MIME-Version: 1.0 To: Byron Nikolaidis CC: applixware-list@applix.com, Postgres Interfaces Mailing List Subject: Re: AWL: postgres odbc woes, continued ....... References: <369D5D0E.AA522E2C@quoll.com> Content-Type: multipart/mixed; boundary="------------4B4E7B65CEE481687E86D367" This is a multi-part message in MIME format. --------------4B4E7B65CEE481687E86D367 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Any thoughts would be greatly appreciated. I'm having trouble running the development tree version of psqlODBC. Picking up the odbc source code from the v6.4 Postgres tarball and inserting it into src/interfaces/odbc gives me back a driver which seems to work. Byron, do you have any ideas on what might have changed? I vaguely recall that the newest code is using v6.4 protocol, and the v6.4 tarball code was using the v6.3.2 protocol?? I've enclosed my log files. TIA - Tom --------------4B4E7B65CEE481687E86D367 Content-Type: text/plain; charset=iso-8859-1; name="mylog_tgl2539.log" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="mylog_tgl2539.log" globals.extra_systable_prefixes =3D 'dd_;' CC_connect: entering... CC_connect(): DSN =3D 'Test', server =3D 'localhost', port =3D '=08', dat= abase =3D 'test', username =3D 'tgl', password=3D'no$way' connecting to the server socket... connection to the server socket failed. CONN ERROR: func=3DSQLConnect, desc=3D'Error on CC_connect', errnum=3D101= , errmsg=3D'Could not connect to the server' **** SQLError: henv=3D0, hdbc=3D134613032, hstmt=3D0 calling CC_get_error enter CC_get_error enter CC_create_errormsg msg =3D 'Could not connect to the server' exit CC_create_errormsg exit CC_get_error CC_get_error: status =3D 101, msg =3D #Could not connect to the server; Could not connect to remote socket.# --------------4B4E7B65CEE481687E86D367 Content-Type: text/plain; charset=us-ascii; name="psqlodbc_tgl2539.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="psqlodbc_tgl2539.log" DSN info: DSN='Test',server='localhost',port='5432',dbase='test',user='tgl',passwd='no$way' readonly='0',protocol='',showoid='',fakeoidindex='',showsystable='' conn_settings='' translation_dll='',translation_option='' conn = 134613032, SQLConnect(DSN='Test', UID='tgl', PWD='no$way') Global Options: Version='06.40.0002', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094 disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0 text_as_longvarchar=0, unknowns_as_longvarchar=0, bools_as_char=1 extra_systable_prefixes='dd_;', conn_settings='' CONN ERROR: func=SQLConnect, desc='Error on CC_connect', errnum=101, errmsg='Could not connect to the server' ------------------------------------------------------------ henv=134613016, conn=134613032, status=0, num_stmts=16 sock=134619360, stmts=134627608, lobj_type=-999 ---------------- Socket Info ------------------------------- socket=-1, reverse=0, errornumber=4, errormsg='Could not connect to remote socket.' buffer_in=134619400, buffer_out=134623504 buffer_filled_in=0, buffer_filled_out=0, buffer_read_in=0 --------------4B4E7B65CEE481687E86D367--