Re: The PUT Command is better than EXECUTE Insert?

> Bashir Akram <bash@bash.demon.co.uk> writes: > When a program needs to do hundreds of inserts into a table, rather than > Executing an Insert Cursor, it is better to use PUT. > (from a performance point of view?) > > Comments? Opinions? Problems? > > Thought I would ask before we start re-coding our programs. Start recoding, it's much faster. Be aware of a small issue if you use a serial column and need it's value immediately after a put. It isn't available in the sqlca-structure until you do a flush (or a flush happens automatically). We have found put to be faster, even with a flush for every record to get the serial value, than other alternatives, although we haven't realy tested it extensively. Nils.Myklebust@ccmail.telemax.no NM-data, Dalsbergstien 7, N-0170 Oslo, Norway My opinions are those of my company