23.05.2018 15:07, Adriano dos Santos Fernandes wrote:
On 23/05/2018 08:51, Vlad Khorsun via Firebird-devel wrote:
23.05.2018 13:40, Adriano dos Santos Fernandes wrote:
On 23/05/2018 06:48, Dimitry Sibiryakov wrote:
In this case I guess there must be two triggers: BEFORE RESET and
AFTER RESET.
I like this more than the other approaches.
I strongly suggest to consider existing DISCONNECT\CONNECT triggers
also. I think, most of the code will be the same in both set of events
therefore it is very questionable if we need another pair of triggers.
Yes, but for me it seems as a hack. User can always do a single SP and
call it on both triggers.
Hmm... do you consider INSERT OR UPDATE OR DELETE triggers as hack also ?
I have an idea with I think is good.
What if RESET resets not to the initial (before ON CONNECT) state, but
to the state present after ON CONNECT?
It means we should know what changes was made by ON CONNECT trigger.
I.e. we need to save names and values of context variables, save values
of session properties and save contents of GTT's.
Looks overkill for me.
So ON CONNECT can define context variables that is not reset.
You mean - all context variables in USER_SESSION namespace that was
assigned by ON CONNECT trigger ? Or you speak about some way to mark
context variables as "DON'T RESET" ?
Regards,
Vlad
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
