Thanks for the wonderfully simple and concise solution. I see now triggers
do support CTEs if they SELECT a RAISE() function. I never thought of using
a BEFORE trigger.
Fijne kerstdagen
On 24 December 2017 at 17:17, E.Pasma wrote:
> On 24/12/2017 11:56, Shane Dev wrote:
>
> Related to my previo
On 24/12/2017 11:56, Shane Dev wrote:
Related to my previous question
https://www.mail-archive.com/sqlite-users@mailinglists.sqlit
e.org/msg107527.html,
I want to prevent the client from inserting a cycle.
For example -
sqlite> .sch edges
CREATE TABLE edges(parent integer not null, child integ
make child a unique key. so each node can only have 1 parent.
On Sun, Dec 24, 2017 at 6:44 AM, Lifepillar
wrote:
> On 24/12/2017 11:56, Shane Dev wrote:
>
>> Related to my previous question
>> https://www.mail-archive.com/sqlite-users@mailinglists.sqlit
>> e.org/msg107527.html,
>> I want to p
On 24/12/2017 11:56, Shane Dev wrote:
Related to my previous question
https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg107527.html,
I want to prevent the client from inserting a cycle.
For example -
sqlite> .sch edges
CREATE TABLE edges(parent integer not null, child integer
Related to my previous question
https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg107527.html,
I want to prevent the client from inserting a cycle.
For example -
sqlite> .sch edges
CREATE TABLE edges(parent integer not null, child integer not null,
constraint self_reference che
5 matches
Mail list logo