Re: ODBC Driver Options - Mailing list pgsql-odbc
From | Andrew Ayers |
---|---|
Subject | Re: ODBC Driver Options |
Date | |
Msg-id | 40A911FB.6080505@eldocomp.com Whole thread Raw |
In response to | ODBC Driver Options ("Nicola Tiling" <nti@w4w.net>) |
Responses |
Re: ODBC Driver Options
|
List | pgsql-odbc |
Jeff Eckermann wrote: > --- Dave Page <dpage@vale-housing.co.uk> wrote: > >>Hi, >> >>It's not as up to date as it should be, but most >>options are documented >>at >> > > http://gborg.postgresql.org/project/psqlodbc/genpage.php?doc-config > >>Regards, Dave. >> >> >>>-----Original Message----- >>>From: Nicola Tiling [mailto:nti@w4w.net] >>>Sent: 17 May 2004 11:12 >>>To: pgsql-odbc@postgresql.org >>>Subject: [ODBC] ODBC Driver Options >>> >>>Hi >>> >>>I have installed psqlodbc-07_03_0200 for Windows >> >>(under XP). >> >>>I use it for M$ Access as a frontend of a pg >> >>database on a >> >>>FreeBSD Server. >>> >>>Can anyone tell me where I can find any documents >> >>about the >> >>>options of the driver? I have searched under >>> >> > http://gborg.postgresql.org/project/psqlodbc/projdisplay.php > >>>and http://techdocs.postgresql.org. The document >>> >> > "ftp://ftp.postgresql.org/pub/odbc/psqlodbc_confighelp.html" > >>>doesn't exist anymore. >>> >>>I would be lucky to know what >>> >>>- Use Declare/Fetch >>>- Parse Statements >>>- Cancel as FreeStmt(Exp) >>>- Row Versioning >>>- Disallow Premature >>>- Server side prepare >>> >>>mean and what are the effects of them? > > > Since you are using MS Access, you will probably avoid > some problems by setting "row versioning" to true. > Also, some people have reported big performance gains > from setting "use declare/fetch" to true, so you may > want to test that. I am not aware that any of those > other options will give you any benefit with other > than default values. A related question would be what the "name" of these variables are if you are passing them in a DSN-less connection. For example, I was having problems in my VB6 application where if I didn't turn off Keyset Query Optimization I would get errors. This is easy to do in the ODBC setup, but in order to do it via a DSN-less connection, you have to pass "ksqo=;" in the connection string. In this case, it is fairly easy to guess - but what about others, like "use declare/fetch"? I would love to try this out in my application, but without knowing what variable to pass - it would take a little to track down (likely a before/after snapshot of a log, while using a DSN connection and turning off/on the flag to see what changes in the log entries). A list of these variables and what their settings can be would be doubly helpful... Andrew Ayers Phoenix, Arizona >>>Excuse my bad english >>>Regards >>>Nicola >>> >>> >>> >>>---------------------------(end of >>>broadcast)--------------------------- >>>TIP 9: the planner will ignore your desire to >> >>choose an index >> >>>scan if your >>> joining column's datatypes do not match >>> >> >>---------------------------(end of >>broadcast)--------------------------- >>TIP 9: the planner will ignore your desire to choose >>an index scan if your >> joining column's datatypes do not match > > > > > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! - Internet access at a great low price. > http://promo.yahoo.com/sbc/ > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > -- CONFIDENTIALITY NOTICE -- This message is intended for the sole use of the individual and entity to whom it is addressed, and may contain informationthat is privileged, confidential and exempt from disclosure under applicable law. If you are not the intendedaddressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy,disclose or distribute to anyone the message or any information contained in the message. If you have received thismessage in error, please immediately advise the sender by reply email, and delete the message. Thank you.
pgsql-odbc by date: