On 01/02/2013 03:27 PM, Marco ten Thije wrote:
On 12/21/2012 05:18 PM, Dan Kennedy wrote:
Thanks. I think it's this:
http://www.sqlite.org/src/info/0cfd98ee20
Dan.
Thanks. I have looked into ticket, but we also see this problem when the
backup is written and read by the
same SQLite version (3.7.5).
I have recreated a backup using the 3.7.5 version. These are the
hexdumps of both the original file and
the backup created with SQLite 3.7.5:
The original file:
0000000 5153 694c 6574 6620 726f 616d 2074 0033
0000010 0004 0101 4000 2020 0000 f1d0 0000 7600
0000020 0000 9700 0000 2100 0000 0300 0000 0100
0000030 0000 0000 0000 0000 0000 0100 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
0000050 0000 0000 0000 0000 0000 0000 0000 0200
0000060 2d00 1de2 000d 0000 0004 00e3 7202 2002
0000070 7301 e300 0000 0000 0000 0000 0000 0000
0000080 0000 0000 0000 0000 0000 0000 0000 0000
What series of commands did you pass to 3.7.5 to create
this file?
That the change counters at byte offsets 24 and 92 are
different makes this file look like it was created using
3.7.5 and then populated using an older version.
Perhaps there is a bug in 3.7.5 causing this. What happens
if you use 3.7.15 to create the original and do the backup?
Dan.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
