Is that a Bug or R:Base Restriction for triggers? There is no information about using Triggers and Integrity Constraints!
I have Table1 with T1_ID primary key and INSERT trigger to insert a row into Table2. I should set Foreign Key in Table2 references to the Table1.T1_ID. R:Base gives error, because this is AFTER trigger and there is NO �such row in Table1.� I cannot say if this is a Bug, or rbase Restriction, or setting problem. If this is a Restriction, please provide documentation about Triggers versus Integrity Constraints! Moreover, there is no information what type of trigger is current AFTER TRIGGER. Is that Row trigger or Statement trigger? A row trigger is fired each time the table is affected. For example, if an UPDATE statement updates multiple rows of a table, a row trigger is fired once for each row affected by the UPDATE statement. A statement trigger is fired once, regardless of the number of rows in the table that the triggering statement affects. This information is important if you try to handle errors by trigger�s procedure! I think that using of triggers required good documentation about: - Triggers versus Integrity Constraints and Rules - Modifying updateable views by trigger�s procedure - User access and Data access - Connection between triggers, TRANSACT ON, and Data access - Connection between triggers, SET QUALCOLS, and Data access Konstantin Gudjev _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
