./showdb my-db dbheader
Pagesize: 4096
Available pages: 1..745888
000: 53 51 4c 69 74 65 20 66 6f 72 6d 61 74 20 33 00 SQLite format 3.
010: 10 00 01 01 00 40 20 20 00 00 0b 7a 00 0b 61 a0 .@ ...z..a.
020: 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 04
030: 00 00 00 00 0
On 7/28/16, Youngjoon Lee wrote:
>
> ./showdb my-db 5
>
Thank you.
Can you also please send the result of "./showdb my-db dbheader" and
the result of "sqlite3 my-db .schema"
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users
./showdb my-db 5
Pagesize: 4096
Available pages: 1..745888
Page 5: (offsets 0x4000..0x4fff)
: 0d 00 00 00 01 0e 0d 00 0e 0d 00 00 00 00 00 00
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..
On 7/28/16, 이영준 wrote:
>
> For sqlite_sequence table, the hex dump of the problematic entry is like
> below.
> The rootpage of sqlite_sequence resides in page 5.
Please get the original SQLite source tree and run "make showdb" .
Then run the commands:
./showdb your-database 5
./showdb yo
On 7/28/16, Richard Hipp wrote:
> On 7/28/16, 이영준 wrote:
>> The title ["string or blob too big" issue on a corrupted db] may not
>> clear
>> for you.
>> Let me describe my situation.
>>
>> I have a problematic database.
>> It has two of tables which have a huge entry approximately 1.45GB.
>> They
On 7/28/16, 이영준 wrote:
> The title ["string or blob too big" issue on a corrupted db] may not clear
> for you.
> Let me describe my situation.
>
> I have a problematic database.
> It has two of tables which have a huge entry approximately 1.45GB.
> They are sqlite_sequence and log table.
The defa
The title ["string or blob too big" issue on a corrupted db] may not clear
for you.
Let me describe my situation.
I have a problematic database.
It has two of tables which have a huge entry approximately 1.45GB.
They are sqlite_sequence and log table.
Here are output from sqlite3 shell.
-
> D. Richard,
It is very good clue for us to check the page size on the src and dest db.
Thank you very much for the help!
jp
> On Jul 28, 2016, at 3:49 PM, Richard Hipp wrote:
>
> On 7/28/16, Richard Hipp wrote:
>> On 7/28/16, Jian Ping Yan wrote:
>>> HI,
>>>
>>> We update SQLite3 versio
On 7/28/16, Richard Hipp wrote:
> On 7/28/16, Jian Ping Yan wrote:
>> HI,
>>
>> We update SQLite3 version to 3.13.0.
>>
>> After running sqlite3_backup_step(), the return value is 8, which said
>>
>> ret[8] Error message: [attempt to write a readonly database].
>>
>> is any clue?
>
> Is the desti
On 7/28/16, Jian Ping Yan wrote:
> HI,
>
> We update SQLite3 version to 3.13.0.
>
> After running sqlite3_backup_step(), the return value is 8, which said
>
> ret[8] Error message: [attempt to write a readonly database].
>
> is any clue?
Is the destination database an in-memory database that has
HI,
We update SQLite3 version to 3.13.0.
After running sqlite3_backup_step(), the return value is 8, which said
ret[8] Error message: [attempt to write a readonly database].
is any clue?
thanks in advance!
jp
___
sqlite-users mailing list
sqli
On 7/28/16, Java4Life wrote:
> Hi All,
>
> I think there is a comma missing here:
>
> Here: https://www.sqlite.org/fts3.html#section_4_2
Please confirm that the draft document for the next release
(http://sqlite.org/draft/fts3.html#section_4_2) fixes the problem you
see. Thanks.
--
D. Richard
Hi All,
I think there is a comma missing here:
Here: https://www.sqlite.org/fts3.html#section_4_2
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 7/28/16, Gerry Kleinpenning wrote:
> The following SQL create table statement is accepted:
This is an "undocumented feature". Really it is a bug in prior
versions of the SQLite parser. But we have to maintain this bug
moving forward to avoid breaking database files that might actually be
usi
The following SQL create table statement is accepted:
CREATE TABLE CST_PAGE_z (
PAGE_ID INTEGER PRIMARY KEY,
PAGE_MASTER INTEGER NOT NULL,
PAGE_DETAIL INTEGER NOT NULL,
PAGE_HIDDEN BOOLEAN NOT NULL DEFAULT 0,
FOREIGN KEY(PAGE_MASTER) REFERENCES CST_TABLE(TABLE_ID) ON DELETE CA
Hello
thank you for your prompt answer and fix.
I've jus tested the 3.14 pre-release and now all work right
follows the explain query result with 3.14 (OK)
explain query plan SELECT
...> pupdate,idinstrum,Vlnsys,Vl1n,Vl2n,Vl3n,Vllsys,Vl1l2,Vl2l3,Vl3l1,
...> Al1,Al2,Al3,kWsys,kWl1,kWl2,kW
On 26.07.2016 12:53, Dan Kennedy wrote:
The corrupt database thing is unexpected, of course. It might be fixed
here:
http://sqlite.org/src/info/483994a54dee3c7a
Please let us know if you get the chance to try the fix above with your
databases.
I confirm that the fix solves the problem repo
17 matches
Mail list logo
