Home > Contents > Index >
CATALOGMANAGER
Creates, modifies, or deletes rows and tables (known previously as a "catalogs" in earlier verisions of the product).
Using LOCAL or STACKED for the SCOPED argument protects those variables from change, but disallow sharing of input space. Use <CGIARGUMENT NAME="name"/> to specify that specific CGI parameters be made available to the CatalogManager. Use <ARGUMENT> as always for specific string values.
By omitting SCOPED (or setting it to "local") you can cause the CatalogManager to share all the existing input variables without scoping. Note that this means specified arguments overwrite existing variables. Using SCOPED="shared" means that you need not specify any argument; CGIARGUMENTS, specifically, is ignored. Note that variables set since program execution began are reset to the original values passed on the URL line. Use with care.
Syntax
<CATALOGMANAGER> [<ARGUMENT NAME="ftcmd" VALUE="some value
"/>] [<CGIARGUMENT
NAME="Some CGI arg" VALUE="Some CGI value"/>] </CATALOGMANAGER>Parameters
ARGUMENT (optional)
- Arguments passed to the CatalogManager as it is called.
CGIARGUMENT (optional)
- CGI arguments passed to the CatalogManager.
SCOPED (optional)
- Valid options for this attribute are as follows:
GLOBAL
- the default behavior. Does not protect input variables.LOCAL
- arguments passed in are restored (or destroyed) on return from the call.STACKED
- the child only sees the explicit arguments passed in and can only return values in that same namespace.
Note
HTTP headers are not preserved when the
SCOPED
parameter is set toSTACKED
. To preserveHTTP
header variables, you must specify them within an argument.For example:
<ARGUMENT NAME="HTTPS" VALUE="Variables.HTTPS"/>
and
<ARGUMENT NAME="HTTPS_HOST" VALUE="Variables.HTTPS_HOST"/>
Description
The
<CATALOGMANAGER>
tag invokes the CatalogManager module. TheCATALOGMANAGER
module creates, modifies, or deletes tables and rows. It is an alternative to SQL-based tags, such as<CALLSQL>
.The following is a list of the commands that you use with the CATALOGMANAGER tag.
Using LOCAL or STACKED for the SCOPED argument protects those variables from change, but disallows sharing of input space. Use <CGIARGUMENT NAME="name"/> to specify that specific CGI parameters be made available to the CatalogManager. Use <ARGUMENT> as always for specific string values.
By omitting SCOPED (or setting it to "local") you can cause the CatalogManager to share all the existing input variables without scoping. Note that this means specified arguments overwrite existing variables. Using SCOPED="shared" means that you need not specify any argument; CGIARGUMENTS, specifically, is ignored. Note that variables set since program execution began are reset to the original values passed on the URL line. Use with care.
Error Numbers
There are no possible
errno
for this tag.Example
<SETVAR NAME="errno" VALUE="0"/> <CATALOGMANAGER> <ARGUMENT NAME="ftcmd" VALUE="deleterow"/> <ARGUMENT NAME="tablename" VALUE="Movies"/> <ARGUMENT NAME="contentname" VALUE="Ishtar"/> <!-- Be sure review upload files are deleted--> <ARGUMENT NAME="Delete uploaded file(s)" VALUE="yes"/> </CATALOGMANAGER> <!-- Check status --> <ICS.ARGUMENT COND="Variables.errno=0"> <IF> <THEN> Deleted movie: <CSVAR NAME="Variables.contentname"/> <br/> </THEN> </IF>See Also
Home > Contents > Index > ![]()
Oracle XML Tag Reference
Copyright (c) 2013, 2018, Oracle and/or its affiliates. All rights reserved.