|Subject||RE: [Firebird-Architect] Kicking users off the system|
> >Create aThere is no special granting thing necessary, if you use
> >new user and get them all to connect under that instead.
> This sounds to me like a lot of fuss and bother for nothing. That means
> that I'll constantly have to be maintaining the grants for an
> all-powerful user, so as to make sure that it always says all-powerful.
> If I want it be all-powerful, why not use SYSDBA, which is already
another user when creating the database *and* the database
objects. The owner of database objects automatically has
all rights. No granting necessary.
Why not use SYSDBA? Ever thought about deplyoing your app
to a site where Firebird is already installed and you don't
get your hands on the SYSDBA's password?
It's a good choice that each database and its database objects
has a separate owner and on top of that, you can implement
a security model based on roles with ease.
Due to our FBOwnerMigrator tool, we know that people regret
their choice at a later point of using SYSDBA as database
Just a thought.
LogManager Serie - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database and MS SQL Server