Seagate ST43401N/ND Guia de Instalação descarregar pdf (Página 51)

CHAPTER 5 Implement: Making Required Application Changes

select * from mary.sales_prospects

However, this user cannot execute the procedure; the attempt to execute returns

a permissions error.

Stored Procedure Existence Checks in Command Batches

In pre-11.5 versions, an entire batch fails during compilation if a stored

procedure named in the batch does not exist. In 11.5.x and later versions, the

existence of stored procedures included in batches is not checked until

execution time.

Each command in the batch succeeds or fails independently at execution time

unless begin transaction and commit or rollback transaction commands are

used, so other commands in the batch may succeed, while the stored procedure

execution returns an error message.

For example, this batch attempts to execute a procedure that does not exist:

ANY_COMMAND_BEFORE

exec proc_that_does_not_exist

ANY_COMMAND_AFTER

In pre-11.5 versions, the entire batch would fail at compilation time. In 11.5.1

and later versions, the commands before and after the missing procedure

execute (if they do not return errors) but

proc_that_does_not_exist returns an

error.

Ordering of Integrity and Permissions Checks

In some cases in pre-11.5 versions, integrity checks were performed before

permissions checks. Now, certain permissions checks are performed before

integrity checks. This may result in cases where commands that previously

failed integrity checks may instead fail permissions checks, if both these

problems existed in the command. The results of auditing may differ.

Changes in Error Numbers

Error message numbers have changed and new messages have been added.

Applications that perform checks on message numbers need to also check for

the new error message numbers. The permission failures described in this table

include:

1 2 ... 46 47 48 49 50 51 52 53 54 55 56 ... 145 146

Sem comentários

Seagate ST43401N/ND Guia de Instalação Página 51