Laura Stewart wrote:
> I understand, and because of that, I would prefer to change the
> procedure name.
> One question to ask the community as how often are these particular
> procedures invoked by users?
>
> If you look at the Ref Guide PDF, every occasion where these long
> names are used, they
For backward compatibility I think we should always support the
older names. For future name choices can you let us know what
is the max length that causes problems.
Laura Stewart wrote:
I understand, and because of that, I would prefer to change the
procedure name.
One question to ask the com
I understand, and because of that, I would prefer to change the procedure name.
One question to ask the community as how often are these particular
procedures invoked by users?
If you look at the Ref Guide PDF, every occasion where these long
names are used, they bleed outside the margins or in s
If you have to, to get it work then go ahead. But do note that I have
gotten multiple questions about "missing" system procedures when the
answer was that the user left off the SYSCS_UTIL. -- this is why I
prefer all documentation to have the complete reference. I know it
is likely that a paragr
Laura Stewart wrote:
Is it possible to change the name of a built-in system procedure?
The following procedures cause real problems in the PDF output of the
docs because of their really long names:
SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE
SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_E
Laura Stewart wrote:
Okay, is it acceptable in places where we are only discussing the
procedure to omit the SYSCS_UTIL. portion of the name?
Clearly in examples that users might copy/paste we would use the full name.
In the description of procedures it might be ok to omit the
"SYSCS_UTIL." p
Is it possible to change the name of a built-in system procedure?
The following procedures cause real problems in the PDF output of the
docs because of their really long names:
SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE
SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE
Okay, is it acceptable in places where we are only discussing the
procedure to omit the SYSCS_UTIL. portion of the name?
Clearly in examples that users might copy/paste we would use the full name.
On 3/2/07, Suresh Thalamati <[EMAIL PROTECTED]> wrote:
Laura Stewart wrote:
> Is it possible to cha