Ah, thanks Dean. Yes, CloseCursor (or SQLCloseCursor) is it. I think I'll probably leave finish() unchanged until I get into thinking about fetch_scroll(), caching result sets, and cursor libraries. Then rename it to fit in with however those work out.
Tim. On Mon, Jul 01, 2002 at 01:53:33PM -0700, Dean Arnold wrote: > The one I'm most familiar with is the JDBC > spec, specifically ResultSet.close() > (and I guess Statement.close() is similar as > well). > > And of course, one could argue that, after > execute(), $sth is just a cursor handle, > and "CLOSE <cursorname>" > has been the standard SQL way to close a > cursor for years (decades ?), > regardless whether the > resultset had been completely consumed > or not. > > Can't recall the ODBC syntax off the top of my > head, tho I think its something like > CloseCursor() ?? > > Regards, > Dean Arnold > > On Mon, 1 Jul 2002 21:33:36 +0100 Tim Bunce <[EMAIL PROTECTED]> wrote: > > Can you point me to a reference that shows close() doing exactly > what finish() does? > > Tim. > > On Mon, Jul 01, 2002 at 07:28:15AM -0700, Dean Arnold wrote: > > Perhaps just $sth->close() is sufficient ? This would mimic > > most other API's syntax... > > > > Dean Arnold > > > > > > > > > > > >I'll probably rename finish() to something like > > discard_unfetched_rows(). > > > > >(Keeping an alias for old code of course.) > > > > > > > > I guess I got the idea from this sentence in perldoc DBI: > > > > > > > > The `finish' method should have been called `cancel_select'. > > > > > > I keep changing what I want to rename it to - which is why I haven't > > > renamed it yet :) > > > > > > I think discard_unfetched_rows is the most descriptive and least > > > ambiguous one I've come up with yet. > > > > > > Tim. > > >
