On Tue, 11 Dec 2007 15:37:52 +0530, "Yuvaraj Athur Raghuvir"
<[EMAIL PROTECTED]> wrote:
>Thanks.
>
>To ensure that the database size is closest to the data in the database, I
>see the following have to be taken care off:
>a) The latest in-memory transactions have to be flushed to disk.
>How?
>b)
Thanks.
To ensure that the database size is closest to the data in the database, I
see the following have to be taken care off:
a) The latest in-memory transactions have to be flushed to disk.
How?
b) The space has to be reclaimed after delete/drop.
For this I use the PRAGMA VACUUM statement.
On Dec 11, 2007, at 3:00 PM, Yuvaraj Athur Raghuvir wrote:
1) Can I assume that MAX_PAGE_COUNT * PAGE_SIZE = size of file on
disk?
No. It is the maximum size of the file. An attempt to
insert data that would cause the file to grow larger than
this will return SQLITE_FULL.
2) When insert
1) Can I assume that MAX_PAGE_COUNT * PAGE_SIZE = size of file on disk?
2) When insert statements are being executed, I would like to - for example
- redirect the queries to another data base when 70% of the space is
reached. How can I do that?
~Yuva
On Dec 11, 2007 11:48 AM, Dan <[EMAIL
On Dec 11, 2007, at 8:39 AM, Yuvaraj Athur Raghuvir wrote:
Hello,
I am trying a simple experiment where I want to limit the size of
the file
that SQLite uses. Further, I want to manage the growth of the
database(s)
explicitly.
One of the first aspects I want to manage is the size of the
Hello,
I am trying a simple experiment where I want to limit the size of the file
that SQLite uses. Further, I want to manage the growth of the database(s)
explicitly.
One of the first aspects I want to manage is the size of the file on the
disk. I want to set hard limits on the size and during
6 matches
Mail list logo
