Re: [sqlite] Auto Index Warnings; key on deterministic functions

On Tue, Feb 6, 2018 at 2:24 AM, J Decker wrote: > create table tableA ( pk PRIMARY KEY, dataA ) > create table tableB ( fk, dataB, FOREIGN KEY (fk) REFERENCES tableA(pk) ON DELETE CASCADE ) > > if the table was also ON UPDATE CASCADE could it slave to the same index > as

Re: [sqlite] Auto Index Warnings; key on deterministic functions

--- > The fact that there's a Highway to Hell but 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 J Decker > >Sent: Monday,

Re: [sqlite] Auto Index Warnings; key on deterministic functions

>boun...@mailinglists.sqlite.org] On Behalf Of J Decker >Sent: Monday, 5 February, 2018 18:24 >To: General Discussion of SQLite Database >Subject: [sqlite] Auto Index Warnings; key on deterministic functions > >I have a couple tables like... > >create table tableA ( pk PRIM

[sqlite] Auto Index Warnings; key on deterministic functions

I have a couple tables like... create table tableA ( pk PRIMARY KEY, dataA ) create table tableB ( fk, dataB, FOREIGN KEY (fk) REFERENCES tableA(pk) ON DELETE CASCADE ) if the table was also ON UPDATE CASCADE could it slave to the same index as primary key? doing a LEFT JOIN on the tables I