[sqlite] Fw: how are you?

[ronny . dierckx]

Hi friend! 

I've read an article  recently nd it reminded  me  of you, please read  it here 
and tell me your thoughts 


Good wishes, ronny.dierckx
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] not sure

[ronny . dierckx]

Hello friend, 

I'm  not sure whether I should tell  you  that, please read it yourself 


See you around, ronny.dierckx


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] wow, amazing!

[ronny . dierckx]

Yo! 


I've been  looking for some info  on the web  and came across that  amazing 
picture, just  take a look 

Faithfully, ronny.dierckx


___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] fsync/fdatasync problem on UBIFS

[Ronny Dierckx]

>
>Using "PRAGMA journal_mode=truncate" made no difference, the journal
>reappeared with file size > 0.
>
>But "PRAGMA journal_mode=persist" fixes the problem, the database is no
>longer rolled back after a power cut.
>

FYI, 

The problem turned out to be a bug in the UBIFS backport we are using. With
this fixed everything works fine even with default journal mode.

Ronny

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] fsync/fdatasync problem on UBIFS

[Ronny Dierckx]

>> I'm using SQLite 3.6.20 on an ARM Linux device which uses the UBIFS
>> filesystem (on OneNAND flash).
>>
>> When I perform a database update, and cut the power a few seconds  
>> later, the
>> changes are rolled back
>> when the device restarts. This is because after the restart the  
>> journal file
>> has re-appeared in the filesystem.
>> If I perform a manual sync command in the shell before cutting the  
>> power,
>> everything works fine.
>> Does anyone else have experience with running SQLite on UBIFS?
>>
>> Before switching to UBIFS we were using our application on a JFFS2
>> filesystem without any problems.
>
>Not a solution, but you could try experimenting with
>"PRAGMA journal_mode=persist" or "PRAGMA journal_mode=truncate"
>to work around the problem.
>
>Dan.


Using "PRAGMA journal_mode=truncate" made no difference, the journal
reappeared with file size > 0.

But "PRAGMA journal_mode=persist" fixes the problem, the database is no
longer rolled back after a power cut.

Thanks,

Ronny Dierckx


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] fsync/fdatasync problem on UBIFS

[Ronny Dierckx]

Dear list,

I'm using SQLite 3.6.20 on an ARM Linux device which uses the UBIFS
filesystem (on OneNAND flash).

When I perform a database update, and cut the power a few seconds later, the
changes are rolled back
when the device restarts. This is because after the restart the journal file
has re-appeared in the filesystem.
If I perform a manual sync command in the shell before cutting the power,
everything works fine.
Does anyone else have experience with running SQLite on UBIFS?

Before switching to UBIFS we were using our application on a JFFS2
filesystem without any problems.

Thanks,

Ronny Dierckx


___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] get the actual database size.

[Ronny Dierckx]

Hi,

I think a possible solution is to calculate the difference between
the database file size and the number of free pages multiplied by
the page size. This is of course an approximation, but it works for me.

Number of free pages: pragma freelist_count
Page size: pragma page_size 

Ronny

http://www.syntegro.be


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of P Kishor
Sent: vrijdag 30 mei 2008 2:40
To: General Discussion of SQLite Database
Subject: Re: [sqlite] get the actual database size.

On 5/29/08, Joanne Pham <[EMAIL PROTECTED]> wrote:
> Hi All,
>  I have the database which has a lot of insertion and deletion.
>  Is there anyway that I can get the actual database size without running
VACUUM.

Your question implies that VACUUM lets you "get the database size."
No, it doesn't. VACUUM recovers the space left behind by deleting data
from the db.

To find out the size of the database, just read the size of the file
in the operating system.

Or, maybe you are asking something completely different that I don't get.


>  Thanks,
>  JP
>
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Helping with table definition?

[Ronny Dierckx]

Hi,

I think you should look at "PRAGMA table_info(table-name);" instead:

For each column in the named table, invoke the callback function once with 
information about that column, including the column name, data type, whether 
or not the column can be NULL, and the default value for the column.


Ronny



I am wondering if someone did a function (the language doesn't care very
much) to get the table information and want to share him/her code.

I know that you can have the SQL definition of a table doing a "select *
from sqlite_master where type='table' ", but I need to parse SQL and
understand it.



-
To unsubscribe, send email to [EMAIL PROTECTED]
-