Karl Forner wrote:
> On Tue, Dec 19, 2017 at 3:12 PM, Clemens Ladisch wrote:
>> Where does the hex number in "excluded_mice_temp2b5036f270" come from?
>> Is it random?
>
> Yes, thanks, I think I got it. In order to alter tables, we first move them
> to a new table with a temp name, copy them, then
On Tue, Dec 19, 2017 at 3:12 PM, Clemens Ladisch wrote:
> Karl Forner wrote:
> > Here's a screenshot of some of the diffs using vbindiff
> >
> > https://ibb.co/kNm0X6
>
> SQLite uses hash tables for schema objects, so different names might
> result in such differences.
>
> Where does the hex numb
>
> PRAGMA integrity_check;
>
all ok
>
>
>
> Simon.
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite
Karl Forner wrote:
> Here's a screenshot of some of the diffs using vbindiff
>
> https://ibb.co/kNm0X6
SQLite uses hash tables for schema objects, so different names might
result in such differences.
Where does the hex number in "excluded_mice_temp2b5036f270" come from?
Is it random?
Regards,
C
On 19 Dec 2017, at 1:30pm, Karl Forner wrote:
> and the dumps usign the .dump sqlite3.exe command are also identical.
Paul has a better chance of understanding the hex dump than I do, but what I
think I’m seeing is trivial differences in file organisation. In other words
some pieces of data a
only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Karl Forner
>Sent: Tuesday, 19 December, 2017 06:30
>To: SQLite mailing list
>Subject: Re: [sqlit
and the dumps usign the .dump sqlite3.exe command are also identical.
On Tue, Dec 19, 2017 at 2:19 PM, Karl Forner wrote:
> > Using the sqlite3 shell tool please give the command
> > SELECT * FROM sqlite_master;
>
> the results are identical
>
> table|_meta|_meta|2|CREATE TABLE "_meta"("TABL
> Using the sqlite3 shell tool please give the command
> SELECT * FROM sqlite_master;
the results are identical
table|_meta|_meta|2|CREATE TABLE "_meta"("TABLENAME" TEXT NOT NULL ,
"COLNAME" TEXT NOT NULL , "VARNAMES" TEXT , "LABELS" TEXT , "PREFS"
TEXT , PRIMARY KEY(TABLENAME,COLNAME))
On 19 Dec 2017, at 12:43pm, Karl Forner wrote:
> All the software in the docker container. so it is exactly the same version
> of all software and libraries, except the linux kernel. Moreover the
> differences are not in the header, rather interspersed with what looks like
> CREATE statements.
Thanks for your reply.
All the software in the docker container. so it is exactly the same version
of all software and libraries, except the linux kernel. Moreover the
differences are not in the header, rather interspersed with what looks like
CREATE statements.
On Tue, Dec 19, 2017 at 1:40 PM,
SQLite stores the verison number of the librrary in the database header.
Different SQlite libraries on different computers would cause this error.
Paul
www.sandersonforensics.com
skype: r3scue193
twitter: @sandersonforens
Tel +44 (0)1326 572786
http://sandersonforensics.com/forum/content.php?195-S
11 matches
Mail list logo
