Subject | Dabase Owner Privileges changed in Firebird 2.1? |
---|---|
Author | ruan_h |
Post date | 2010-09-24T04:19:37Z |
Hi
When we used to run Firebird 1.5 and 2.0, if a user other than the owner of the database creates a table but doesn't grant any permissions to the database owner, then the owner can't read/update/delete the table, can't drop the table, and can't grant permissions on this table. This is all as expected.
Now that we upgraded to 2.1, I recently noticed that in the same scenario, the database owner can now read/update/delete the table, and even drop the table. This doesn't seem right to me. Also, it's inconsistent that the owner can drop the table but still can't grant permissions on it.
I couldn't find any reference to this in the release notes. Could someone please explain why this was changed? Thanks.
We're running classic on Linux, but I get the same behaviour on Windows.
Thanks
Huan
When we used to run Firebird 1.5 and 2.0, if a user other than the owner of the database creates a table but doesn't grant any permissions to the database owner, then the owner can't read/update/delete the table, can't drop the table, and can't grant permissions on this table. This is all as expected.
Now that we upgraded to 2.1, I recently noticed that in the same scenario, the database owner can now read/update/delete the table, and even drop the table. This doesn't seem right to me. Also, it's inconsistent that the owner can drop the table but still can't grant permissions on it.
I couldn't find any reference to this in the release notes. Could someone please explain why this was changed? Thanks.
We're running classic on Linux, but I get the same behaviour on Windows.
Thanks
Huan