Subject | RE: [Firebird-Architect] On connect/disconnect trigger |
---|---|
Author | Dimitry Sibiryakov |
Post date | 2006-06-02T06:51:02Z |
On 2 Jun 2006 at 9:12, Dmitry Yemanov wrote:
useful if they include connection params.
Consider these examples:
IF(OLD.ROLE = 'NONE') THEN
NEW.ROLE = 'SIMPLE_USER';
SELECT RDB$CHARSET FROM RDB$DATABASE INTO :NEW.CHARSET;
--
SY, Dimitry Sibiryakov.
>tracker. But I'm not sure I like the term "trigger" in this context.Not sure about before connect, but OLD and NEW contexts could be
>Such an object has enough semantical differences from a regular
>trigger. It doesn't have OLD/NEW contexts, it doesn't make sense to
>have before connect/after disconnect triggers, etc.
useful if they include connection params.
Consider these examples:
IF(OLD.ROLE = 'NONE') THEN
NEW.ROLE = 'SIMPLE_USER';
SELECT RDB$CHARSET FROM RDB$DATABASE INTO :NEW.CHARSET;
--
SY, Dimitry Sibiryakov.