> On 3 Jan 2016, at 6:52pm, Richard Hipp wrote:
>
> On 1/3/16, Simon Slavin wrote:
>>
>> I've seen references to imposter tables in the SQLite comments. What is an
>> imposter table ?
>
> An undocumented and unsupported feature that allows two or tables in
> the schema to refer to the same
On 03-01-16 00:11, richard parkins wrote:
> An INSERT statement which fails with no explicit conflict clause appears to
> throw away a pending SAVEPOINT.
> The following sequence demonstrates this behaviour
> SAVEPOINT demonstration;
> CREATE TABLE IF NOT EXISTS "PK" ( "first name" "TEXT",
>
On 3 Jan 2016, at 5:49pm, Richard Hipp wrote:
> /* Make sure every column of the PRIMARY KEY is NOT NULL. (Except,
> ** do not enforce this for imposter tables.) */
I've seen references to imposter tables in the SQLite comments. What is an
imposter table ?
Simon.
On 1/3/16, Simon Slavin wrote:
>
> On 3 Jan 2016, at 5:49pm, Richard Hipp wrote:
>
>> /* Make sure every column of the PRIMARY KEY is NOT NULL. (Except,
>> ** do not enforce this for imposter tables.) */
>
> I've seen references to imposter tables in the SQLite comments. What is an
>
On 1/3/16, Luuk wrote:
>
>
> On 03-01-16 00:11, richard parkins wrote:
>> An INSERT statement which fails with no explicit conflict clause appears
>> to throw away a pending SAVEPOINT.
>> The following sequence demonstrates this behaviour
>> SAVEPOINT demonstration;
>> CREATE TABLE IF NOT EXISTS
An INSERT statement which fails with no explicit conflict clause appears to
throw away a pending SAVEPOINT.
The following sequence demonstrates this behaviour
SAVEPOINT demonstration;
CREATE TABLE IF NOT EXISTS "PK" ( "first name" "TEXT",
"last name" "TEXT",
"address",
PRIMARY KEY ( "first name",
6 matches
Mail list logo
