Re: [sqlite] Parsing sqlitedb file.

2012-07-10 Thread rsharnagate
Hi Simon, Yes, I am working from . This issue encountered for ABPerson table. On Mon, Jul 9, 2012 at 8:34 PM, Simon Slavin-3 [via SQLite] < ml-node+s1065341n63205...@n5.nabble.com> wrote: > > On 9 Jul 2012, at 10:10am, rsharnagate <[hidden >

[sqlite] Format string vulnerability in SQLite

2012-07-10 Thread Yury Maryshev
Dear sirs, We have detected a vulnerabilities in SQLite for OS/2. Vulnerability details can be found in the attachment. Our disclosure policy is available here: http://en.securitylab.ru/lab/disclosure-policy.php -- Yury Maryshev Security Engineer Positive Technologies Tel: +007 (495) 744-0144

Re: [sqlite] Parsing sqlitedb file.

2012-07-10 Thread rsharnagate
Hi Simon, While iterating iPhone Addressbook.sqlitedb pages, I found table records in Table Interior page, but according to sqlite file format only child page offsets and rowids are stored in it. So how is it possible or I am understanding it properly On Mon, Jul 9, 2012 at 8:34 PM, Simon

Re: [sqlite] Format string vulnerability in SQLite

2012-07-10 Thread Richard Hipp
On Tue, Jul 10, 2012 at 3:22 AM, Yury Maryshev wrote: > Dear sirs, > > We have detected a vulnerabilities in SQLite for OS/2. Vulnerability > details can be found in the attachment. > Our disclosure policy is available here: >

[sqlite] SQLite4 key encoding bug

2012-07-10 Thread bardzotajnekonto
SQLite version 4.0.0 2012-07-07 12:21:48 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> create table t(a); sqlite> insert into t values(123); sqlite> insert into t values(123.0); sqlite> insert into t values(12323); sqlite> insert into t values(12323.0); sqlite>

Re: [sqlite] SQLite4 key encoding bug

2012-07-10 Thread Ryan Johnson
On 10/07/2012 9:58 AM, bardzotajneko...@interia.pl wrote: SQLite version 4.0.0 2012-07-07 12:21:48 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> create table t(a); sqlite> insert into t values(123); sqlite> insert into t values(123.0); sqlite> insert into t

Re: [sqlite] SQLite4 key encoding bug

2012-07-10 Thread Igor Tandetnik
On 7/10/2012 11:24 AM, Ryan Johnson wrote: On 10/07/2012 9:58 AM, bardzotajneko...@interia.pl wrote: SQLite version 4.0.0 2012-07-07 12:21:48 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> create table t(a); sqlite> insert into t values(123); sqlite> insert

Re: [sqlite] SQLite4 key encoding bug

2012-07-10 Thread Richard Hipp
On Tue, Jul 10, 2012 at 11:33 AM, Igor Tandetnik wrote: > On 7/10/2012 11:24 AM, Ryan Johnson wrote: > >> On 10/07/2012 9:58 AM, >> bardzotajneko...@interia.pl wrote: >> >>> SQLite version 4.0.0 2012-07-07 12:21:48 >>> Enter ".help" for instructions >>> Enter SQL statements

Re: [sqlite] SQLite4 key encoding bug

2012-07-10 Thread Igor Tandetnik
On 7/10/2012 11:44 AM, Richard Hipp wrote: SQLite4 is still using "double" internally for floating point computations. (Yes, there are plans to change that but it has not happened yet.) The bug above is due to rounding errors in the doubles, specifically rounding errors that occur when doing

Re: [sqlite] SQLite4 key encoding bug

2012-07-10 Thread Richard Hipp
On Tue, Jul 10, 2012 at 11:54 AM, Igor Tandetnik wrote: > On 7/10/2012 11:44 AM, Richard Hipp wrote: > >> SQLite4 is still using "double" internally for floating point >> computations. (Yes, there are plans to change that but it has not >> happened >> yet.) The bug above is

Re: [sqlite] Parsing sqlitedb file.

2012-07-10 Thread Andrew Barnes
> > Message: 6 > Date: Mon, 9 Jul 2012 22:17:02 -0700 (PDT) > From: rsharnagate > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Parsing sqlitedb file. > Message-ID: >

[sqlite] using the SQLITE_BUSY and BEGIN IMMEDIATE

2012-07-10 Thread deltagam...@gmx.net
In http://ideone.com/eWPWD is my example code. I would like to know if this would be an appropiate implemetation/use of BEGIN IMMEDIATE and sqlite3_busy_timeout. As I understood from the documentation and literature about Transaction and locks the sqlite3_step is the action state part so I

Re: [sqlite] using the SQLITE_BUSY and BEGIN IMMEDIATE

2012-07-10 Thread Marcus Grimm
Am 2012-07-10 20:50, schrieb deltagam...@gmx.net: In http://ideone.com/eWPWD is my example code. I would like to know if this would be an appropiate implemetation/use of BEGIN IMMEDIATE and sqlite3_busy_timeout. sqlite3_busy_timeout is specified once per db connection. Probably at the

Re: [sqlite] using the SQLITE_BUSY and BEGIN IMMEDIATE

2012-07-10 Thread Simon Slavin
On 10 Jul 2012, at 7:50pm, "deltagam...@gmx.net" wrote: > sqlite3_busy_timeout(db, 23) e.g. 23 milliseconds is a very little time for a timeout. Even just a hard disk spinning up can take 800 milliseconds. Can I suggest, for testing purposes, that you use a timeout of