Hi Khizar,
I am guessing you found the note about config.ing in a
document in our knowledge base about the Intersolv ODBC driver.
This is for a very old version of ingres, config.ing was replaced by
config.dat and we stopped using the Intersolv driver at about Ingres 2.0.
I am going update these KB documents!
You have not actually said what version of Ingres or
ODBC you are using - that is always a good thing to include when asking a
question like this.
If you want to set the lockmode permanently on the
server, issue this command (on
the server):
ingsetenv ING_SET "set lockmode session where
readlock=nolock"
If you want to set the lockmode dynamically
from within the client application, use the ODBC API
SQLSetConnectOption ('set lockmode session
where readlock=nolock') or SQLExecDirect ('set lockmode session where
readlock=nolock')
If you
have any problems with the above, feel free to log a support
issue.
Hope
this helps.
Thanks and
regards,
Russell Neal
Technical Consultant
Ingres
Corporation
russel...@ingres.com
PHONE
1800 614 435
www.ingres.com
This transmission is
confidential and intended solely for the use of the recipient named above. It
may contain confidential, proprietary, or legally privileged information. If you
are not the intended recipient, you are hereby notified that any unauthorized
review, use, disclosure or distribution is strictly prohibited. If you have
received this transmission in error, please contact the sender by reply e-mail
and delete the original transmission and all copies from your
system.