Re: C-ISAM: should we use it?

Path: emory!sol.ctr.columbia.edu!spool.mu.edu!cs.umn.edu!dege From: dege@cs.umn.edu (Dege Jeffrey Charles) Newsgroups: comp.databases.informix Message-ID: <1991Sep24.051929.26342@cs.umn.edu> Date: 24 Sep 91 05:19:29 GMT References: <1991Sep23.042632.4884@redsox.bsw.com> <wvhcx6@lynx.unm.edu> Organization: University of Minnesota, Minneapolis, CSci dept. In <wvhcx6@lynx.unm.edu> ewise@cie.uoregon.edu (Edwin Wise) writes: >But it doesn't support NFS, so be careful about your networks. >We found that for our "convenience" C-ISAM remembers the various information >about files when you open them the first time (with a virtual file system) >and makes it difficult to change the way you want to access a table (such >as changing locking or transaction modes). We've been using C-ISAM under MsDOS, and this virtual close has proven extremely irritating. isclose() doesn't close a file, it "virtually" closes it, meaning that if you can't normally depend upon having file descriptors available for any other use. Informix has a function, in the MsDOS vcersion, at least, called isvclose(), that is NOT documented. You pass it an integer that sets the maximum number of isam files that will be "virtually" closed (that is, actually held open despite your isclose() call.) We add a call to isvclose(0) at the beginning of every program. If this function is available with your version, and you weren't aware of it, it might help with your problem. ------------------------- We don't need no steenkin .sigs.