Re: Foxpro goto command and deleted records
Carl Karsten <[email protected]>
| Newsgroups | gmane.comp.python.db |
|---|---|
| Message-ID | <CADmzSSiNVBpwpLDVJThpJO0GMb_YZtBbhSRX183iyyY-K+egjw@mail.gmail.com> |
On Tue, Jul 17, 2012 at 5:46 PM, Ethan Furman <[email protected]> wrote: > In Foxpro if you do a > > GOTO 7 > > with deleted off and record 7 is deleted, the record pointer doesn't move > (at least in version 6). > > I don't like that. > > I see four other options: > > 0) don't move the pointer (listed for completeness) > 1) go to that record anyway > 2) go to the next undeleted record > 3) go to the seventh undeleted record (possibly the least practical) > 4) raise an exception > > Any opinions? dBase/FoxPro had a PURGE command which would actually de-alocate the space used for the deleted record. It also had the concept of a record pointer that related to the data on disk. Neither is at all part of the SQL spec, and I doubt has anything to do with python's dbapi. So my opinion is this isn't an issue. -- Carl K _______________________________________________ DB-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/db-sig