] SQLITE_CORRUPT error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/10/2010 04:07 PM, daksh jasra wrote:
> I have ported SQLITE over VRTX based embedded platform,
I'd suggest licensing the TH3 test suite in order to verify your port. You
could be doing something like getting an operati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/10/2010 04:07 PM, daksh jasra wrote:
> I have ported SQLITE over VRTX based embedded platform,
I'd suggest licensing the TH3 test suite in order to verify your port. You
could be doing something like getting an operating wrong once the database
Hey Guy's,
I have ported SQLITE over VRTX based embedded platform, now after using for a 1
year suddenly started getting SQLITE_CORRUPT ERORR, used queue and mutex at
application level to make sqilte DB access thread safe as sqlite library itself
is compiled without thread safe options, Strange
So I'm gonna find this fix in the 3.6.16 version right?
I'd like to avoid to download it directly from cvs...
D. Richard Hipp ha scritto:
> On Jun 23, 2009, at 3:16 AM, Andrea Galeazzi wrote:
>
>
>> Any news about this problem?
>>
>
> http://www.sqlite.org/cvstrac/tktview?tn=3929
>
>
>>
On Jun 23, 2009, at 3:16 AM, Andrea Galeazzi wrote:
> Any news about this problem?
http://www.sqlite.org/cvstrac/tktview?tn=3929
> galea...@korg.it ha scritto:
>
> In order to be more confidence about what I'm saying, I downloaded the
> precompiled sqlite console 3.6.15 (windows version), I ex
Any news about this problem?
galea...@korg.it ha scritto:
In order to be more confidence about what I'm saying, I downloaded the
precompiled sqlite console 3.6.15 (windows version), I executed the
statement above and I've got the following error:
sqlite3.exe malformed_db.db
SQLite version 3.
Citando "D. Richard Hipp" :
>
> On Jun 18, 2009, at 12:36 PM, galea...@korg.it wrote:
>
>> This statement is giving me truoble:
>> INSERT INTO PlayList_Song(id_song, id_playlist, song_number) VALUES
>> (5235, 9, 256)
>
> That INSERT statement works fine for me.
>
> Did you try recompiling with opt
On Jun 18, 2009, at 12:36 PM, galea...@korg.it wrote:
> This statement is giving me truoble:
> INSERT INTO PlayList_Song(id_song, id_playlist, song_number) VALUES
> (5235, 9, 256)
That INSERT statement works fine for me.
Did you try recompiling with optimizations turned off?
D. Richard Hipp
This statement is giving me truoble:
INSERT INTO PlayList_Song(id_song, id_playlist, song_number) VALUES
(5235, 9, 256)
Citando "D. Richard Hipp" :
>
> On Jun 18, 2009, at 9:04 AM, galea...@korg.it wrote:
>
>> I updated sqlite version from 3.6.14 to 15, now when I try to run a
>> C++ code to fil
On Jun 18, 2009, at 9:04 AM, galea...@korg.it wrote:
> I updated sqlite version from 3.6.14 to 15, now when I try to run a
> C++ code to fill the database I have SQLITE_CORRUPT error.
Even with your new database that uses NOCASE in place of KORGCOLLATE,
I don't have any problems.
What query,
On Jun 18, 2009, at 9:04 AM, galea...@korg.it wrote:
> I updated sqlite version from 3.6.14 to 15, now when I try to run a
> C++ code to fill the database I have SQLITE_CORRUPT error.
Works fine when I run it with your database.
I cannot access any of the indices, though, since I lack the
KOR
On Jun 18, 2009, at 11:01 AM, galea...@korg.it wrote:
> I run "PRAGMA integrity_check" using version 3.6.14 at the end of the
> code and it executed a query with only one row "ok", so where do I
> have to send the databbase?
d...@sqlite.org
>
> Thanks
>
> Citando "D. Richard Hipp" :
>
>>
>> On
I run "PRAGMA integrity_check" using version 3.6.14 at the end of the
code and it executed a query with only one row "ok", so where do I
have to send the databbase?
Thanks
Citando "D. Richard Hipp" :
>
> On Jun 18, 2009, at 9:04 AM, galea...@korg.it wrote:
>
>> I updated sqlite version from 3
On Jun 18, 2009, at 9:04 AM, galea...@korg.it wrote:
> I updated sqlite version from 3.6.14 to 15, now when I try to run a
> C++ code to fill the database I have SQLITE_CORRUPT error.
New logic was added to version 3.6.15 to detect database corruption
sooner.
What happens when you run "PRAGMA
I updated sqlite version from 3.6.14 to 15, now when I try to run a
C++ code to fill the database I have SQLITE_CORRUPT error. This error
happens in the accessPayload method (btree.c) in the condition
if( rc==SQLITE_OK && amt>0 ){
return SQLITE_CORRUPT_BKPT;
}
where rc is SQLITE_OK but amt
On Thu, 3 Jan 2008 13:52:03 -0500, "Griggs, Donald"
<[EMAIL PROTECTED]> wrote:
>Maybe this is implied, but you might also try to .DUMP tables
>*invididually* if .DUMP'ing the entire database fails.
I didn't think of that, but yes, that is a good suggestion.
I hope it helps the original poster.
--
Regarding:
>>I suspect the answer is no, but is there any way to salvage any of the
data?
>You could try the .dump command in the command line tool, but I'm
afraid you're out of luck.
Maybe this is implied, but you might also try to .DUMP tables
*invididually* if .DUMP'ing
Hi Doug,
On Wed, 2 Jan 2008 21:47:45 -0600, "Doug" <[EMAIL PROTECTED]>
wrote:
>I have a customer that has a database that has somehow become corrupted.
>I'm fairly certain he was on v3.4.1 but I'll double check. The database
>isn't completely bad, I can look at the master table and one of the tw
I have a customer that has a database that has somehow become corrupted.
I'm fairly certain he was on v3.4.1 but I'll double check. The database
isn't completely bad, I can look at the master table and one of the two
tables in the database. But if the second table is touched SQLITE_CORRUPT
is retur
19 matches
Mail list logo
