From cec668d7fd6bda991a186ce8ee9dc4f2db4bfff4 Mon Sep 17 00:00:00 2001 From: robocop Date: Tue, 3 Feb 2009 10:41:54 +0000 Subject: [PATCH] Misc. --- doc/README.incompatibilities.txt | 2 +- doc/README.services_extension | 6 +++--- doc/README.superclassic | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/README.incompatibilities.txt b/doc/README.incompatibilities.txt index 84a1fde757..804a743aee 100644 --- a/doc/README.incompatibilities.txt +++ b/doc/README.incompatibilities.txt @@ -67,7 +67,7 @@ API SECURITY -------------------------- - * Members of administrative windows groups are not mapped to SYSDBA any more + * Members of administrative Windows groups are not mapped to SYSDBA any more by default. Mapping is controlled on per-database basis using SQL command ALTER ROLE RDB$ADMIN SET/DROP AUTO ADMIN MAPPING. See README.trusted_authentication for details. diff --git a/doc/README.services_extension b/doc/README.services_extension index ad442afdc9..3b10ea5198 100644 --- a/doc/README.services_extension +++ b/doc/README.services_extension @@ -35,9 +35,9 @@ password are set using some other method): (Alex Peshkov, peshkoff@mail.ru, 2008) Nbackup performs two logical groups of operations - locking/unlocking database -and backup/restore it. It's absolutely no use duplicating locking/unlocking in -services, cause that functionality is present remotely in much better from any -point of view SQL language interface (ALTER DATABASE). But backup and restore +and backup/restore it. It's doesn't make sense duplicating locking/unlocking in +services, cause that functionality is present remotely in much better (from any +point of view) in SQL language interface (ALTER DATABASE). But backup and restore must be run on localhost and the only way to access them is nbackup utility. Therefore expanding services API with this functionalty is very useful. diff --git a/doc/README.superclassic b/doc/README.superclassic index 64410af917..b5a787ee30 100644 --- a/doc/README.superclassic +++ b/doc/README.superclassic @@ -39,7 +39,7 @@ The drawbacks are the following: * Somewhat ineffective memory usage (same as for Classic) * High lock table contention (due to page locks), so it requires careful tuning - the lock manager confuguration (again, same as for Classic) + the lock manager configuration (again, same as for Classic) * Server crash affects all user attachments (same as for SuperServer)