php-src/ext/oci8/tests/error.phpt
Antony Dovgal d99f05f1a2 add _not yet 100% complete_ Unicode support
collections, statements and BLOBs seem to be working ok
though there are still some things to be done in order to make oci_bind_array_by_name() work with U-strings

Notes:
- in Unicode mode OCI8 always speaks to Oracle server using UTF-16, so all the conversions are done by the client lib.
This is why character set parameter of oci_connect() and NLS_LANG are ignored in U-mode.

- BLOBs and CLOBs behave quite differently in U-mode.
Reading data from a CLOB would result in Unicode string, while BLOBs would return binary string.
Also, all LOB utilities work with _bytes_ when BLOB is used and _characters_ when it's CLOB.
It's not that obvious, but it does make a lot of sense to me.
2006-11-10 16:56:19 +00:00

58 lines
1.1 KiB
PHP

--TEST--
oci_error()
--SKIPIF--
<?php if (!extension_loaded('oci8')) die("skip no oci8 extension"); ?>
--FILE--
<?php
require dirname(__FILE__)."/connect.inc";
if (!empty($dbase)) {
var_dump(oci_connect($user, $password, $dbase));
}
else {
var_dump(oci_connect($user, $password));
}
var_dump($s = oci_parse($c, "WRONG SYNTAX"));
var_dump(oci_execute($s));
var_dump(oci_error($s));
echo "Done\n";
?>
--EXPECTF--
resource(%s) of type (oci8 connection)
resource(%s) of type (oci8 statement)
Warning: oci_execute(): ORA-00900: invalid SQL statement in %s on line %d
bool(false)
array(4) {
["code"]=>
int(900)
["message"]=>
string(32) "ORA-00900: invalid SQL statement"
["offset"]=>
int(0)
["sqltext"]=>
string(12) "WRONG SYNTAX"
}
Done
--UEXPECTF--
resource(%d) of type (oci8 connection)
resource(%d) of type (oci8 statement)
Warning: oci_execute(): ORA-00900: invalid SQL statement in %s on line %d
bool(false)
array(4) {
["code"]=>
int(900)
["message"]=>
unicode(32) "ORA-00900: invalid SQL statement"
["offset"]=>
int(0)
["sqltext"]=>
unicode(12) "WRONG SYNTAX"
}
Done