On 09-02-2021 17:48, Alex Peshkoff via Firebird-devel wrote:
I do wonder about this case. Specifically, why am I not able to
execute SET ROLE TESTROLE in this case? According to the mapping I'm
allowed to use this role.
According to SQL specification set role shall fail if user is not
I'm working on the Firebird 3 Language Reference, and I'm currently
writing documentation for SET TRUSTED ROLE. I have tried reading the
Firebird 3 release notes, and a Google-translated version of the Russian
Firebird 3 Language Reference, but the meaning and intent of this
feature is unclear
On 2/9/21 5:42 PM, Mark Rotteveel wrote:
I'm working on the Firebird 3 Language Reference, and I'm currently
writing documentation for SET TRUSTED ROLE. I have tried reading the
Firebird 3 release notes, and a Google-translated version of the
Russian Firebird 3 Language Reference, but the
On 09-02-2021 15:52, Alex Peshkoff via Firebird-devel wrote:
On 2/9/21 5:42 PM, Mark Rotteveel wrote:
I'm working on the Firebird 3 Language Reference, and I'm currently
writing documentation for SET TRUSTED ROLE. I have tried reading the
Firebird 3 release notes, and a Google-translated
On 2/9/21 7:01 PM, Mark Rotteveel wrote:
On 09-02-2021 16:23, Mark Rotteveel wrote:
In other words, does my confusion derive from the fact the Firebird 3
release notes say that CREATE MAPPING ... TO ROLE ... updates the
CURRENT_ROLE, while in fact it does no such thing?
Having done some
On 2/9/21 6:23 PM, Mark Rotteveel wrote:
CREATE MAPPING WIN_ADMINS
USING PLUGIN WIN_SSPI
FROM Predefined_Group DOMAIN_ANY_RID_ADMINS
TO ROLE RDB$ADMIN
```
While SET AUTO ADMIN MAPPING will apply RDB$ADMIN automatically if no
explicit role is specified on connect.
In other words, does
On 09-02-2021 16:23, Mark Rotteveel wrote:
In other words, does my confusion derive from the fact the Firebird 3
release notes say that CREATE MAPPING ... TO ROLE ... updates the
CURRENT_ROLE, while in fact it does no such thing?
Having done some further tests, a mapping will actually set
