Re: How to change default isolation adn wait mode

lclee@nntp.best.com (Lin-Chuan Lee) wrote: :Our databases have committed read isolation and lock mode to not wait. :Is there any means of changing this ?? I certainly am aware :of isolation/lock modes in my ESQL/C programs and I know :you can do passthrough SQL in VB ( most client apps implented :in this) to set iso/lock modes. However, maintaining discipline :is not always there. Also, there are reporting programs :(Business Objects) and other "technologies" that attach :to the database that really IMHO should have at least :dirty read isolation. This is but one of the many reasons why you should use the openlink ODBC driver. We haven't realy started using this part of its functionallity yet. I have only had time to read the manual on this part so far. So this is from the manual: It obviously have options to set up these things. You can create a file of sql-commands to be executed whenever a session is started. You can differentiate it by user, application and several other parameters. Dirty read for reporting programs becomes easy. Have Informix even thought of the necessity for things like these in I-Net/CLI? Nils.Myklebust@idg.no <- New E-mail adress NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company