From 5386297f86704ceab3b278902a32f92214ee1f50 Mon Sep 17 00:00:00 2001 From: Christopher Jones Date: Wed, 18 Nov 2009 21:50:25 +0000 Subject: [PATCH] Add PL/SQL example and discuss use of semi-colons git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@290947 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/oci8/functions/oci-parse.xml | 58 ++++++++++++++++++++++++-- 1 file changed, 54 insertions(+), 4 deletions(-) diff --git a/reference/oci8/functions/oci-parse.xml b/reference/oci8/functions/oci-parse.xml index 5c4e6394e4..6b472b95a8 100644 --- a/reference/oci8/functions/oci-parse.xml +++ b/reference/oci8/functions/oci-parse.xml @@ -14,7 +14,7 @@ stringsql_text - Prepares the sql_textusing + Prepares sql_text using connection and returns the statement identifier, which can be used with oci_bind_by_name, oci_execute and other functions. @@ -45,6 +45,12 @@ The SQL or PL/SQL statement. + + SQL statements should not end with a + semi-colon (";"). PL/SQL + statements should end with a semi-colon + (";"). + @@ -62,13 +68,14 @@ &reftitle.examples; - <function>oci_parse</function> example + <function>oci_parse</function> example for SQL statements \n"; +?> +]]> + + + + + + <function>oci_parse</function> example for PL/SQL statements + + ]]> @@ -101,8 +151,8 @@ echo "\n"; - In PHP versions before 5.0.0 you must - use ociparse instead. &oci.name.compat.note; + In PHP versions before 5.0.0 use ociparse + instead. &oci.name.compat.note;