Re: CLOSE and FREE

Posted in 1995

"Andy Kent" — Sun, 22 Jan 1995 21:41:22 GMT — source: Informix-list mailing list archive (1991-1998)

> FREE clears the program memory resources as well as engine resources; > you can OPEN a cursor that was previously CLOSEd, but you have to > DECLARE the cursor again if you FREE it. If you FREE a cursor does it FREE the associated prepared statement? And vice versa? What releases active set memory - close or free? Why was it decided that SELECT should do an implied FREE, thereby making it necessary for it to be re-parsed and optimised the next time it's invoked? If it wasn't for this, un-prepared SELECTs would go so much faster. akent@cix.compulink.co.uk (Andy Kent) -------------------------------------