On Mon, Mar 28, 2011 at 08:55:28PM +0530, Sudha Venkatareddy scratched on the
wall:
> Dear Jay,
> Please check the below source code from Amalgamation file and suggest me
> which section of the code is critical and what happens during execution of
> each of the APis called within Sqlire3RunVacuum
Dear Jay,
In the course of execution of Sqlite3RunVacuum() API, total 4 new files will
be created. 3 temporary files and 1 journal file.
Since my main DB file name is "MyDb.db", the journal file which is created
is "MyDb.db-journal"
I observed that there was no failure in sqlite3_io_methods API s
Hi,
As per the link http://www.sqlite.org/lang_vacuum.html , SQLite claims that
"*The VACUUM command works by copying the contents of the database into a
temporary database file and then overwriting the original with the contents
of the temporary file*." In this phrase "*The VACUUM command works
Hi,
I fixed the code in such a way that the temp files which are created with
below flags are deleted during close.
dwFlagsAndAttributes = FILE_ATTRIBUTE_TEMPORARY
| FILE_ATTRIBUTE_HIDDEN
| FILE_FLAG_DELETE_ON_CLOSE;
so..
* Pro
Hi,
The porting is done in little tricky way due to limited support from
underlying platform.
Ported code does not completely follow WINDOWS. it is WINDOWS + WINCE
configuration.
Porting is done as below.
*Step 1.* Main macros defnined in the source include:
#define SQLITE_DEBUG 0
#define SQL
Make sure your antivirus is turned off when you run your vacuum test.
It's a long-shot, but I've seen some AVs lock files etc...
> Date: Wed, 23 Feb 2011 10:14:15 -0600
> From: j...@kreibi.ch
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Problem with VACUUM featu
On Wed, Feb 23, 2011 at 11:50:05AM +0530, Sudha Venkatareddy scratched on the
wall:
> Hi All,
>
> Input:MyDb.db with size 23KB (has lot of empty pages caused due to delete
> operation)
>
> *Expected OutPut: after applying Vacuum command, should be MyDb.db with
> reduced file size of 13KB.*
>
>
Hi-
On Windows, SQLite uses the FILE_FLAG_DELETE_ON_CLOSE flag to have
temporary files automatically deleted after they are closed. WINCE
doesn't support this flag, so you will see special logic in os_win.c,
wrapped in #ifdef SQLITE_OS_WINCE, for handling the deletion of these
files. You mention
Hi,
I referred the link http://www.sqlite.org/cvstrac/tktview?tn=2829
it is slightly related to it but the temporary files are created while
running VACUUM command.
---
Ticket 2829:
This patch seems to fix it (added: SQLITE_OPEN_DELETEON
On 23 Feb 2011, at 6:11am, Sudha Venkatareddy wrote:
> *Actual output: MyDb.db remains size 23KB(size not changes from original)
> and creates temporary file etilqs_Hm4RUi6JPXcMZ17 whose data is same as
> MyDb.db but the size is reduced to 13KB*
Your problem is probably related to
http://www.sq
Hi All,
I am using sqlite-amalgamation-3_7_3.zip source in my project.
I tested VACUUM command on a DB file which has lot of holes(fragmentation
caused by deletion of random records ) but the source file size does not
change. Instead sqlite applies the vaccum command and writes data into new
tempo
Hi All,
I am using sqlite-amalgamation-3_7_3.zip source in my project.
I tested VACUUM command on a DB file which has lot of holes(fragmentation
caused by deletion of random records ) but the source file size does not
change. Instead sqlite applies the vaccum command and writes data into new
tempo
12 matches
Mail list logo
