On 23/09/2010 11:52 p.m., Richard Hipp wrote:
>> Josh Gibbs wrote:
>>> CREATE TABLE Message (message_id INTEGER PRIMARY KEY AUTOINCREMENT,
>>> Subject TEXT);
>>> CREATE TABLE MessageRecipient (message_id INTEGER REFERENCES
>>> Message(message_id) ON DELETE CASCADE, recipient_ID INTEGER REFERENCES
Josh Gibbs wrote:
> On 23/09/2010 3:15 p.m., Igor Tandetnik wrote:
>> You could do something like
>>
>> delete from Recipient where recipient_ID = old.recipient_ID and
>>recipient_ID not in (select recipient_ID from MessageRecipient);
>>
>
> That was the last idea we had as well. Trouble
On Wed, Sep 22, 2010 at 11:15 PM, Igor Tandetnik wrote:
> Josh Gibbs wrote:
> > CREATE TABLE Message (message_id INTEGER PRIMARY KEY AUTOINCREMENT,
> > Subject TEXT);
> > CREATE TABLE MessageRecipient (message_id INTEGER REFERENCES
> > Message(message_id) ON DELETE CASCADE, recipient_ID INTEGER R
On 23/09/2010 3:15 p.m., Igor Tandetnik wrote:
> Josh Gibbs wrote:
>> CREATE TABLE Message (message_id INTEGER PRIMARY KEY AUTOINCREMENT,
>> Subject TEXT);
>> CREATE TABLE MessageRecipient (message_id INTEGER REFERENCES
>> Message(message_id) ON DELETE CASCADE, recipient_ID INTEGER REFERENCES
>>
Josh Gibbs wrote:
> CREATE TABLE Message (message_id INTEGER PRIMARY KEY AUTOINCREMENT,
> Subject TEXT);
> CREATE TABLE MessageRecipient (message_id INTEGER REFERENCES
> Message(message_id) ON DELETE CASCADE, recipient_ID INTEGER REFERENCES
> Recipient(recipient_id));
> CREATE TABLE Recipient (rec
Hi all, I'm hoping someone can assist me with a problem I'm having
creating a cascading delete operation as well as a constraint.
This table is an example of the layout of my data:
CREATE TABLE Message (message_id INTEGER PRIMARY KEY AUTOINCREMENT,
Subject TEXT);
CREATE TABLE MessageRecipient
6 matches
Mail list logo