Article: Integrate PHP and Java Applications with Oracle WebLogic Server and Zend Server 5.0
Zend Server, a high-performance, enterprise-ready PHP stack, comes with a built-in "Java bridge" to connect PHP with JEE applications and services. Here's how it works.
SQLSRV_ERRORS(3)SQLSRV_ERRORS(3)sqlsrv_errors - Returns error and warning information about the last SQLSRV operation performedSYNOPSIS
mixed sqlsrv_errors ([int $errorsOrWarnings])
DESCRIPTION
Returns error and warning information about the last SQLSRV operation performed.
PARAMETERS
o $errorsOrWarnings
- Determines whether error information, warning information, or both are returned. If this parameter is not supplied, both error
information and warning information are returned. The following are the supported values for this parameter: SQLSRV_ERR_ALL, SQL-
SRV_ERR_ERRORS, SQLSRV_ERR_WARNINGS.
RETURN VALUES
If errors and/or warnings occurred on the last sqlsrv operation, an array of arrays containing error information is returned. If no errors
and/or warnings occurred on the last sqlsrv operation, NULL is returned. The following table describes the structure of the returned
arrays:
Array returned by sqlsrv_errors
+---------+---------------------------------------------------+
| Key | |
| | |
| | Description |
| | |
+---------+---------------------------------------------------+
|SQLSTATE | |
| | |
| | For errors that originate from the ODBC driver, |
| | the SQLSTATE returned by ODBC. For errors that |
| | originate from the Microsoft Drivers for PHP for |
| | SQL Server, a SQLSTATE of IMSSP. For warnings |
| | that originate from the Microsoft Drivers for PHP |
| | for SQL Server, a SQLSTATE of 01SSP. |
| | |
| code | |
| | |
| | For errors that originate from SQL Server, the |
| | native SQL Server error code. For errors that |
| | originate from the ODBC driver, the error code |
| | returned by ODBC. For errors that originate from |
| | the Microsoft Drivers for PHP for SQL Server, the |
| | Microsoft Drivers for PHP for SQL Server error |
| | code. |
| | |
|message | |
| | |
| | A description of the error. |
| | |
+---------+---------------------------------------------------+
EXAMPLES
Example #1
functionname(3) example
<?php
$serverName = "serverName/sqlexpress";
$connectionInfo = array( "Database"=>"dbName", "UID"=>"username", "PWD"=>"password");
$conn = sqlsrv_connect( $serverName, $connectionInfo);
if( $conn === false ) {
die( print_r( sqlsrv_errors(), true));
}
/* Set up a query to select an invalid column name. */
$sql = "SELECT BadColumnName FROM Table_1";
/* Execution of the query will fail because of the bad column name. */
$stmt = sqlsrv_query( $conn, $sql );
if( $stmt === false ) {
if( ($errors = sqlsrv_errors() ) != null) {
foreach( $errors as $error ) {
echo "SQLSTATE: ".$error[ 'SQLSTATE']."<br />";
echo "code: ".$error[ 'code']."<br />";
echo "message: ".$error[ 'message']."<br />";
}
}
}
?>
NOTES
By default, warnings generated on a call to any SQLSRV function are treated as errors. This means that if a warning occurs on a call to a
SQLSRV function, the function returns FALSE. However, warnings that correspond to SQLSTATE values 01000, 01001, 01003, and 01S02 are never
treated as errors. For information about changing this behavior, see sqlsrv_configure(3) and the WarningsReturnAsErrors setting.
SEE ALSO sqlsrv_configure(3).
PHP Documentation Group SQLSRV_ERRORS(3)
