Re: -266 Error When Logging Is Enabled

However you should not that the default isolation level in a 4GL app is different in non logged databases from logged database. Non logged is dirty read, logged databases I think is committed read. As a result you may have some issue with concurrency if you do not specify an isolation level in your 4GL code. Abhishek Mathur wrote: > Hi, > I think what you are hitting is a server bug. A bug for this was > reported and fixed. PTS - 172334. > > Bug Description - ERROR -266 WHEN UPDATING A ROW FETCHED BY A > CURSOR DECLARED FOR UPDATE AND WITH HOLD. > > The bug was fixed for the 7.31.UD9, 9.40.xC8 and 10.00.xC4 > servers. Please contact Tech Support to provide you a patch with the right > fix. > > This does not seem to be a 4GL issue and you should still be able > to use the existing 4Gl scripts as is. > > Thanks and Regards, > > > Abhishek Mathur > Advisory Software Engineer > > IBM - Information Management > 913-599-7109 (T/L - 337-7109) > abhishek@us.ibm.com > > > > > > Adam Tauno Williams <adam@morrison-ind.com> > Sent by: owner-informix-list@iiug.org > 11/01/2005 01:50 PM > > To > informix-list@iiug.org > cc > > Subject > -266 Error When Logging Is Enabled > > > > > > > I have some 4GL applications that where written with a database with > logging disabled and I would like to enable logging on that database. > However when I do so the 4GLs still work so long as you don't attempt to > modify data; as soon as you attempt to modify data you get an "-266 > There is no current row for UPDATE/DELETE cursor." error. Turning > database logging back off (of course) resolves the problem. > > Are these 4GLs a lost cause or is there some work-around? > sending to informix-list > > [demime 1.01d removed an attachment of type image/jpeg] > sending to informix-list