Matthias,
Are you by chance using the VACUUM command on your data?
I just noticed an update on the sqlite website that says:
--------------------------------
2007-Jly-20 - Version 3.4.1
This release fixes a bug in VACUUM that can lead to database
corruption. The bug was introduced in version 3.3.14. Upgrading is
recommended for all users. Also included are a slew of other more
routine enhancements and bug fixes.
--------------------------------
Something else to look out for....
GregO
On Jul 29, 2007, at 5:46 am, Matthias Buercher wrote:
> is there a limit of rows in an RealSQLdatabase.
>
> i have added more than 100'000 rows to a database, but i cannot tell
> even any more how many they are.
>
> select count(messageid) from mails
> returns no recordset
>
> select messageid from limit 0,100000
> returns a recordset with 100'000 rows
>
> select messageid from mails limit 10000,100000
> returns a recordset with 100'000 rows
>
> select messageid from mails limit 15000,100000
> returns no recordset
>
> select messageid from mails limit 0,114233
> returns 114233 rows
>
> select messageid from mails limit 114230,5
> returns no recordset
>
>
> it looks like that there is a corrupted row.
> is it likely that a RealSQLdatabase goes corrupt and how can it be
> avoided?
>
> how can i find the corrupted row?
>
> matthias
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|