=Date: Thu, 5 Oct 1995 10:49:00 -0700 (PDT)
=From: Alan Goodman <alan@dssmktg.com>
=
=>From Jonathan Leffler:
=>
=>One of the weirder parts of the pre-5.00 ESQL/C implementation is that
=>there was barely any distinction between cursors and statements. This is
=>one of the reasons why you only FREE either the cursor or the statement but
=>not both in pre-5.00 ESQL/C. By contrast, in post-5.00 ESQL/C, and
=>therefore in 6.0x I4GL too, there is a real distinction between the two,
=>and this leads to the problem you found. The lack of distinction in
=>pre-5.00 code is one of the reasons why you get a bunch of unused cursor
=>structures _SQn declared in the file.
=
=Are you saying that in 6.0x 4GL and future version that we will have to
=free both the cursor and the prepared statement?
Yes, if you are concerned about cleaning up all (most) memory, and releasing
the maximum available resources in the servers. In practice, most programs
do not accumulate enough memory for this to be a major problem. But a daemon
server program would probably want to worry about this.
Yours,
Jonathan Leffler (johnl@informix.com) #include <disclaimer.h>