From 020edc73be983e8e2aca04782ff7c901da4afad7 Mon Sep 17 00:00:00 2001 From: Gina Peter Banyard Date: Sun, 18 Jan 2026 21:36:01 +0000 Subject: [PATCH] ibm_db2: fix XML by converting para to simpara tags via script (#5136) --- reference/ibm_db2/book.xml | 13 +- reference/ibm_db2/configure.xml | 12 +- .../ibm_db2/functions/db2-autocommit.xml | 32 +- .../ibm_db2/functions/db2-bind-param.xml | 56 ++-- .../ibm_db2/functions/db2-client-info.xml | 24 +- reference/ibm_db2/functions/db2-close.xml | 20 +- .../functions/db2-column-privileges.xml | 24 +- reference/ibm_db2/functions/db2-columns.xml | 24 +- reference/ibm_db2/functions/db2-commit.xml | 12 +- .../ibm_db2/functions/db2-conn-error.xml | 20 +- .../ibm_db2/functions/db2-conn-errormsg.xml | 20 +- reference/ibm_db2/functions/db2-connect.xml | 284 +++++++++--------- .../ibm_db2/functions/db2-cursor-type.xml | 12 +- .../ibm_db2/functions/db2-escape-string.xml | 16 +- reference/ibm_db2/functions/db2-exec.xml | 52 ++-- reference/ibm_db2/functions/db2-execute.xml | 44 +-- .../ibm_db2/functions/db2-fetch-array.xml | 24 +- .../ibm_db2/functions/db2-fetch-assoc.xml | 24 +- .../ibm_db2/functions/db2-fetch-both.xml | 24 +- .../ibm_db2/functions/db2-fetch-object.xml | 32 +- reference/ibm_db2/functions/db2-fetch-row.xml | 32 +- .../functions/db2-field-display-size.xml | 16 +- .../ibm_db2/functions/db2-field-name.xml | 16 +- reference/ibm_db2/functions/db2-field-num.xml | 16 +- .../ibm_db2/functions/db2-field-precision.xml | 16 +- .../ibm_db2/functions/db2-field-scale.xml | 16 +- .../ibm_db2/functions/db2-field-type.xml | 16 +- .../ibm_db2/functions/db2-field-width.xml | 16 +- .../ibm_db2/functions/db2-foreign-keys.xml | 20 +- .../ibm_db2/functions/db2-free-result.xml | 12 +- reference/ibm_db2/functions/db2-free-stmt.xml | 12 +- .../ibm_db2/functions/db2-get-option.xml | 40 +-- .../ibm_db2/functions/db2-last-insert-id.xml | 32 +- reference/ibm_db2/functions/db2-lob-read.xml | 24 +- .../ibm_db2/functions/db2-next-result.xml | 16 +- .../ibm_db2/functions/db2-num-fields.xml | 16 +- reference/ibm_db2/functions/db2-num-rows.xml | 24 +- reference/ibm_db2/functions/db2-pclose.xml | 20 +- reference/ibm_db2/functions/db2-pconnect.xml | 272 ++++++++--------- reference/ibm_db2/functions/db2-prepare.xml | 40 +-- .../ibm_db2/functions/db2-primary-keys.xml | 20 +- .../functions/db2-procedure-columns.xml | 24 +- .../ibm_db2/functions/db2-procedures.xml | 20 +- reference/ibm_db2/functions/db2-result.xml | 20 +- reference/ibm_db2/functions/db2-rollback.xml | 16 +- .../ibm_db2/functions/db2-server-info.xml | 48 +-- .../ibm_db2/functions/db2-set-option.xml | 124 ++++---- .../ibm_db2/functions/db2-special-columns.xml | 20 +- .../ibm_db2/functions/db2-statistics.xml | 40 +-- .../ibm_db2/functions/db2-stmt-error.xml | 16 +- .../ibm_db2/functions/db2-stmt-errormsg.xml | 16 +- .../functions/db2-table-privileges.xml | 20 +- reference/ibm_db2/functions/db2-tables.xml | 24 +- reference/ibm_db2/ini.xml | 132 ++++---- reference/ibm_db2/setup.xml | 21 +- 55 files changed, 998 insertions(+), 1004 deletions(-) diff --git a/reference/ibm_db2/book.xml b/reference/ibm_db2/book.xml index 24df3ec6e6..cc530f2fae 100644 --- a/reference/ibm_db2/book.xml +++ b/reference/ibm_db2/book.xml @@ -1,28 +1,26 @@ - - + IBM DB2, Cloudscape and Apache Derby IBM DB2 - + &reftitle.intro; - + These functions enable you to access IBM DB2 Universal Database, IBM Cloudscape, and Apache Derby databases using the DB2 Call Level Interface (DB2 CLI). - + - + &reference.ibm-db2.setup; &reference.ibm-db2.constants; &reference.ibm-db2.reference; - - diff --git a/reference/ibm_db2/configure.xml b/reference/ibm_db2/configure.xml index 78de262d53..0535af0587 100644 --- a/reference/ibm_db2/configure.xml +++ b/reference/ibm_db2/configure.xml @@ -2,7 +2,7 @@
&reftitle.install; - + To build the ibm_db2 extension, the DB2 application development header files and libraries must be installed on the system. DB2 does not install these by default, so it may be necessary to return to the @@ -10,13 +10,13 @@ The DB2 Application Development Client includes the header files and is freely available for download from the IBM DB2 Universal Database support site. - - + + If the DB2 application development header files and libraries are added to a Linux or Unix operating system on which DB2 was already installed, the command db2iupdt -e must be issued to update the symbolic links to the header files and libraries in the DB2 instances. - + ibm_db2 is a &link.pecl; extension, so follow the instructions in to install the ibm_db2 extension for PHP. @@ -32,10 +32,10 @@ bash$ ./configure --with-IBM_DB2=/path/to/DB2 Note for IIS users - + If the ibm_db2 driver is being used with Microsoft Internet Information Server (IIS), it may be necessary to do the following: - + Install DB2 with extended operating system security. diff --git a/reference/ibm_db2/functions/db2-autocommit.xml b/reference/ibm_db2/functions/db2-autocommit.xml index c991101076..526f3fe1f9 100644 --- a/reference/ibm_db2/functions/db2-autocommit.xml +++ b/reference/ibm_db2/functions/db2-autocommit.xml @@ -15,9 +15,9 @@ intvalue - + Sets or gets the AUTOCOMMIT behavior of the specified connection resource. - + @@ -26,10 +26,10 @@ connection - + A valid database connection resource variable as returned from db2_connect or db2_pconnect. - + @@ -41,17 +41,17 @@ DB2_AUTOCOMMIT_OFF - + Turns AUTOCOMMIT off. - + DB2_AUTOCOMMIT_ON - + Turns AUTOCOMMIT on. - + @@ -62,21 +62,21 @@ &reftitle.returnvalues; - + When db2_autocommit receives only the connection parameter, it returns the current state of AUTOCOMMIT for the requested connection as an integer value. A value of DB2_AUTOCOMMIT_OFF indicates that AUTOCOMMIT is off, while a value of DB2_AUTOCOMMIT_ON indicates that AUTOCOMMIT is on. - - + + When db2_autocommit receives both the connection parameter and autocommit parameter, it attempts to set the AUTOCOMMIT state of the requested connection to the corresponding state. &return.success; - + @@ -84,11 +84,11 @@ Retrieving the AUTOCOMMIT value for a connection - + In the following example, a connection which has been created with AUTOCOMMIT turned off is tested with the db2_autocommit function. - + Setting the AUTOCOMMIT value for a connection - + In the following example, a connection which was initially created with AUTOCOMMIT turned off has its behavior changed to turn AUTOCOMMIT on. - + intscale0 - + Binds a PHP variable to an SQL statement parameter in a statement resource returned by db2_prepare. This function gives you more control over the parameter type, data type, precision, and scale for the parameter than simply passing the variable as part of the optional input array to db2_execute. - + @@ -35,33 +35,33 @@ stmt - + A prepared statement returned from db2_prepare. - + parameter_number - + Specifies the 1-indexed position of the parameter in the prepared statement. - + variable_name - + A string specifying the name of the PHP variable to bind to the parameter specified by parameter_number. - + parameter_type - + A constant specifying whether the PHP variable should be bound to the SQL parameter as an input parameter (DB2_PARAM_IN), an output parameter (DB2_PARAM_OUT), or as a @@ -70,49 +70,49 @@ also specify DB2_PARAM_FILE to bind the PHP variable to the name of a file that contains large object (BLOB, CLOB, or DBCLOB) data. - + data_type - + A constant specifying the SQL data type that the PHP variable should be bound as: one of DB2_BINARY, DB2_CHAR, DB2_DOUBLE, or DB2_LONG . - + precision - + Specifies the precision with which the variable should be bound to the database. This parameter can also be used for retrieving XML output values from stored procedures. A non-negative value specifies the maximum size of the XML data that will be retrieved from the database. If this parameter is not used, a default of 1MB will be assumed for retrieving the XML output value from the stored procedure. - + scale - + Specifies the scale with which the variable should be bound to the database. - + &reftitle.returnvalues; - + &return.success; - + @@ -120,7 +120,7 @@ Binding PHP variables to a prepared statement - + The SQL statement in the following example uses two input parameters in the WHERE clause. We call db2_bind_param to bind two PHP variables to the corresponding SQL parameters. Notice that the PHP @@ -132,7 +132,7 @@ db2_bind_param. The variables must be bound and, for parameters that accept input, must have any value assigned, before calling db2_execute. - + - + an input (IN) parameter that accepts the name of the first animal as input - + - + an input-output (INOUT) parameter that accepts the name of the second animal as input and returns the string TRUE if an animal in the database matches that name - + - + an output (OUT) parameter that returns the sum of the weight of the two identified animals - + In addition, the stored procedure returns a result set consisting of the @@ -248,14 +248,14 @@ Results: Inserting a binary large object (BLOB) directly from a file - + The data for large objects are typically stored in files, such as XML documents or audio files. Rather than reading an entire file into a PHP variable, and then binding that PHP variable into an SQL statement, you can avoid some memory overhead by binding the file directly to the input parameter of your SQL statement. The following example demonstrates how to bind a file directly into a BLOB column. - + MINIMUM - + Supports the minimum ODBC SQL grammar. - + CORE - + Supports the core ODBC SQL grammar. - + EXTENDED - + Supports extended ODBC SQL grammar. - + @@ -124,18 +124,18 @@ connection - + Specifies an active DB2 client connection. - + &reftitle.returnvalues; - + Returns an object on a successful call,&return.falseforfailure; - + A <function>db2_last_insert_id</function> example - + The following example shows how to return the auto generated ID of last insert query that successfully executed on this connection. - + intcolnum intlength - + Use db2_lob_read to iterate through a specified column of a result set and retrieve a user defined size of LOB data. - + @@ -29,25 +29,25 @@ stmt - + A valid stmt resource containing LOB data. - + colnum - + A valid column number in the result set of the stmt resource. - + length - + The size of the LOB data to be retrieved from the stmt resource. - + @@ -55,18 +55,18 @@ &reftitle.returnvalues; - + Returns the amount of data the user specifies. Returns &false; if the data cannot be retrieved. - + &reftitle.examples; Iterating through different types of data - - + + - + A stored procedure can return zero or more result sets. While you handle the first result set in exactly the same way you would handle the results returned by a simple SELECT statement, to fetch the second and subsequent result sets from a stored procedure you must call the db2_next_result function and return the result to a uniquely named PHP variable. - + @@ -32,35 +32,35 @@ stmt - + A prepared statement returned from db2_exec or db2_execute. - + &reftitle.returnvalues; - + Returns a new statement resource containing the next result set if the stored procedure returned another result set. Returns &false; if the stored procedure did not return another result set. - + &reftitle.examples; Calling a stored procedure that returns multiple result sets - + In the following example, we call a stored procedure that returns three result sets. The first result set is fetched directly from the same statement resource on which we invoked the CALL statement, while the second and third result sets are fetched from statement resources returned from our calls to the db2_next_result function. - + - + Returns the number of fields contained in a result set. This is most useful for handling the result sets returned by dynamically generated queries, or for result sets returned by stored procedures, where your application cannot otherwise know how to retrieve and use the results. - + @@ -30,30 +30,30 @@ stmt - + A valid statement resource containing a result set. - + &reftitle.returnvalues; - + Returns an integer value representing the number of fields in the result set associated with the specified statement resource. Returns &false; if the statement resource is not a valid input value. - + &reftitle.examples; Retrieving the number of fields in a result set - + The following example demonstrates how to retrieve the number of fields returned in a result set. - + - + Returns the number of rows deleted, inserted, or updated by an SQL statement. - - + + To determine the number of rows that will be returned by a SELECT statement, issue SELECT COUNT(*) with the same predicates as your intended SELECT statement and retrieve the value. - - + + If your application logic checks the number of rows returned by a SELECT statement and branches if the number of rows is 0, consider modifying your application to attempt to return the first row with one of db2_fetch_assoc, db2_fetch_both, db2_fetch_array, or db2_fetch_row, and branch if the fetch function returns &false;. - + - + If you issue a SELECT statement using a scrollable cursor, db2_num_rows returns the number of rows returned by the SELECT statement. However, the overhead associated with scrollable @@ -44,7 +44,7 @@ you should use a forward-only cursor and either call SELECT COUNT(*) or rely on the bool return value of the fetch functions to achieve the equivalent functionality with much better performance. - + @@ -54,19 +54,19 @@ stmt - + A valid stmt resource containing a result set. - + &reftitle.returnvalues; - + Returns the number of rows affected by the last SQL statement issued by the specified statement handle,&return.falseforfailure; - + Closing a persistent connection - + The following example demonstrates a successful attempt to close a connection to an IBM DB2 i5/OS database. - + - + Returns a persistent connection to an IBM DB2 Universal Database, IBM Cloudscape, or Apache Derby database. - + - + For more information on persistent connections, refer to . - + - + Calling db2_close on a persistent connection always returns &true;, but the underlying DB2 client connection remains open and waiting to serve the next matching db2_pconnect request. - + - + Users running version 1.9.0 or later of ibm_db2 should be aware that the extension will perform a transaction rollback on persistent connections at the end of a request, thus ending the transaction. This prevents the transaction block from carrying over to the next request which uses that connection if script execution ends before the transaction block does. - + @@ -51,10 +51,10 @@ database - + For a cataloged connection to a database, database represents the database alias in the DB2 client catalog. - + For an uncataloged connection to a database, database represents a complete connection @@ -75,43 +75,43 @@ database - + The name of the database. - + hostname - + The hostname or IP address of the database server. - + port - + The TCP/IP port on which the database is listening for requests. - + username - + The username with which you are connecting to the database. - + password - + The password with which you are connecting to the database. - + @@ -121,17 +121,17 @@ username - + The username with which you are connecting to the database. - + password - + The password with which you are connecting to the database. - + @@ -144,47 +144,47 @@ autocommit - + Passing the DB2_AUTOCOMMIT_ON value turns autocommit on for this connection handle. - - + + Passing the DB2_AUTOCOMMIT_OFF value turns autocommit off for this connection handle. - + DB2_ATTR_CASE - + Passing the DB2_CASE_NATURAL value specifies that column names are returned in natural case. - - + + Passing the DB2_CASE_LOWER value specifies that column names are returned in lower case. - - + + Passing the DB2_CASE_UPPER value specifies that column names are returned in upper case. - + CURSOR - + Passing the DB2_FORWARD_ONLY value specifies a forward-only cursor for a statement resource. This is the default cursor type and is supported on all database servers. - - + + Passing the DB2_SCROLLABLE value specifies a scrollable cursor for a statement resource. This mode enables random access to rows in a result set, but currently is supported only by IBM DB2 Universal Database. - + @@ -196,19 +196,19 @@ trustedcontext - + Passing the DB2_TRUSTED_CONTEXT_ENABLE value turns trusted context on for this connection handle. This parameter cannot be set using db2_set_option. - - + + This key works only if the database is cataloged (even if the database is local), or if you specify the full DSN when you create the connection. - - + + To catalog the database, use following commands: - + db2 catalog tcpip node loopback remote <SERVERNAME> server <SERVICENAME> db2 catalog database <LOCALDBNAME> as <REMOTEDBNAME> at node loopback db2 "update dbm cfg using svcename <SERVICENAME>" @@ -222,37 +222,37 @@ db2set DB2COMM=TCPIP The following new i5/OS options are available in ibm_db2 version 1.5.1 and later. - Conflicting connection attributes used in conjunction with persistent + Conflicting connection attributes used in conjunction with persistent connections can produce indeterminate results on i5/OS. Site policies should be establish for all applications using each persistent connection user profile. The default DB2_AUTOCOMMIT_ON is suggested when using persistent connections. - + i5_lib - + A character value that indicates the default library that will be used for resolving unqualified file references. This is not valid if the connection is using system naming mode. - + i5_naming - + DB2_I5_NAMING_ON value turns on DB2 UDB CLI iSeries system naming mode. Files are qualified using the slash (/) delimiter. Unqualified files are resolved using the library list for the job. - - + + DB2_I5_NAMING_OFF value turns off DB2 UDB CLI default naming mode, which is SQL naming. Files are qualified using the period (.) delimiter. Unqualified files are resolved using either the default library or the current user ID. - + @@ -265,69 +265,69 @@ db2set DB2COMM=TCPIP source, the change does not take effect until the next successful db2_pconnect for the connection handle. - + The php.ini setting ibm_db2.i5_allow_commit==0 or DB2_I5_TXN_NO_COMMIT is the default, but may be overridden with the i5_commit option. - + - + DB2_I5_TXN_NO_COMMIT - Commitment control is not used. - - + + DB2_I5_TXN_READ_UNCOMMITTED - Dirty reads, nonrepeatable reads, and phantoms are possible. - - + + DB2_I5_TXN_READ_COMMITTED - Dirty reads are not possible. Nonrepeatable reads, and phantoms are possible. - - + + DB2_I5_TXN_REPEATABLE_READ - Dirty reads and nonrepeatable reads are not possible. Phantoms are possible. - - + + DB2_I5_TXN_SERIALIZABLE - Transactions are serializable. Dirty reads, non-repeatable reads, and phantoms are not possible - + i5_query_optimize - + DB2_FIRST_IO All queries are optimized with the goal of returning the first page of output as fast as possible. This goal works well when the output is controlled by a user who is most likely to cancel the query after viewing the first page of output data. Queries coded with an OPTIMIZE FOR nnn ROWS clause honor the goal specified by the clause. - - + + DB2_ALL_IO All queries are optimized with the goal of running the entire query to completion in the shortest amount of elapsed time. This is a good option when the output of a query is being written to a file or report, or the interface is queuing the output data. Queries coded with an OPTIMIZE FOR nnn ROWS clause honor the goal specified by the clause. This is the default. - + i5_dbcs_alloc - + DB2_I5_DBCS_ALLOC_ON value turns on DB2 6X allocation scheme for DBCS translation column size growth. - + DB2_I5_DBCS_ALLOC_OFF value turns off DB2 6X allocation scheme for DBCS translation column size growth. - + The php.ini setting ibm_db2.i5_dbcs_alloc==0 or DB2_I5_DBCS_ALLOC_OFF is the default, but may be overridden with the i5_dbcs_alloc option. - + @@ -335,123 +335,123 @@ db2set DB2COMM=TCPIP i5_date_fmt - + DB2_I5_FMT_ISO - The International Organization for Standardization (ISO) date format yyyy-mm-dd is used. This is the default. - - + + DB2_I5_FMT_USA - The United States date format mm/dd/yyyy is used. - - + + DB2_I5_FMT_EUR - The European date format dd.mm.yyyy is used. - - + + DB2_I5_FMT_JIS - The Japanese Industrial Standard date format yyyy-mm-dd is used. - - + + DB2_I5_FMT_MDY - The date format mm/dd/yyyy is used. - - + + DB2_I5_FMT_DMY - The date format dd/mm/yyyy is used. - - + + DB2_I5_FMT_YMD - The date format yy/mm/dd is used. - - + + DB2_I5_FMT_JUL - The Julian date format yy/ddd is used. - - + + DB2_I5_FMT_JOB - The job default is used. - + i5_date_sep - + DB2_I5_SEP_SLASH - A slash ( / ) is used as the date separator. This is the default. - - + + DB2_I5_SEP_DASH - A dash ( - ) is used as the date separator. - - + + DB2_I5_SEP_PERIOD - A period ( . ) is used as the date separator. - - + + DB2_I5_SEP_COMMA - A comma ( , ) is used as the date separator. - - + + DB2_I5_SEP_BLANK - A blank is used as the date separator. - - + + DB2_I5_SEP_JOB - The job default is used - + i5_time_fmt - + DB2_I5_FMT_ISO - The International Organization for Standardization (ISO) time format hh.mm.ss is used. This is the default. - - + + DB2_I5_FMT_USA - The United States time format hh:mmxx is used, where xx is AM or PM. - - + + DB2_I5_FMT_EUR - The European time format hh.mm.ss is used. - - + + DB2_I5_FMT_JIS - The Japanese Industrial Standard time format hh:mm:ss is used. - - + + DB2_I5_FMT_HMS - The hh:mm:ss format is used. - + i5_time_sep - + DB2_I5_SEP_COLON - A colon ( : ) is used as the time separator. This is the default. - - + + DB2_I5_SEP_PERIOD - A period ( . ) is used as the time separator. - - + + DB2_I5_SEP_COMMA - A comma ( , ) is used as the time separator. - - + + DB2_I5_SEP_BLANK - A blank is used as the time separator. - - + + DB2_I5_SEP_JOB - The job default is used. - + i5_decimal_sep - + DB2_I5_SEP_PERIOD - A period ( . ) is used as the decimal separator. This is the default. - - + + DB2_I5_SEP_COMMA - A comma ( , ) is used as the decimal separator. - - + + DB2_I5_SEP_JOB - The job default is used. - + @@ -468,10 +468,10 @@ db2set DB2COMM=TCPIP resolving unqualified file references. Specify the library list elements separated by blanks 'i5_libl'=>"MYLIB YOURLIB ANYLIB". - + i5_libl calls qsys2/qcmdexc('cmd',cmdlen), which is only available in i5/OS V5R4 and later. - + @@ -484,14 +484,14 @@ db2set DB2COMM=TCPIP &reftitle.returnvalues; - + Returns a connection handle resource if the connection attempt is successful. db2_pconnect tries to reuse an existing connection resource that exactly matches the database, username, and password parameters. If the connection attempt fails, db2_pconnect returns &false;. - + @@ -549,13 +549,13 @@ db2set DB2COMM=TCPIP A <function>db2_pconnect</function> example - + In the following example, the first call to db2_pconnect returns a new persistent connection resource. The second call to db2_pconnect returns a persistent connection resource that simply reuses the first persistent connection resource. - + Using trusted context - + The following example shows how to enable trusted context, switch users, and get the current user ID. - + - + db2_prepare creates a prepared SQL statement which can include 0 or more parameter markers (? characters) representing parameters for input, output, or input/output. You can pass parameters to the prepared statement using db2_bind_param, or for input values only, as an array passed to db2_execute. - + There are three main advantages to using prepared statements in your application: - + Performance: when you prepare a statement, the database server creates an optimized access plan for retrieving data with that statement. Subsequently issuing the prepared statement with db2_execute enables the statements to reuse that access plan and avoids the overhead of dynamically creating a new access plan for every statement you issue. - + - + Security: when you prepare a statement, you can include parameter markers for input values. When you execute a prepared statement with input values for placeholders, the database server checks each input value to ensure that the type matches the column definition or parameter definition. - + - + Advanced functionality: Parameter markers not only enable you to pass input values to prepared SQL statements, they also enable you to retrieve OUT and INOUT parameters from stored procedures using db2_bind_param. - + @@ -67,55 +67,55 @@ connection - + A valid database connection resource variable as returned from db2_connect or db2_pconnect. - + statement - + An SQL statement, optionally containing one or more parameter markers.. - + options - + An associative array containing statement options. You can use this parameter to request a scrollable cursor on database servers that support this functionality. - - + + For a description of valid statement options, see db2_set_option. - + &reftitle.returnvalues; - + Returns a statement resource if the SQL statement was successfully parsed and prepared by the database server. Returns &false; if the database server returned an error. You can determine which error was returned by calling db2_stmt_error or db2_stmt_errormsg. - + &reftitle.examples; Preparing and executing an SQL statement with parameter markers - + The following example prepares an INSERT statement that accepts four parameter markers, then iterates over an array of arrays containing the input values to be passed to db2_execute. - + stringtable_name - + Returns a result set listing the primary keys for a table. - + @@ -29,36 +29,36 @@ connection - + A valid connection to an IBM DB2, Cloudscape, or Apache Derby database. - + qualifier - + A qualifier for DB2 databases running on OS/390 or z/OS servers. For other databases, pass &null; or an empty string. - + schema - + The schema which contains the tables. If schema is &null;, db2_primary_keys matches the schema for the current connection. - + table_name - + The name of the table. - + diff --git a/reference/ibm_db2/functions/db2-procedure-columns.xml b/reference/ibm_db2/functions/db2-procedure-columns.xml index d4c46ffcea..6f360a5823 100644 --- a/reference/ibm_db2/functions/db2-procedure-columns.xml +++ b/reference/ibm_db2/functions/db2-procedure-columns.xml @@ -19,10 +19,10 @@ stringnullparameter - + Returns a result set listing the parameters for one or more stored procedures. - + @@ -31,49 +31,49 @@ connection - + A valid connection to an IBM DB2, Cloudscape, or Apache Derby database. - + qualifier - + A qualifier for DB2 databases running on OS/390 or z/OS servers. For other databases, pass &null; or an empty string. - + schema - + The schema which contains the procedures. This parameter accepts a search pattern containing _ and % as wildcards. - + procedure - + The name of the procedure. This parameter accepts a search pattern containing _ and % as wildcards. - + parameter - + The name of the parameter. This parameter accepts a search pattern containing _ and % as wildcards. If this parameter is &null;, all parameters for the specified stored procedures are returned. - + diff --git a/reference/ibm_db2/functions/db2-procedures.xml b/reference/ibm_db2/functions/db2-procedures.xml index aa3a842d30..bbfe82b531 100644 --- a/reference/ibm_db2/functions/db2-procedures.xml +++ b/reference/ibm_db2/functions/db2-procedures.xml @@ -19,10 +19,10 @@ - + Returns a result set listing the stored procedures registered in a database. - + @@ -31,38 +31,38 @@ connection - + A valid connection to an IBM DB2, Cloudscape, or Apache Derby database. - + qualifier - + A qualifier for DB2 databases running on OS/390 or z/OS servers. For other databases, pass &null; or an empty string. - + schema - + The schema which contains the procedures. This parameter accepts a search pattern containing _ and % as wildcards. - + procedure - + The name of the procedure. This parameter accepts a search pattern containing _ and % as wildcards. - + diff --git a/reference/ibm_db2/functions/db2-result.xml b/reference/ibm_db2/functions/db2-result.xml index 16e0c76366..a0910111c3 100644 --- a/reference/ibm_db2/functions/db2-result.xml +++ b/reference/ibm_db2/functions/db2-result.xml @@ -17,13 +17,13 @@ - + Use db2_result to return the value of a specified column in the current row of a result set. You must call db2_fetch_row before calling db2_result to set the location of the result set pointer. - + @@ -32,39 +32,39 @@ stmt - + A valid stmt resource. - + column - + Either an integer mapping to the 0-indexed field in the result set, or a string matching the name of the column. - + &reftitle.returnvalues; - + Returns the value of the requested field if the field exists in the result set. Returns &null; if the field does not exist, and issues a warning. - + &reftitle.examples; A <function>db2_result</function> example - + The following example demonstrates how to iterate through a result set with db2_fetch_row and retrieve columns from the result set with db2_result. - + resourceconnection - + Rolls back an in-progress transaction on the specified connection resource and begins a new transaction. PHP applications normally default to AUTOCOMMIT mode, so db2_rollback normally has no effect unless AUTOCOMMIT has been turned off for the connection resource. - + @@ -29,26 +29,26 @@ connection - + A valid database connection resource variable as returned from db2_connect or db2_pconnect. - + &reftitle.returnvalues; - + &return.success; - + &reftitle.examples; Rolling back a DELETE statement - + In the following example, we count the number of rows in a table, turn off AUTOCOMMIT mode on a database connection, delete all of the rows in the table and return the count of 0 to prove that the @@ -57,7 +57,7 @@ is the same as before we issued the DELETE statement. The return to the original state of the table demonstrates that the roll back of the transaction succeeded. - + UR - + Uncommitted read: changes are immediately visible by all concurrent transactions. - + CS - + Cursor stability: a row read by one transaction can be altered and committed by a second concurrent transaction. - + RS - + Read stability: a transaction can add or remove rows matching a search condition or a pending transaction. - + RR - + Repeatable read: data affected by pending transaction is not available to other transactions. - + NC - + No commit: any changes are visible at the end of a successful operation. Explicit commits and rollbacks are not allowed. - + @@ -222,33 +222,33 @@ ENTRY - + Entry-level SQL-92 compliance. - + FIPS127 - + FIPS-127-2 transitional compliance. - + FULL - + Full level SQL-92 compliance. - + INTERMEDIATE - + Intermediate level SQL-92 compliance. - + @@ -267,18 +267,18 @@ connection - + Specifies an active DB2 client connection. - + &reftitle.returnvalues; - + Returns an object on a successful call,&return.falseforfailure; - + diff --git a/reference/ibm_db2/functions/db2-special-columns.xml b/reference/ibm_db2/functions/db2-special-columns.xml index a7dd6fbd75..93912f54af 100644 --- a/reference/ibm_db2/functions/db2-special-columns.xml +++ b/reference/ibm_db2/functions/db2-special-columns.xml @@ -19,9 +19,9 @@ intscope - + Returns a result set listing the unique row identifier columns for a table. - + @@ -30,34 +30,34 @@ connection - + A valid connection to an IBM DB2, Cloudscape, or Apache Derby database. - + qualifier - + A qualifier for DB2 databases running on OS/390 or z/OS servers. For other databases, pass &null; or an empty string. - + schema - + The schema which contains the tables. - + table_name - + The name of the table. - + diff --git a/reference/ibm_db2/functions/db2-statistics.xml b/reference/ibm_db2/functions/db2-statistics.xml index 99be72cf11..1602d2400e 100644 --- a/reference/ibm_db2/functions/db2-statistics.xml +++ b/reference/ibm_db2/functions/db2-statistics.xml @@ -19,9 +19,9 @@ boolunique - + Returns a result set listing the index and statistics for a table. - + @@ -30,47 +30,47 @@ connection - + A valid connection to an IBM DB2, Cloudscape, or Apache Derby database. - + qualifier - + A qualifier for DB2 databases running on OS/390 or z/OS servers. For other databases, pass &null; or an empty string. - + schema - + The schema that contains the targeted table. If this parameter is &null;, the statistics and indexes are returned for the schema of the current user. - + table_name - + The name of the table. - + unique - + When unique is &true;, the information for all indexes in the table are returned. Otherwise, only the information for unique indexes in the table are returned. - + @@ -205,31 +205,31 @@ CARDINALITY - + If the row contains information about an index, this column contains an integer value representing the number of unique values in the index. - - + + If the row contains information about the table itself, this column contains an integer value representing the number of rows in the table. - + PAGES - + If the row contains information about an index, this column contains an integer value representing the number of pages used to store the index. - - + + If the row contains information about the table itself, this column contains an integer value representing the number of pages used to store the table. - + diff --git a/reference/ibm_db2/functions/db2-stmt-error.xml b/reference/ibm_db2/functions/db2-stmt-error.xml index 7a880ae288..685b407bfe 100644 --- a/reference/ibm_db2/functions/db2-stmt-error.xml +++ b/reference/ibm_db2/functions/db2-stmt-error.xml @@ -15,16 +15,16 @@ resourcenullstmt&null; - + Returns a string containing the SQLSTATE value returned by an SQL statement. - - + + If you do not pass a statement resource as an argument to db2_stmt_error, the driver returns the SQLSTATE value associated with the last attempt to return a statement resource, for example, from db2_prepare or db2_exec. - + To learn what the SQLSTATE value means, you can issue the following command at a DB2 Command Line Processor prompt: @@ -40,18 +40,18 @@ stmt - + A valid statement resource. - + &reftitle.returnvalues; - + Returns a string containing an SQLSTATE value. - + - - + &reftitle.setup;
&reftitle.required; - + To connect to IBM DB2 Universal Database for Linux, UNIX, and Windows, or IBM Cloudscape, or Apache Derby, you must install an IBM DB2 Universal Database client on the same computer on which you are running PHP. The extension has been developed and tested with DB2 Version 8.2. - - + + To connect to IBM DB2 Universal Database for z/OS or iSeries, you also require IBM DB2 Connect or the equivalent DRDA gateway software. - +
Requirements on Linux or Unix - + The user invoking the PHP executable or SAPI must specify the DB2 instance before accessing these functions. You can set the name of the DB2 instance in &php.ini; using the ibm_db2.instance_name configuration option, or you can source the DB2 instance profile before invoking the PHP executable. - + If you created a DB2 instance named db2inst1 in /home/db2inst1/, for example, you can add the @@ -64,15 +63,14 @@ bash$ source /home/db2inst1/sqllib/db2profile
&reftitle.resources; - + The ibm_db2 extension returns connection resources, statement resources, and result set resources. - +
- -