This is a discussion on Re: Windows, ODBC drivers and strange points ... within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto gsql-odbc-owner@postgresql.org] On Behalf Of Marten Feldtmann > Sent: 16 November 2005 ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto > Sent: 16 November 2005 21:41 > To: pgsql-odbc@postgresql.org > Subject: Re: [ODBC] Windows, ODBC drivers and strange points ... > > Perhaps you might remember my tests with > PostgreSQL and IBm VisualAge Smalltalk. > > I mentioned my problems with column lengths > and stuff like this. > > I still testing (from time to time) with > the 8.0.3 database and use the newest > 8.01.00.03 libpq ODBC drivers and now > the situation is getting worse :-(((( > > IBM Smalltalk is now not able to get the > correct column size for strings any more. > > I always get either 254 bytes or 508 bytes > as column size. > > We have a table like: > > create table "TPERSON" ("ALLCSTVIEW" CHAR(1) > .... > > Now IBM Smalltalk calls OdbcSQLDescribeCol > and gets 254 for this column as size in the > return parameter cbPrecision. > > And the alternate call via OdbcSQLColAttribute > with parameter Sql_Column_Lengthreturns 508. > > Actually this is true for ALL string columns > > The PostgreSQL drivers seem strange for me ... > I've done work with other database systems > via this ODBC library, but PostgreSQL does > not give me any real success .... > > If anyone has any help .... Why are you using such an old development snapshot of the driver? Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |