Holding Locks?

Path: emory!ogicse!henson!n8420101 From: n8420101@henson.cc.wwu.edu (Chris A. Hopen) Newsgroups: comp.databases.informix Summary: Need to hold locks even after commit work! Message-ID: <1991Oct18.015545.29600@henson.cc.wwu.edu> Date: 18 Oct 91 01:55:45 GMT Organization: Western Washington University Posted: Thu Oct 17 18:55:45 1991 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 and cursors defined without the "WITH HOLD" clause are closed! I could attempt to go re-aquire the locks again but there is no guarantee that I will get them! I can't change the transaction logging params from within ESQL/C code nor would I want to. I would like to somehow use the informix locks because it seems more elegant and easier to do. If anyone has run into this problem or one similar, PLEASE let me know asap before I go off writing some unnessary locking functions on top of the standard UNIX file system .... Thanks in advance! Chris Hopen Email: n8420101@henson.cc.wwu.edu USmail: Geographic Technology 301 Telegraph Rd. Bellingham WA 98226