Oracle 5.0 Reference Manual page 1733

• Because procedure logging occurs at the statement level rather than at the
of the
--replicate-*-table
apply to stored procedures, except those procedures that are invoked from within functions.
Routine logging changes in MySQL 5.0.16: In 5.0.12, a change was introduced to log stored
procedure calls at the statement level rather than at the
the requirement that procedures be identified as safe. The requirement now exists only for
stored functions, because they still appear in the binary log as function invocations rather
than as the statements executed within the function. To reflect the lifting of the restriction on
stored procedures, the
to
log_bin_trust_function_creators
[1468] server option is renamed to
creators
(For backward compatibility, the old names are recognized but result in a warning.) Error messages
that now apply only to functions and not to routines in general are re-worded.
Routine logging changes in MySQL 5.0.19: In 5.0.12, a change was introduced to log a stored
function invocation as
statement, or if the function invokes a stored procedure that produces an error. In 5.0.19, these
invocations are logged as
use of was found to yield insufficient control over error code checking.
DO
Binary Logging of Stored Programs
options is revised to apply only to stored functions. They no longer
log_bin_trust_routine_creators
if the invocation changes data and occurs within a nonlogged
DO func_name()
SELECT func_name()
1713
level. This change eliminates
CALL
system variable is renamed
[463] and the
--log-bin-trust-routine-
--log-bin-trust-function-creators
instead. The change to
level, interpretation
CALL
[1468].
was made because
SELECT