Path: emory!swrinde!cs.utexas.edu!uunet!snorkelwacker.mit.edu!apple!uokmax!munnari.oz.au!deakin.OZ.AU!rand!auzodt3!shaneb
From: shaneb@auzodt3.mel.cocam.oz.au (Shane Booth)
Newsgroups: comp.databases.informix
Message-ID: <515@rand.mel.cocam.oz.au>
Date: 14 Oct 91 06:56:18 GMT
Sender: usenet@rand.mel.cocam.oz.au
Organization: Co-Cam Computer Group, Melbourne, OZ
Came across an interesting one the other day. When we try to run the following
code (with 64 insert statements), the program crashes on the CREATE INDEX with
error -257, system limit on cursors exceeded... But an INSERT statement isn't
a cursor declaration! Also, placing a single SELECT statement before the
CREATE INDEX seems to make the whole thing work fine! Why should it makeany difference? We run the Rapid Development System v4.00.UC1 on SCO Unix.
DATABASE test
MAIN
CREATE TEMP TABLE t1 (f1 INTEGER, f2 INTEGER) WITH NO LOG
INSERT INTO tab001(field001) VALUES ("xxx")
{ repeat above INSERT 63 more times }
CREATE INDEX temp1 ON t1(f1)
END MAIN
Is it OK to create indexes on temporary tables?
Also, are there any known bugs involving temporary tables? I'd be interested
in any other traps that may be lurking just around the corner...
Shane Booth: shaneb@auzodt3.mel.cocam.oz.au