Seagate ST43401N/ND Guida di Installazione Pagina 50

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 146
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 49
If Your Version is 11.5
42
Workarounds
If deadlocks are creating problems, consider converting the table to use
datarows locking.
If deadlocks or excessive numbers of locks are creating problems, consider
using the lock table command to acquire an exclusive table lock before you
begin the transaction.
Changes to Error Checking
As of version 11.5.1, ASE performs more rigorous checking of permissions-
related access to database objects. This change was not documented in 11.5
documentation. The changes may affect the behavior of applications that test
for specific error codes and those that perform auditing of failed permissions.
The types of changes include the following:
Some permission checks that used to be performed at compile time are
now delayed until execution time. This closes a loophole that allowed
users to execute stored procedures if copies of the procedure remained in
cache after permissions for the user were revoked. It can affect the type of
error, and the error number, returned by some command batches.
The ordering of checks for existence, checks for permissions, integrity
checks, and the auditing of events may now be performed in different
order. The order of these checks depends on the type of query, on whether
commands were batched, and on the inclusion of procedural objects in the
batch. This can affect the type of error, the error number, or the type of
event audited.
Permissions on Objects in Procedures Checked at Run-time
Users can create procedural objects (procedures, views, etc.) that name objects
which they normally do not have access to, although they are not allowed to
execute the procedure or use the view.
Previously, attempts to create the procedural object would fail when the create
command was run. Now, the create command succeeds, but attempts to use the
object fail.
For example, the following command to create a procedure succeeds, even
though the user issuing the command does not have permission on
mary.sales_prospects:
create proc steal_leads
Vedere la pagina 49
1 2 ... 45 46 47 48 49 50 51 52 53 54 55 ... 145 146

Commenti su questo manuale

Nessun commento