Re: First record status inconsistent using SQLite

2006-05-30 Thread Devin Asay
Noted and voted. DNA On May 28, 2006, at 3:35 AM, David Vaughan wrote: On 28/05/2006, at 1:24, Devin Asay wrote: OTOH, documentation errors are easy to fix. I recently stumbled across a minor doco error in one of the revDB functions and submitted it to BZ. Lo and behold it showed up as

Re: First record status inconsistent using SQLite

2006-05-28 Thread David Vaughan
On 28/05/2006, at 1:24, Devin Asay wrote: OTOH, documentation errors are easy to fix. I recently stumbled across a minor doco error in one of the revDB functions and submitted it to BZ. Lo and behold it showed up as fixed in the next 2.7.x release. You should submit it for sure. I would

Re: First record status inconsistent using SQLite

2006-05-27 Thread Devin Asay
On May 26, 2006, at 10:21 PM, David Vaughan wrote: On 27/05/2006, at 12:30, Kay C Lan wrote: ... ...BUT once you move away from these, moving back to them using 'previous' or 'next' will not result in them be recognised, you need to try an move past them, then they'll be recognised. I

First record status inconsistent using SQLite

2006-05-26 Thread David Vaughan
Using Rev 2.7.1 with AltSqlite/SQLite 3, I found inconsistent behaviour (as I see it) with the function revdb_isbof alias RevCurrentRecordIsFirst. Let us assume you find a record set comprising one record. -- revdb_isbof will be true (expected) -- revdb_iseof will be false (not expected)

Re: First record status inconsistent using SQLite

2006-05-26 Thread Jan Schenkel
--- David Vaughan [EMAIL PROTECTED] wrote: Using Rev 2.7.1 with AltSqlite/SQLite 3, I found inconsistent behaviour (as I see it) with the function revdb_isbof alias RevCurrentRecordIsFirst. Let us assume you find a record set comprising one record. -- revdb_isbof will be true

Re: First record status inconsistent using SQLite

2006-05-26 Thread David Vaughan
On 26/05/2006, at 19:02, Jan Schenkel wrote: I remember an old discussion about when exactly you were at the end of a cursor: on the last record, or after you call revdb_movenext on the last record? FoxPro seemed to think that the EOF() was _after_ the last record, not on it. I do not

Re: First record status inconsistent using SQLite

2006-05-26 Thread Kay C Lan
On 5/26/06, Jan Schenkel [EMAIL PROTECTED] wrote: I remember an old discussion about when exactly you were at the end of a cursor: on the last record, or after you call revdb_movenext on the last record? FoxPro seemed to think that the EOF() was _after_ the last record, not on it. I

Re: First record status inconsistent using SQLite

2006-05-26 Thread David Vaughan
On 27/05/2006, at 12:30, Kay C Lan wrote: ... ...BUT once you move away from these, moving back to them using 'previous' or 'next' will not result in them be recognised, you need to try an move past them, then they'll be recognised. I recognise it but it leaves me thinking that the old