Dirty Read Default

Posted in 2006

Topics: Connectivity: ODBC / JDBC / .NET, Transactions, Locking & Isolation, Platform-Specific Issues, Versions, Editions & End-of-Life

Nick — 11 Apr 2006 12:18:42 -0700 — source: Usenet: comp.databases.informix

I thought I heard a while back about an environment variable setting to change the default isolation level to DR. Does anyone know about this, or maybe I was just dreaming. The users of our data warehouse have been running selects against tables with the default of Committed Read. This is causing (or appears to be causing) some of our insert jobs to fail. The users have only select permission on the tables, which doesn't make since why they would be getting any locks, but I see no other obvious reasons for the inserts to fail. They are usually good at using set isolation to dirty read; But it would be nice if this was just a default for them. ISQL 7.31.UC3 on Solaris 8 and/or ODBC (setnet 2.90.TC3) on windows. IDS 9.40.FC5 on Solaris 8. Does anyone know of an environment variable? Thanks, Nick

↪ replying to Nick

Peter J Diaz de Leon — Tue, 11 Apr 2006 14:39:47 -0500 — source: Usenet: comp.databases.informix

I am having a bit of a problem getting i4gl and isql to work properly work under FC5. i4gl and isql start properly, but when exiting them within a gnome-terminal window the stty environment gets totally messed up. Any thoughts? A regular console (virtual terminal) login works fine. Thanks Peter

↪ replying to Nick

david@smooth1.co.uk — 11 Apr 2006 15:45:41 -0700 — source: Usenet: comp.databases.informix

http://www.smooth1.co.uk/pages/smooth1_my-bulldog_com/ifaq/ifaq04b.htm#4.3.3 SACEISOL="CURSOR STABILITY" export SACEISOL for ACE Reports Similarly SPERISOL for Perform . valid values are: DIRTY READ or dirty read COMMITTED READ or committed read CURSOR STABILITY or cursor stability REPEATABLE READ or repeatable read David.

Glossary

isolation level