I'm sure about 'Id_' presence (it is used successfully in other saving
operations close to UPDATE)
My doubt is about implicit sum:
Gross=Gross+ integer_value
this operation works fine for about 64 consecutive times and then I found
a mismatch.
It seems to be solved only by reducing the spee
Hallo,
I'm working with SQLite rel.3.4.3. on embedded system with ARM processor
(unfortunately I cannot use a more recent release due to customizations on
source code)
I need to update a db of statistics very often,
opening and closing db handle many times, with a short delay between each
upd
On my laptop integrity_check fail
> PRAGMA integrity_check
> returns
>
> *** in database main ***
> rowid 0 missing from index JournalDateIndex
> rowid 0 missing from index sqlite_autoindex_Journal_1
> wrong # of entries in index JournalDateIndex
> wrong # of entries in index sqlite_autoindex_Jour
Sorry,
I cannot run a shell sqlite3 on my embedded system. I will explain it
using your example.
It happen that sometime autoincrement begin to fail
and new records overwrite the one at rowid =1
1|1|2|3|one|two|three replaced by 1|4|2|3|one|two|three
2|2|2|3|one|two|three
3|3|2|3|one|two|three
table definition:
"CREATE TABLE Journal (ClosureNum INTEGER, TicketNum INTEGER, ItemNum
INTEGER, Date DATE, Time TIME, Item BLOB, PRIMARY KEY(ClosureNum,
TicketNum, ItemNum))"
example insert (sorry for cut&paste from my code...):
sprintf(zSql, "INSERT INTO Journal VALUES(%i, %i, %i, '%s', '%s'
creation statement is
"CREATE TABLE Journal (ClosureNum INTEGER, TicketNum INTEGER, ItemNum
INTEGER, Date DATE, Time TIME, Item BLOB, PRIMARY KEY(ClosureNum,
TicketNum, ItemNum))"
Autoincrement seems to work fine
Thanks for your support
Alessandro
From:
Richard Hipp
To:
General Discussio
I'm using SQLite on embedded system (ARM processor)
and DB file is on MMC memory.
Normally INSERT operations of new records works fine. Perhaps,
autoincrement failure is due to electrical pbm and is present only on few
devices
but I'm looking for a way to protect DB file against this pbm.
This
Reindex procedure returns 'no_error'
but rowid=1 is still present 37 times with same values
How can I avoid to fall in this bug?
It's very dangerous because any new INSERT operation terminate
successfully
but previous data has beeen overwrited with new one (on rowid =1)
Many thanks,
Alessandro
schema 3
PRAGMA integrity_check
returns
*** in database main ***
rowid 0 missing from index JournalDateIndex
rowid 0 missing from index sqlite_autoindex_Journal_1
wrong # of entries in index JournalDateIndex
wrong # of entries in index sqlite_autoindex_Journal_1
From:
Richard Hipp
To:
Gener
SELECT rowid FROM (mytable) WHERE (mystuff)
returns
37 identical rows(!) where Rowid = 1
Alessandro
From:
a.azzol...@custom.it
To:
Date:
22/08/2011 16.26
Subject:
Re: [sqlite] Autoincrement failure
sqlite> .dump sqlite_sequence
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
COMMIT;
sq
sqlite> .dump sqlite_sequence
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
COMMIT;
sqlite>
Any idea?
Thanks
Alessandro
From:
Richard Hipp
To:
General Discussion of SQLite Database
Date:
22/08/2011 16.11
Subject:
Re: [sqlite] Autoincrement failure
On Mon, Aug 22, 2011 at 9:56 AM, wrote:
Hallo,
Have you ever seen a SQLite3 DB file with autoincrement algoritm broken?
Every new record seems to be added with rowid=1 overwriting existing
info...
Any idea about the causes of this issue
and about extracting lost data (if present)?
Many thanks
Alessandro
__
I am out of the office until 22/08/2011.
Note: This is an automated response to your message "Re: [sqlite] How to
convert a database with FTS2 to FTS3/4?" sent on 01/08/2011 4.32.58.
This is the only notification you will receive while this person is away.
__
Hallo,
I lost many data in a database where autoindex crashed
and any new record, from this event, has been saved on rowid=1.
Any SELECT about lost data return many rows but identical data. (only
COUNT(rowid) is correct - data is not real)
Is there any tool/way to extract data that appear to b
14 matches
Mail list logo