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

Re: IM004-unixODBC

From: Ludek Finstrle <luf(at)pzkagis(dot)cz>
To: juanudo(at)galeon(dot)com
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: IM004-unixODBC
Date: 2006-03-22 12:06:28
Message-ID: 20060322120628.GI6294@soptik.pzkagis.cz (view raw or flat)
Thread:
Lists: pgsql-odbc
Hello

Tue, Mar 21, 2006 at 08:57:35PM +0100, juanudo(at)galeon(dot)com napsal(a):
> I'm work on:
>           S.O.: Linux Suse 9.2
> PostgreSQL: 8
>   unixODBC: 2.2.10-3

I see no psqlodbc version.

> When a try to connect to PostgreSQL with ODBC:
> isql PostgreSQL user password -v
> 
> suse:/etc/unixODBC # cat odbc.ini
> [ODBC Data Sources]
> PostgreSQL              = PostgreSQL ODBC 2.50 
> Driver DSN
> 
> [PostgreSQL]
> Description             = PostgreSQL
> Driver                    = PostgreSQL
> Trace                     = Yes
> TraceFile                = /tmp/sql.log
> Database                = GESTION
> Servername              = 167.175.51.178
> Username                = postgres
> Password                = XXXXXXXXXXXXX
  ^^^^^^^^
Don't include password next time.

> Port            = 5432
> Protocol                = 6.4
> ReadOnly                = No
> RowVersioning           = No
> ShowSystemTables                = No
> ShowOidColumn           = No
> FakeOidIndex            = No
> ConnSettings            =
> FileUsage               = 1

You could try add Debug = 1 and then you can see more in /tmp/*mylog*.
If there is no /tmp/*mylog* you have bad definition of psqlodbc driver.

Regards,

Luf

In response to

Responses

pgsql-odbc by date

Next:From: Bart SamwelDate: 2006-03-22 12:20:38
Subject: Re: Most recent driver aborts transaction after one error
Previous:From: Ludek FinstrleDate: 2006-03-22 12:00:58
Subject: Re: newline in varchar causing funny behavior?

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