|Subject||Re: [firebird-support] Re: Set custom value on connection system info|
Hi.I see no difference. You join your custom table with MON$Attachments and you are safe here because if user is not logged you have not row in mon$table.E.g. you have tableWorker with fieldsIdNameAge...User_nameAnd you joinSelect * from mon$attachments A inner join workers W where A.mon$user=W.user_nameRegards,Karol Bieniaszewski-------- Oryginalna wiadomość --------Data: 06.02.2018 08:13 (GMT+01:00)Temat: Re: [firebird-support] Re: Set custom value on connection system infoHi,I wouldn't store in a standard table because I couldn' intercept the crash or forced logoff.If I join context var with the connection I absolute safe who are actually connected.2018-02-05 21:16 GMT+01:00 'livius' liviuslivius@... [firebird-support] <firebird-support@yahoogroups. com>:
I know that you solved your problem.But why you store ID from your custom table into context varnot oposite USER_NAME in your custom user table? Then you do not need var at all.regards,Karol Bieniaszewski
Wow, thanks!This is what I really wantedI never known the existence of that system table.Actually I use RDB$SET_CONTEXT for store user name and id; with this table I could know the user really logged inThanks Dmitry2018-02-04 13:46 GMT+01:00 Dmitry Yemanov dimitr@... [firebird-support] <firebird-support@yahoogroups. com>:
03.02.2018 23:14, marco andreolli wrote:
> but RDB$SET_CONTEXT() it's not right for me, because it store
> information in actual connection (or transaction) and they can not be
> read out of this (with a monitor program for example).
It can be, via MON$CONTEXT_VARIABLES.