Re: \n converted to \r\n - Mailing list pgsql-odbc

From Dave Page
Subject Re: \n converted to \r\n
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E430687A@ratbert.vale-housing.co.uk
Whole thread Raw
In response to \n converted to \r\n  (amir <amir@binaryreef.com>)
Responses Re: \n converted to \r\n
List pgsql-odbc

> -----Original Message-----
> From: Amir Zicherman [mailto:amir.zicherman@gmail.com]
> Sent: 01 October 2004 18:27
> To: Dave Page
> Cc: Jeff Eckermann; ben.trewern@mowlem.com; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] \n converted to \r\n
>
> Hi, thax for your help.  Took me a while to see where the
> configuration options are because i'm not using a DSN.  I
> then put in a DSN to see if it comes with configuration
> options and found what you guys were talking about.  If i'm
> just using a connection string in my code, is there any way
> to configure this option?  My code needs to be more generic
> than to rely on me settign up DSNs for each database i want
> to connect to.  This is what i'm using to connect in the code:
>
> "DRIVER={" + DB_DRIVER +
>     "};DATABASE=" + dbName_ +
>     ";SERVER=" + dbIP_ +
>     ";PORT=" + dbPort_ +
>     ";UID=" + dbUser_ +
>     ";PWD=" + dbPassword_;
>
> thanx, amir

The easy way to get the connection string is to create a DSN with the
settings you want, switch on the commlog and then connect. The resulting
logfile will show you the full connection string built.

In pgAdmin II which used ODBC, we used to use the following:

DRIVER={PostgreSQL};READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN
=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS=;FETCH=100;SOCKET=409
6;UNKNOWNSIZES=0;MAXVARCHARSIZE=254;MAXLONGVARCHARSIZE=65536;OPTIMIZER=1
;KSQO=1;USEDECLAREFETCH=0;TEXTASLONGVARCHAR=1;UNKNOWNSASLONGVARCHAR=0;BO
OLSASCHAR=1;PARSE=0;CANCELASFREESTMT=0;EXTRASYSTABLEPREFIXES=dd_;

Obviously we would add the database, server, username, password and port
options to that.

Regards,Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: problems with the ODBC driver
Next
From: Mike Fahey
Date:
Subject: default current_timestamp problem