Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Interfaces Odbc > How to force an...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 1 Topic 2342 of 2384
Post > Topic >>

How to force an Option?

by Michael.Knigge@[EMAIL PROTECTED] (Michael Knigge) Apr 16, 2008 at 01:38 PM

All,

yesterday we've discovered a little problem with our application within
a bunch of statements, like

BEGIN
SELECT ...
UPDATE ...
SELECT ...
UPDATE ...
COMMIT

we've discovered that the ODBC-Driver issues a ROLBACK when doing a
SQLPrepare() for the second SELECT - and so the first UPDATE will never
hit the database.

After playing around we've discovered that everything is ok if we enable
"Server Side Prepare" or "Disallow Premature".

Now the question is: Is it possible to force this options? Something
like a "SET server_site_prepare = 1;" after the connection is established?

Or is it possible to check if this option is in effect (so I could abort
the application with an error message)? Currently we do a SQLConnect()
so we don't have a Connect-String that could be parsed for an option...


Thank you for any help,
Michael



-- 
Sent via pgsql-odbc mailing list (pgsql-odbc@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc
 




 1 Posts in Topic:
How to force an Option?
Michael.Knigge@[EMAIL PRO  2008-04-16 13:38:57 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan13V112 Thu Jul 24 7:07:29 CDT 2008.