Re: Holding Locks?

> In article: posted 10/28/91 discussion between David Cortesi > and Chris Hopen. > > > I am using Infomix OnLine 4.0 and ESQL/C under DG/UX 4.31 > and have a unique problem. I have a group of 4 tables that I > want to lock and keep locked until I am done with all the processing > I need to perform. The first part (i.e Locking the tables) is quite > simple, but my question is how do I keep them locked when I am accessing > a database that uses logging? In (I believe) all SQL databases when > you "commit work" all row-level and table-level locks are released... > > > The very little that you say about your problem is enough to raise > red flags, ring alarm bells, sound sirens etc. in my mind. You make me > very dubious about the design you are attempting. Please post a more > complete description of what you are doing and why this unusual locking > is needed. Maybe other readers can suggest an alternate design that > avoids these problems. I have been interested in doing this same or similar thing. We have a job that runs at night out of cron. This program locks 23 tables and then proceeds to delete, update, insert into different tables depending on program logic loop ( kind of convoluted ). The tables contain anywhere from 1 to 150,000 rows. After @ 7 hours of running, the program blows off. (informix turbo w/ buffered log) I suggested placing a commit work that would clear buffers and assure us that some amount of work is getting done. This commit would be kicked off by a counter after 1000 rows of a critical table has been processed. We are in the process of writing and testing it. I'll post a message if and when we finish. ************************************************************************** STANDARD DIsCLAIMERS Brian MacWilliams APPLY USAMC SIMA L. E. A. D. CHAMBERSBURG, PA **************************************************************************