On Tuesday, 6 August, 2019 04:27, Olivier Mascia inquired:
>On one database instance, a .dump command gives me (among many other
>lines) things like:
>
>INSERT INTO STATISTICS VALUES(11237795927160,11868);
>
>while the output of .recover command gives me things this way:
>
>INSERT INTO
On 6 Aug 2019, at 7:51pm, Dan Kennedy quoted:
>> INSERT INTO 'STATISTICS'('_rowid_', STATDATE, DISKUSED) VALUES( 1,
>> 11237795927160, 11868 );
Quoting these entity names using apostrophes looks wrong to me. It may work
but someone might read it, know it's official output from a program
On 6/8/62 17:26, Olivier Mascia wrote:
On one database instance, a .dump command gives me (among many other lines)
things like:
INSERT INTO STATISTICS VALUES(11237795927160,11868);
while the output of .recover command gives me things this way:
INSERT INTO 'STATISTICS'('_rowid_',
> Le 6 août 2019 à 14:18, Chris Locke a écrit :
>
>> I got foreign key constraint failures
>
> I don't know why one would work and one would fail, but usually, this
> occurs when you insert a record which has foreign keys to another table,
> but that table hasn't been imported yet. The
> I got foreign key constraint failures
I don't know why one would work and one would fail, but usually, this
occurs when you insert a record which has foreign keys to another table,
but that table hasn't been imported yet. The workaround is usually to
ensure all the 'lookup' tables are done
On one database instance, a .dump command gives me (among many other lines)
things like:
INSERT INTO STATISTICS VALUES(11237795927160,11868);
while the output of .recover command gives me things this way:
INSERT INTO 'STATISTICS'('_rowid_', STATDATE, DISKUSED) VALUES( 1,
6 matches
Mail list logo
