mirror of
https://github.com/php/php-src.git
synced 2024-09-29 05:46:06 +00:00
d99f05f1a2
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.
52 lines
906 B
PHP
52 lines
906 B
PHP
--TEST--
|
|
oci_bind_array_by_name() and invalid values 10
|
|
--SKIPIF--
|
|
<?php if (!extension_loaded('oci8')) die("skip no oci8 extension"); ?>
|
|
--FILE--
|
|
<?php
|
|
|
|
require dirname(__FILE__).'/connect.inc';
|
|
|
|
$statement = oci_parse($c, 'SELECT user FROM v$session');
|
|
|
|
$array = Array(1,2,3,4,5);
|
|
|
|
oci_bind_array_by_name($statement, ":c1", $array, 5, 5, SQLT_CHR);
|
|
|
|
oci_execute($statement);
|
|
|
|
var_dump($array);
|
|
|
|
echo "Done\n";
|
|
?>
|
|
--EXPECTF--
|
|
Warning: oci_bind_array_by_name(): ORA-01036: illegal variable name/number in %s on line %d
|
|
array(5) {
|
|
[0]=>
|
|
string(1) "1"
|
|
[1]=>
|
|
string(1) "2"
|
|
[2]=>
|
|
string(1) "3"
|
|
[3]=>
|
|
string(1) "4"
|
|
[4]=>
|
|
string(1) "5"
|
|
}
|
|
Done
|
|
--UEXPECTF--
|
|
Warning: oci_bind_array_by_name(): ORA-01036: illegal variable name/number in %s on line %d
|
|
array(5) {
|
|
[0]=>
|
|
unicode(1) "1"
|
|
[1]=>
|
|
unicode(1) "2"
|
|
[2]=>
|
|
unicode(1) "3"
|
|
[3]=>
|
|
unicode(1) "4"
|
|
[4]=>
|
|
unicode(1) "5"
|
|
}
|
|
Done
|