cvs: phpdoc /en/reference/sybase/functions sybase-affected-rows.xml sybase-close.xml sybase-connect.xml sybase-data-seek.xml
sybase-deadlock-retry-count.xml sybase-fetch-array.xml sybase-fetch-assoc.xml sybase-fetch-field.xml sybase-fetch-object.xml sybase-fetch-row.xml
sybase-field-seek.xml sybase-free-result.xml sybase-get-last-message.xml sybase-min-client-severity.xml sybase-min-error-severity.xml
sybase-min-message-severity.xml sybase-min-server-severity.xml sybase-num-fields.xml sybase-num-rows.xml sybase-pconnect.xml sybase-query.xml
sybase-result.xml sybase-select-db.xml sybase-set-message-handler.xml sybase-unbuffered-query.xml

From:	Enrique Garcia Briones	Date:	Wed, 30 Mar 2005 16:03:27 +0000
Subject:	cvs: phpdoc /en/reference/sybase/functions sybase-affected-rows.xml sybase-close.xml sybase-connect.xml sybase-data-seek.xml sybase-deadlock-retry-count.xml sybase-fetch-array.xml sybase-fetch-assoc.xml sybase-fetch-field.xml sybase-fetch-object.xml sybase-fetch-row.xml sybase-field-seek.xml sybase-free-result.xml sybase-get-last-message.xml sybase-min-client-severity.xml sybase-min-error-severity.xml sybase-min-message-severity.xml sybase-min-server-severity.xml sybase-num-fields.xml sybase-num-rows.xml sybase-pconnect.xml sybase-query.xml sybase-result.xml sybase-select-db.xml sybase-set-message-handler.xml sybase-unbuffered-query.xml
Groups:	php.doc
Request:	Send a blank email to phpdoc+get-969367164@lists.php.net to get a copy of this message

baoengb Wed Mar 30 11:03:27 2005 EDT Modified files: /phpdoc/en/reference/sybase/functions sybase-affected-rows.xml sybase-close.xml sybase-connect.xml sybase-data-seek.xml sybase-deadlock-retry-count.xml sybase-fetch-array.xml sybase-fetch-assoc.xml sybase-fetch-field.xml sybase-fetch-object.xml sybase-fetch-row.xml sybase-field-seek.xml sybase-free-result.xml sybase-get-last-message.xml sybase-min-client-severity.xml sybase-min-error-severity.xml sybase-min-message-severity.xml sybase-min-server-severity.xml sybase-num-fields.xml sybase-num-rows.xml sybase-pconnect.xml sybase-query.xml sybase-result.xml sybase-select-db.xml sybase-set-message-handler.xml sybase-unbuffered-query.xml Log: Initial WS, preparation for new doc style

http://cvs.php.net/diff.php/phpdoc/en/reference/sybase/functions/sybase-affected-rows.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/reference/sybase/functions/sybase-affected-rows.xml diff -u phpdoc/en/reference/sybase/functions/sybase-affected-rows.xml:1.8 phpdoc/en/reference/sybase/functions/sybase-affected-rows.xml:1.9 --- phpdoc/en/reference/sybase/functions/sybase-affected-rows.xml:1.8 Fri Mar 11 11:11:51 2005 +++ phpdoc/en/reference/sybase/functions/sybase-affected-rows.xml Wed Mar 30 11:03:25 2005 @@ -1,58 +1,59 @@ <?xml version="1.0" encoding="iso-8859-1"?> - +  - <refentry id="function.sybase-affected-rows"> - <refnamediv> - <refname>sybase_affected_rows</refname> - <refpurpose>Gets number of affected rows in last query</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>int</type><methodname>sybase_affected_rows</methodname> - <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_affected_rows</function> returns the number of - rows affected by the last INSERT, UPDATE or DELETE query on the - server associated with the specified link identifier. If the - link identifier isn't specified, the last opened link is assumed. - </para> - <para> - <example> - <title>Delete-Query</title> - <programlisting role="php"> +<refentry id="function.sybase-affected-rows"> + <refnamediv> + <refname>sybase_affected_rows</refname> + <refpurpose>Gets number of affected rows in last query</refpurpose> + </refnamediv> + + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>int</type><methodname>sybase_affected_rows</methodname> + <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_affected_rows</function> returns the number of + rows affected by the last INSERT, UPDATE or DELETE query on the + server associated with the specified link identifier. If the + link identifier isn't specified, the last opened link is assumed. + </para> + <para> + <example> + <title>Delete-Query</title> + <programlisting role="php"> <![CDATA[ <?php - /* connect to database */ - sybase_connect('SYBASE', '', '') or - die("Could not connect"); - sybase_select_db("db"); +/* connect to database */ +sybase_connect('SYBASE', '', '') or +die("Could not connect"); +sybase_select_db("db"); - sybase_query("DELETE FROM sometable WHERE id < 10"); - printf("Records deleted: %d\n", sybase_affected_rows()); +sybase_query("DELETE FROM sometable WHERE id < 10"); +printf("Records deleted: %d\n", sybase_affected_rows()); ?> ]]> - </programlisting> - &example.outputs; - <screen> + </programlisting> + &example.outputs; + <screen> <![CDATA[ - Records deleted: 10 +Records deleted: 10 ]]> - </screen> - </example> - </para> - <para> - This command is not effective for SELECT statements, only on - statements which modify records. To retrieve the number of rows - returned from a SELECT, use <function>sybase_num_rows</function>. - &sybase.ct.only; - </para> - <para> - See also <function>sybase_num_rows</function>. - </para> - </refsect1> - </refentry> + </screen> + </example> + </para> + <para> + This command is not effective for SELECT statements, only on + statements which modify records. To retrieve the number of rows + returned from a SELECT, use <function>sybase_num_rows</function>. + &sybase.ct.only; + </para> + <para> + See also <function>sybase_num_rows</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-close"> - <refnamediv> - <refname>sybase_close</refname> - <refpurpose>Closes a Sybase connection</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>bool</type><methodname>sybase_close</methodname> - <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_close</function> closes the link to a Sybase - database that's associated with the specified link - <parameter>link_identifier</parameter>. - If the link identifier isn't specified, the last opened link is - assumed. - </para> - <para> - &return.success; - </para> - <para> - Note that this isn't usually necessary, as non-persistent - open links are automatically closed at the end of the script's - execution. - </para> - <para> - <function>sybase_close</function> will not close persistent links - generated by <function>sybase_pconnect</function>. - </para> - <para> - See also - <function>sybase_connect</function> and - <function>sybase_pconnect</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-close"> + <refnamediv> + <refname>sybase_close</refname> + <refpurpose>Closes a Sybase connection</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>bool</type><methodname>sybase_close</methodname> + <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_close</function> closes the link to a Sybase + database that's associated with the specified link + <parameter>link_identifier</parameter>. + If the link identifier isn't specified, the last opened link is + assumed. + </para> + <para> + &return.success; + </para> + <para> + Note that this isn't usually necessary, as non-persistent + open links are automatically closed at the end of the script's + execution. + </para> + <para> + <function>sybase_close</function> will not close persistent links + generated by <function>sybase_pconnect</function>. + </para> + <para> + See also + <function>sybase_connect</function> and + <function>sybase_pconnect</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-connect"> - <refnamediv> - <refname>sybase_connect</refname> - <refpurpose>Opens a Sybase server connection</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>resource</type><methodname>sybase_connect</methodname> - <methodparam choice="opt"><type>string</type><parameter>servername</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>username</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>password</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>charset</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>appname</parameter></methodparam> - </methodsynopsis> - <para> - Returns a positive Sybase link identifier on success, or - &false; on failure. - </para> - <para> - <function>sybase_connect</function> establishes a connection to a - Sybase server. The servername argument has to be a valid - servername that is defined in the 'interfaces' file. - </para> - <para> - In case a second call is made to - <function>sybase_connect</function> with the same arguments, no - new link will be established, but instead, the link identifier of - the already opened link will be returned. - </para> - <para> - The link to the server will be closed as soon as the - execution of the script ends, unless it's closed earlier by - explicitly calling <function>sybase_close</function>. - </para> - <para> - <example> - <title><function>sybase_connect</function> example</title> - <programlisting role="php"> +<refentry id="function.sybase-connect"> + <refnamediv> + <refname>sybase_connect</refname> + <refpurpose>Opens a Sybase server connection</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>resource</type><methodname>sybase_connect</methodname> + <methodparam choice="opt"><type>string</type><parameter>servername</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>username</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>password</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>charset</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>appname</parameter></methodparam> + </methodsynopsis> + <para> + Returns a positive Sybase link identifier on success, or + &false; on failure. + </para> + <para> + <function>sybase_connect</function> establishes a connection to a + Sybase server. The servername argument has to be a valid + servername that is defined in the 'interfaces' file. + </para> + <para> + In case a second call is made to + <function>sybase_connect</function> with the same arguments, no + new link will be established, but instead, the link identifier of + the already opened link will be returned. + </para> + <para> + The link to the server will be closed as soon as the + execution of the script ends, unless it's closed earlier by + explicitly calling <function>sybase_close</function>. + </para> + <para> + <example> + <title><function>sybase_connect</function> example</title> + <programlisting role="php"> <![CDATA[ <?php - $link = sybase_connect('SYBASE', '', '') - or die("Could not connect !"); - echo "Connected successfully"; - sybase_close($link); +$link = sybase_connect('SYBASE', '', '') + or die("Could not connect !"); +echo "Connected successfully"; +sybase_close($link); ?> ]]> - </programlisting> - </example> - </para> - <para> - See also - <function>sybase_pconnect</function> and - <function>sybase_close</function>. - </para> - </refsect1> - </refentry> + </programlisting> + </example> + </para> + <para> + See also + <function>sybase_pconnect</function> and + <function>sybase_close</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-data-seek"> - <refnamediv> - <refname>sybase_data_seek</refname> - <refpurpose>Moves internal row pointer</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>bool</type><methodname>sybase_data_seek</methodname> - <methodparam><type>resource</type><parameter>result_identifier</parameter></methodparam> - <methodparam><type>int</type><parameter>row_number</parameter></methodparam> - </methodsynopsis> - <para> - &return.success; - </para> - <para> - <function>sybase_data_seek</function> moves the internal row - pointer of the Sybase result associated with the specified result - identifier to pointer to the specified row number. The next call - to <function>sybase_fetch_row</function> would return that row. - </para> - <para> - See also - <function>sybase_fetch_row</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-data-seek"> + <refnamediv> + <refname>sybase_data_seek</refname> + <refpurpose>Moves internal row pointer</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>bool</type><methodname>sybase_data_seek</methodname> + <methodparam><type>resource</type><parameter>result_identifier</parameter></methodparam> + <methodparam><type>int</type><parameter>row_number</parameter></methodparam> + </methodsynopsis> + <para> + &return.success; + </para> + <para> + <function>sybase_data_seek</function> moves the internal row + pointer of the Sybase result associated with the specified result + identifier to pointer to the specified row number. The next call + to <function>sybase_fetch_row</function> would return that row. + </para> + <para> + See also + <function>sybase_fetch_row</function>. + </para> + </refsect1> +</refentry>  - <refentry id="function.sybase-deadlock-retry-count"> - <refnamediv> - <refname>sybase_deadlock_retry_count</refname> - <refpurpose>Sets the deadlock retry count</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>void</type><methodname>sybase_deadlock_retry_count</methodname> - <methodparam><type>int</type><parameter>retry_count</parameter></methodparam> - </methodsynopsis> - <para> - Using <function>sybase_deadlock_retry_count</function>, the number of retries - can be defined in cases of deadlocks. By default, every deadlock is retried - an infinite number of times or until the process is killed by Sybase, the - executing script is killed (for instance, by <function>set_time_limit</function>) - or the query succeeds. - </para> - - &sybase.ct.only; + +<refentry id="function.sybase-deadlock-retry-count"> + <refnamediv> + <refname>sybase_deadlock_retry_count</refname> + <refpurpose>Sets the deadlock retry count</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>void</type><methodname>sybase_deadlock_retry_count</methodname> + <methodparam><type>int</type><parameter>retry_count</parameter></methodparam> + </methodsynopsis> + <para> + Using <function>sybase_deadlock_retry_count</function>, the number of retries + can be defined in cases of deadlocks. By default, every deadlock is retried + an infinite number of times or until the process is killed by Sybase, the + executing script is killed (for instance, by <function>set_time_limit</function>) + or the query succeeds. + </para> + + &sybase.ct.only; - <para> - <table> - <title>Values for retry_count</title> - <tgroup cols="2"> - <tbody> - <row> - <entry>-1</entry> - <entry>Retry forever (default)</entry> - </row> - <row> - <entry>0</entry> - <entry>Do not retry</entry> - </row> - <row> - <entry>n</entry> - <entry>Retry n times</entry> - </row> - </tbody> - </tgroup> - </table> - </para> - </refsect1> - </refentry> + <para> + <table> + <title>Values for retry_count</title> + <tgroup cols="2"> + <tbody> + <row> + <entry>-1</entry> + <entry>Retry forever (default)</entry> + </row> + <row> + <entry>0</entry> + <entry>Do not retry</entry> + </row> + <row> + <entry>n</entry> + <entry>Retry n times</entry> + </row> + </tbody> + </tgroup> + </table> + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-fetch-array"> - <refnamediv> - <refname>sybase_fetch_array</refname> - <refpurpose>Fetch row as array</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>array</type><methodname>sybase_fetch_array</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - </methodsynopsis> - <para> - Returns an array that corresponds to the fetched row, or - &false; if there are no more rows. - </para> - <para> - <function>sybase_fetch_array</function> is an extended version of - <function>sybase_fetch_row</function>. In addition to storing the - data in the numeric indices of the result array, it also stores - the data in associative indices, using the field names as keys. - </para> - <para> - An important thing to note is that using - <function>sybase_fetch_array</function> is NOT significantly - slower than using <function>sybase_fetch_row</function>, while it - provides a significant added value. - </para> - <note> - <para> - When selecting fields with identical names (for instance, in - a join), the associative indices will have a sequential number prepended. - See the example for details. - </para> - </note> - <para> - <example> - <title>Identical fieldnames</title> - <programlisting role="php"> +<refentry id="function.sybase-fetch-array"> + <refnamediv> + <refname>sybase_fetch_array</refname> + <refpurpose>Fetch row as array</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>array</type><methodname>sybase_fetch_array</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + </methodsynopsis> + <para> + Returns an array that corresponds to the fetched row, or + &false; if there are no more rows. + </para> + <para> + <function>sybase_fetch_array</function> is an extended version of + <function>sybase_fetch_row</function>. In addition to storing the + data in the numeric indices of the result array, it also stores + the data in associative indices, using the field names as keys. + </para> + <para> + An important thing to note is that using + <function>sybase_fetch_array</function> is NOT significantly + slower than using <function>sybase_fetch_row</function>, while it + provides a significant added value. + </para> + <note> + <para> + When selecting fields with identical names (for instance, in + a join), the associative indices will have a sequential number prepended. + See the example for details. + </para> + </note> + <para> + <example> + <title>Identical fieldnames</title> + <programlisting role="php"> <![CDATA[ <?php - $dbh = sybase_connect('SYBASE', '', ''); - $q = sybase_query('SELECT * FROM p, a WHERE p.person_id= a.person_id'); - var_dump(sybase_fetch_array($q)); - sybase_close($dbh); + +$dbh = sybase_connect('SYBASE', '', ''); +$q = sybase_query('SELECT * FROM p, a WHERE p.person_id= a.person_id'); +var_dump(sybase_fetch_array($q)); +sybase_close($dbh); ?> ]]> - </programlisting> - <para> - The above example would produce the following output (assuming the two tables only - have each one column called "person_id"): - </para> - <screen> + </programlisting> + <para> + The above example would produce the following output (assuming the two tables only + have each one column called "person_id"): + </para> + <screen> <![CDATA[ array(4) { [0]=> @@ -65,17 +66,17 @@ int(1) } ]]> - </screen> - </example> - </para> - <para> - See also - <function>sybase_fetch_row</function>, - <function>sybase_fetch_assoc</function> and - <function>sybase_fetch_object</function>. - </para> - </refsect1> - </refentry> + </screen> + </example> + </para> + <para> + See also + <function>sybase_fetch_row</function>, + <function>sybase_fetch_assoc</function> and + <function>sybase_fetch_object</function>. + </para> + </refsect1> +</refentry>  - <refentry id="function.sybase-fetch-assoc"> - <refnamediv> - <refname>sybase_fetch_assoc</refname> - <refpurpose>Fetch a result row as an associative array</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>array</type><methodname>sybase_fetch_assoc</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - </methodsynopsis> - <para> - Returns an array that corresponds to the fetched row, or - &false; if there are no more rows. - </para> - - &sybase.ct.only; - - <para> - <function>sybase_fetch_assoc</function> is a version of - <function>sybase_fetch_row</function> that uses column names - instead of integers for indices in the result array. Columns from - different tables with the same names are returned as - name, name1, name2, ..., nameN. - </para> - <para> - An important thing to note is that using - <function>sybase_fetch_assoc</function> is NOT significantly - slower than using <function>sybase_fetch_row</function>, while it - provides a significant added value. - </para> - <para> - See also - <function>sybase_fetch_array</function>, - <function>sybase_fetch_object</function> and - <function>sybase_fetch_row</function>. - </para> - </refsect1> - </refentry> + +<refentry id="function.sybase-fetch-assoc"> + <refnamediv> + <refname>sybase_fetch_assoc</refname> + <refpurpose>Fetch a result row as an associative array</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>array</type><methodname>sybase_fetch_assoc</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + </methodsynopsis> + <para> + Returns an array that corresponds to the fetched row, or + &false; if there are no more rows. + </para> + + &sybase.ct.only; + + <para> + <function>sybase_fetch_assoc</function> is a version of + <function>sybase_fetch_row</function> that uses column names + instead of integers for indices in the result array. Columns from + different tables with the same names are returned as + name, name1, name2, ..., nameN. + </para> + <para> + An important thing to note is that using + <function>sybase_fetch_assoc</function> is NOT significantly + slower than using <function>sybase_fetch_row</function>, while it + provides a significant added value. + </para> + <para> + See also + <function>sybase_fetch_array</function>, + <function>sybase_fetch_object</function> and + <function>sybase_fetch_row</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-fetch-field"> - <refnamediv> - <refname>sybase_fetch_field</refname> - <refpurpose>Get field information from a result</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>object</type><methodname>sybase_fetch_field</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - <methodparam choice="opt"><type>int</type><parameter>field_offset</parameter></methodparam> - </methodsynopsis> - <para> - Returns an object containing field information. - </para> - <para> - <function>sybase_fetch_field</function> can be used in order to - obtain information about fields in a certain query result. If - the field offset isn't specified, the next field that wasn't yet - retrieved by <function>sybase_fetch_field</function> is retrieved. - </para> - <para> - The properties of the object are: - </para> - <itemizedlist> - <listitem> - <simpara> - name - column name. if the column is a result of a function, this - property is set to computed#N, where #N is a serial number. - </simpara> - </listitem> - <listitem> - <simpara> - column_source - the table from which the column was taken - </simpara> - </listitem> - <listitem> - <simpara> - max_length - maximum length of the column - </simpara> - </listitem> - <listitem> - <simpara> - numeric - 1 if the column is numeric - </simpara> - </listitem> - <listitem> - <simpara> - type - datatype of the column - </simpara> - </listitem> - </itemizedlist> - <para> - See also <function>sybase_field_seek</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-fetch-field"> + <refnamediv> + <refname>sybase_fetch_field</refname> + <refpurpose>Get field information from a result</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>object</type><methodname>sybase_fetch_field</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + <methodparam choice="opt"><type>int</type><parameter>field_offset</parameter></methodparam> + </methodsynopsis> + <para> + Returns an object containing field information. + </para> + <para> + <function>sybase_fetch_field</function> can be used in order to + obtain information about fields in a certain query result. If + the field offset isn't specified, the next field that wasn't yet + retrieved by <function>sybase_fetch_field</function> is retrieved. + </para> + <para> + The properties of the object are: + </para> + <itemizedlist> + <listitem> + <simpara> + name - column name. if the column is a result of a function, this + property is set to computed#N, where #N is a serial number. + </simpara> + </listitem> + <listitem> + <simpara> + column_source - the table from which the column was taken + </simpara> + </listitem> + <listitem> + <simpara> + max_length - maximum length of the column + </simpara> + </listitem> + <listitem> + <simpara> + numeric - 1 if the column is numeric + </simpara> + </listitem> + <listitem> + <simpara> + type - datatype of the column + </simpara> + </listitem> + </itemizedlist> + <para> + See also <function>sybase_field_seek</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-fetch-object"> - <refnamediv> - <refname>sybase_fetch_object</refname> - <refpurpose>Fetch a row as an object</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>object</type><methodname>sybase_fetch_object</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - <methodparam choice="opt"><type>mixed</type><parameter>object</parameter></methodparam> - </methodsynopsis> - <para> - Returns an object with properties that correspond to the - fetched row, or &false; if there are no more rows. - </para> - <para> - <function>sybase_fetch_object</function> is similar to - <function>sybase_fetch_assoc</function>, with one difference - an object - is returned, instead of an array. - </para> - <para> - Use the second <parameter>object</parameter> to specify the type of object - you want to return. If this parameter is omitted, the object will be of - type stdClass. - </para> - <note> - <para> - As of PHP 4.3.0, this function will no longer return numeric object members. - </para> - <para> - Old behaviour: - <screen> +<refentry id="function.sybase-fetch-object"> + <refnamediv> + <refname>sybase_fetch_object</refname> + <refpurpose>Fetch a row as an object</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>object</type><methodname>sybase_fetch_object</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + <methodparam choice="opt"><type>mixed</type><parameter>object</parameter></methodparam> + </methodsynopsis> + <para> + Returns an object with properties that correspond to the + fetched row, or &false; if there are no more rows. + </para> + <para> + <function>sybase_fetch_object</function> is similar to + <function>sybase_fetch_assoc</function>, with one difference - an object + is returned, instead of an array. + </para> + <para> + Use the second <parameter>object</parameter> to specify the type of object + you want to return. If this parameter is omitted, the object will be of + type stdClass. + </para> + <note> + <para> + As of PHP 4.3.0, this function will no longer return numeric object members. + </para> + <para> + Old behaviour: + <screen> <![CDATA[ object(stdclass)(3) { [0]=> @@ -46,9 +46,9 @@ string(3) "bar" } ]]> - </screen> - New behaviour: - <screen> + </screen> + New behaviour: + <screen> <![CDATA[ object(stdclass)(3) { ["foo"]=> @@ -57,13 +57,13 @@ string(3) "bar" } ]]> - </screen> - </para> - </note> - <para> - <example> - <title><function>sybase_fetch_object</function> return as Foo</title> - <programlisting role="php"> + </screen> + </para> + </note> + <para> + <example> + <title><function>sybase_fetch_object</function> return as Foo</title> + <programlisting role="php"> <![CDATA[ <?php class Foo { @@ -77,21 +77,21 @@ // {...] ?> ]]> - </programlisting> - </example> - </para> - <para> - Speed-wise, the function is identical to - <function>sybase_fetch_array</function>, and almost as quick as - <function>sybase_fetch_row</function> (the difference is insignificant). - </para> - <para> - See also - <function>sybase_fetch_array</function> and - <function>sybase_fetch_row</function>. - </para> - </refsect1> - </refentry> + </programlisting> + </example> + </para> + <para> + Speed-wise, the function is identical to + <function>sybase_fetch_array</function>, and almost as quick as + <function>sybase_fetch_row</function> (the difference is insignificant). + </para> + <para> + See also + <function>sybase_fetch_array</function> and + <function>sybase_fetch_row</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-fetch-row"> - <refnamediv> - <refname>sybase_fetch_row</refname> - <refpurpose>Get a result row as an enumerated array</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>array</type><methodname>sybase_fetch_row</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - </methodsynopsis> - <para> - Returns an array that corresponds to the fetched row, or - &false; if there are no more rows. - </para> - <para> - <function>sybase_fetch_row</function> fetches one row of data - from the result associated with the specified result identifier. - The row is returned as an array. Each result column is stored in - an array offset, starting at offset 0. - </para> - <para> - Subsequent call to <function>sybase_fetch_row</function> would - return the next row in the result set, or &false; if there are no - more rows. - </para> - <table> - <title>Data types</title> - <tgroup cols="2"> - <thead> - <row> - <entry>PHP</entry> - <entry>Sybase</entry> - </row> - </thead> - <tbody> - <row> - <entry>string</entry> - <entry>VARCHAR, TEXT, CHAR, IMAGE, BINARY, VARBINARY, DATETIME</entry> - </row> - <row> - <entry>int</entry> - <entry>NUMERIC (w/o precision), DECIMAL (w/o precision), INT, BIT, TINYINT, SMALLINT</entry> - </row> - <row> - <entry>float</entry> - <entry>NUMERIC (w/ precision), DECIMAL (w/ precision), REAL, FLOAT, MONEY</entry> - </row> - <row> - <entry>&null;</entry> - <entry>NULL</entry> - </row> - </tbody> - </tgroup> - </table> - <para> - See also - <function>sybase_fetch_array</function>, - <function>sybase_fetch_assoc</function>, - <function>sybase_fetch_object</function>, - <function>sybase_data_seek</function> and - <function>sybase_result</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-fetch-row"> + <refnamediv> + <refname>sybase_fetch_row</refname> + <refpurpose>Get a result row as an enumerated array</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>array</type><methodname>sybase_fetch_row</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + </methodsynopsis> + <para> + Returns an array that corresponds to the fetched row, or + &false; if there are no more rows. + </para> + <para> + <function>sybase_fetch_row</function> fetches one row of data + from the result associated with the specified result identifier. + The row is returned as an array. Each result column is stored in + an array offset, starting at offset 0. + </para> + <para> + Subsequent call to <function>sybase_fetch_row</function> would + return the next row in the result set, or &false; if there are no + more rows. + </para> + <table> + <title>Data types</title> + <tgroup cols="2"> + <thead> + <row> + <entry>PHP</entry> + <entry>Sybase</entry> + </row> + </thead> + <tbody> + <row> + <entry>string</entry> + <entry>VARCHAR, TEXT, CHAR, IMAGE, BINARY, VARBINARY, DATETIME</entry> + </row> + <row> + <entry>int</entry> + <entry>NUMERIC (w/o precision), DECIMAL (w/o precision), INT, BIT, TINYINT, SMALLINT</entry> + </row> + <row> + <entry>float</entry> + <entry>NUMERIC (w/ precision), DECIMAL (w/ precision), REAL, FLOAT, MONEY</entry> + </row> + <row> + <entry>&null;</entry> + <entry>NULL</entry> + </row> + </tbody> + </tgroup> + </table> + <para> + See also + <function>sybase_fetch_array</function>, + <function>sybase_fetch_assoc</function>, + <function>sybase_fetch_object</function>, + <function>sybase_data_seek</function> and + <function>sybase_result</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-field-seek"> - <refnamediv> - <refname>sybase_field_seek</refname> - <refpurpose>Sets field offset</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>bool</type><methodname>sybase_field_seek</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - <methodparam><type>int</type><parameter>field_offset</parameter></methodparam> - </methodsynopsis> - <para> - Seeks to the specified field offset. If the next call to - <function>sybase_fetch_field</function> won't include a field - offset, this field would be returned. - </para> - <para> - &return.success; - </para> - <para> - See also - <function>sybase_fetch_field</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-field-seek"> + <refnamediv> + <refname>sybase_field_seek</refname> + <refpurpose>Sets field offset</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>bool</type><methodname>sybase_field_seek</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + <methodparam><type>int</type><parameter>field_offset</parameter></methodparam> + </methodsynopsis> + <para> + Seeks to the specified field offset. If the next call to + <function>sybase_fetch_field</function> won't include a field + offset, this field would be returned. + </para> + <para> + &return.success; + </para> + <para> + See also + <function>sybase_fetch_field</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-free-result"> - <refnamediv> - <refname>sybase_free_result</refname> - <refpurpose>Frees result memory</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>bool</type><methodname>sybase_free_result</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_free_result</function> only needs to be called - if you are worried about using too much memory while your script - is running. All result memory will automatically be freed when - the script ends. You may call <function>sybase_free_result</function> - with the result identifier as an argument and the associated - result memory will be freed. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-free-result"> + <refnamediv> + <refname>sybase_free_result</refname> + <refpurpose>Frees result memory</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>bool</type><methodname>sybase_free_result</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_free_result</function> only needs to be called + if you are worried about using too much memory while your script + is running. All result memory will automatically be freed when + the script ends. You may call <function>sybase_free_result</function> + with the result identifier as an argument and the associated + result memory will be freed. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-get-last-message"> - <refnamediv> - <refname>sybase_get_last_message</refname> - <refpurpose>Returns the last message from the server</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>string</type><methodname>sybase_get_last_message</methodname> - <void/> - </methodsynopsis> - <para> - <function>sybase_get_last_message</function> returns the last - message reported by the server. - </para> - <para> - See also <function>sybase_min_message_severity</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-get-last-message"> + <refnamediv> + <refname>sybase_get_last_message</refname> + <refpurpose>Returns the last message from the server</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>string</type><methodname>sybase_get_last_message</methodname> + <void/> + </methodsynopsis> + <para> + <function>sybase_get_last_message</function> returns the last + message reported by the server. + </para> + <para> + See also <function>sybase_min_message_severity</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-min-client-severity"> - <refnamediv> - <refname>sybase_min_client_severity</refname> - <refpurpose>Sets minimum client severity</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>void</type><methodname>sybase_min_client_severity</methodname> - <methodparam><type>int</type><parameter>severity</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_min_client_severity</function> sets the minimum - client severity level. - </para> +<refentry id="function.sybase-min-client-severity"> + <refnamediv> + <refname>sybase_min_client_severity</refname> + <refpurpose>Sets minimum client severity</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>void</type><methodname>sybase_min_client_severity</methodname> + <methodparam><type>int</type><parameter>severity</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_min_client_severity</function> sets the minimum + client severity level. + </para> - &sybase.ct.only; + &sybase.ct.only; - <para> - See also - <function>sybase_min_server_severity</function>. - </para> - </refsect1> - </refentry> + <para> + See also + <function>sybase_min_server_severity</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-min-error-severity"> - <refnamediv> - <refname>sybase_min_error_severity</refname> - <refpurpose>Sets minimum error severity</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>void</type><methodname>sybase_min_error_severity</methodname> - <methodparam><type>int</type><parameter>severity</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_min_error_severity</function> sets the minimum - error severity level. - </para> +<refentry id="function.sybase-min-error-severity"> + <refnamediv> + <refname>sybase_min_error_severity</refname> + <refpurpose>Sets minimum error severity</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>void</type><methodname>sybase_min_error_severity</methodname> + <methodparam><type>int</type><parameter>severity</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_min_error_severity</function> sets the minimum + error severity level. + </para> - &sybase.db.only; + &sybase.db.only; - <para> - See also - <function>sybase_min_message_severity</function>. - </para> - </refsect1> - </refentry> + <para> + See also + <function>sybase_min_message_severity</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-min-message-severity"> - <refnamediv> - <refname>sybase_min_message_severity</refname> - <refpurpose>Sets minimum message severity</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>void</type><methodname>sybase_min_message_severity</methodname> - <methodparam><type>int</type><parameter>severity</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_min_message_severity</function> sets the minimum - message severity level. - </para> - - &sybase.db.only; +<refentry id="function.sybase-min-message-severity"> + <refnamediv> + <refname>sybase_min_message_severity</refname> + <refpurpose>Sets minimum message severity</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>void</type><methodname>sybase_min_message_severity</methodname> + <methodparam><type>int</type><parameter>severity</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_min_message_severity</function> sets the minimum + message severity level. + </para> + + &sybase.db.only; - <para> - See also - <function>sybase_min_error_severity</function>. - </para> - </refsect1> - </refentry> + <para> + See also + <function>sybase_min_error_severity</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-min-server-severity"> - <refnamediv> - <refname>sybase_min_server_severity</refname> - <refpurpose>Sets minimum server severity</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>void</type><methodname>sybase_min_server_severity</methodname> - <methodparam><type>int</type><parameter>severity</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_min_server_severity</function> sets the minimum - server severity level. - </para> +<refentry id="function.sybase-min-server-severity"> + <refnamediv> + <refname>sybase_min_server_severity</refname> + <refpurpose>Sets minimum server severity</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>void</type><methodname>sybase_min_server_severity</methodname> + <methodparam><type>int</type><parameter>severity</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_min_server_severity</function> sets the minimum + server severity level. + </para> - &sybase.ct.only; + &sybase.ct.only; - <para> - See also - <function>sybase_min_client_severity</function>. - </para> - </refsect1> - </refentry> + <para> + See also + <function>sybase_min_client_severity</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-num-fields"> - <refnamediv> - <refname>sybase_num_fields</refname> - <refpurpose>Gets the number of fields in a result set</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>int</type><methodname>sybase_num_fields</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_num_fields</function> returns the number of - fields in a result set. - </para> - <para> - See also - <function>sybase_query</function>, - <function>sybase_fetch_field</function> and - <function>sybase_num_rows</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-num-fields"> + <refnamediv> + <refname>sybase_num_fields</refname> + <refpurpose>Gets the number of fields in a result set</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>int</type><methodname>sybase_num_fields</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_num_fields</function> returns the number of + fields in a result set. + </para> + <para> + See also + <function>sybase_query</function>, + <function>sybase_fetch_field</function> and + <function>sybase_num_rows</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-num-rows"> - <refnamediv> - <refname>sybase_num_rows</refname> - <refpurpose>Get number of rows in a result set</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>int</type><methodname>sybase_num_rows</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_num_rows</function> returns the number of rows - in a result set. - </para> - <para> - See also - <function>sybase_num_fields</function>, - <function>sybase_query</function> and - <function>sybase_fetch_row</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-num-rows"> + <refnamediv> + <refname>sybase_num_rows</refname> + <refpurpose>Get number of rows in a result set</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>int</type><methodname>sybase_num_rows</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_num_rows</function> returns the number of rows + in a result set. + </para> + <para> + See also + <function>sybase_num_fields</function>, + <function>sybase_query</function> and + <function>sybase_fetch_row</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-pconnect"> - <refnamediv> - <refname>sybase_pconnect</refname> - <refpurpose>Open persistent Sybase connection</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>resource</type><methodname>sybase_pconnect</methodname> - <methodparam choice="opt"><type>string</type><parameter>servername</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>username</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>password</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>charset</parameter></methodparam> - <methodparam choice="opt"><type>string</type><parameter>appname</parameter></methodparam> - </methodsynopsis> - <para> - Returns a positive Sybase persistent link identifier on success, - or &false; on error. - </para> - <para> - <function>sybase_pconnect</function> acts very much like - <function>sybase_connect</function> with two major differences. - </para> - <para> - First, when connecting, the function would first try to find a - (persistent) link that's already open with the same host, - username and password. If one is found, an identifier for it - will be returned instead of opening a new connection. - </para> - <para> - Second, the connection to the SQL server will not be closed when - the execution of the script ends. Instead, the link will remain - open for future use (<function>sybase_close</function> will not - close links established by <function>sybase_pconnect()</function>). - </para> - <para> - This type of links is therefore called 'persistent'. - </para> - <para> - See also <function>sybase_connect</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-pconnect"> + <refnamediv> + <refname>sybase_pconnect</refname> + <refpurpose>Open persistent Sybase connection</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>resource</type><methodname>sybase_pconnect</methodname> + <methodparam choice="opt"><type>string</type><parameter>servername</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>username</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>password</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>charset</parameter></methodparam> + <methodparam choice="opt"><type>string</type><parameter>appname</parameter></methodparam> + </methodsynopsis> + <para> + Returns a positive Sybase persistent link identifier on success, + or &false; on error. + </para> + <para> + <function>sybase_pconnect</function> acts very much like + <function>sybase_connect</function> with two major differences. + </para> + <para> + First, when connecting, the function would first try to find a + (persistent) link that's already open with the same host, + username and password. If one is found, an identifier for it + will be returned instead of opening a new connection. + </para> + <para> + Second, the connection to the SQL server will not be closed when + the execution of the script ends. Instead, the link will remain + open for future use (<function>sybase_close</function> will not + close links established by <function>sybase_pconnect()</function>). + </para> + <para> + This type of links is therefore called 'persistent'. + </para> + <para> + See also <function>sybase_connect</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-query"> - <refnamediv> - <refname>sybase_query</refname> - <refpurpose>Sends a Sybase query</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>resource</type><methodname>sybase_query</methodname> - <methodparam><type>string</type><parameter>query</parameter></methodparam> - <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> - </methodsynopsis> - <para> - Returns a positive Sybase result identifier on success, or - &false; on error. - </para> - <para> - <function>sybase_query</function> sends a query to the currently - active database on the server that's associated with the specified - link identifier. If the link identifier isn't specified, the last - opened link is assumed. If no link is open, the function tries to - establish a link as if <function>sybase_connect</function> was - called, and use it. - </para> - <para> - See also - <function>sybase_select_db</function> and - <function>sybase_connect</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-query"> + <refnamediv> + <refname>sybase_query</refname> + <refpurpose>Sends a Sybase query</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>resource</type><methodname>sybase_query</methodname> + <methodparam><type>string</type><parameter>query</parameter></methodparam> + <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> + </methodsynopsis> + <para> + Returns a positive Sybase result identifier on success, or + &false; on error. + </para> + <para> + <function>sybase_query</function> sends a query to the currently + active database on the server that's associated with the specified + link identifier. If the link identifier isn't specified, the last + opened link is assumed. If no link is open, the function tries to + establish a link as if <function>sybase_connect</function> was + called, and use it. + </para> + <para> + See also + <function>sybase_select_db</function> and + <function>sybase_connect</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-result"> - <refnamediv> - <refname>sybase_result</refname> - <refpurpose>Get result data</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>string</type><methodname>sybase_result</methodname> - <methodparam><type>resource</type><parameter>result</parameter></methodparam> - <methodparam><type>int</type><parameter>row</parameter></methodparam> - <methodparam><type>mixed</type><parameter>field</parameter></methodparam> - </methodsynopsis> - <para> - Returns the contents of the cell at the row and offset in - the specified Sybase result set. - </para> - <para> - <function>sybase_result</function> returns the contents of one - cell from a Sybase result set. The field argument can be the - field's offset, or the field's name, or the field's table dot - field's name (tablename.fieldname). If the column name has been - aliased ('select foo as bar from...'), use the alias instead of - the column name. - </para> - <para> - When working on large result sets, you should consider using one - of the functions that fetch an entire row (specified below). As - these functions return the contents of multiple cells in one - function call, they're MUCH quicker than sybase_result(). Also, - note that specifying a numeric offset for the field argument is - much quicker than specifying a fieldname or tablename.fieldname - argument. - </para> - <para> - Recommended high-performance alternatives: - <function>sybase_fetch_row</function>, - <function>sybase_fetch_array</function> and - <function>sybase_fetch_object</function>. - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-result"> + <refnamediv> + <refname>sybase_result</refname> + <refpurpose>Get result data</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>string</type><methodname>sybase_result</methodname> + <methodparam><type>resource</type><parameter>result</parameter></methodparam> + <methodparam><type>int</type><parameter>row</parameter></methodparam> + <methodparam><type>mixed</type><parameter>field</parameter></methodparam> + </methodsynopsis> + <para> + Returns the contents of the cell at the row and offset in + the specified Sybase result set. + </para> + <para> + <function>sybase_result</function> returns the contents of one + cell from a Sybase result set. The field argument can be the + field's offset, or the field's name, or the field's table dot + field's name (tablename.fieldname). If the column name has been + aliased ('select foo as bar from...'), use the alias instead of + the column name. + </para> + <para> + When working on large result sets, you should consider using one + of the functions that fetch an entire row (specified below). As + these functions return the contents of multiple cells in one + function call, they're MUCH quicker than sybase_result(). Also, + note that specifying a numeric offset for the field argument is + much quicker than specifying a fieldname or tablename.fieldname + argument. + </para> + <para> + Recommended high-performance alternatives: + <function>sybase_fetch_row</function>, + <function>sybase_fetch_array</function> and + <function>sybase_fetch_object</function>. + </para> + </refsect1> +</refentry>  +  - <refentry id="function.sybase-select-db"> - <refnamediv> - <refname>sybase_select_db</refname> - <refpurpose>Selects a Sybase database</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>bool</type><methodname>sybase_select_db</methodname> - <methodparam><type>string</type><parameter>database_name</parameter></methodparam> - <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_select_db</function> sets the current active - database on the server that's associated with the specified link - identifier. If no link identifier is specified, the last opened - link is assumed. If no link is open, the function will try to - establish a link as if <function>sybase_connect</function> was - called, and use it. - </para> - <para> - &return.success; - </para> - <para> - Every subsequent call to <function>sybase_query</function> will be - made on the active database. - </para> - <para> - See also - <function>sybase_connect</function>, - <function>sybase_pconnect</function> and - <function>sybase_query</function> - </para> - </refsect1> - </refentry> +<refentry id="function.sybase-select-db"> + <refnamediv> + <refname>sybase_select_db</refname> + <refpurpose>Selects a Sybase database</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>bool</type><methodname>sybase_select_db</methodname> + <methodparam><type>string</type><parameter>database_name</parameter></methodparam> + <methodparam choice="opt"><type>resource</type><parameter>link_identifier</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_select_db</function> sets the current active + database on the server that's associated with the specified link + identifier. If no link identifier is specified, the last opened + link is assumed. If no link is open, the function will try to + establish a link as if <function>sybase_connect</function> was + called, and use it. + </para> + <para> + &return.success; + </para> + <para> + Every subsequent call to <function>sybase_query</function> will be + made on the active database. + </para> + <para> + See also + <function>sybase_connect</function>, + <function>sybase_pconnect</function> and + <function>sybase_query</function> + </para> + </refsect1> +</refentry>  - <refentry id="function.sybase-set-message-handler"> - <refnamediv> - <refname>sybase_set_message_handler</refname> - <refpurpose>Sets the handler called when a server message is raised</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>bool</type><methodname>sybase_set_message_handler</methodname> - <methodparam><type>callback</type><parameter>handler</parameter></methodparam> - <methodparam choice="opt"><type>resource</type><parameter>connection</parameter></methodparam> - </methodsynopsis> - <para> - <function>sybase_set_message_handler</function> sets a user function to - handle messages generated by the server. You may specify the name of a - global function, or use an array to specify an object reference and a - method name. - </para> - - &sybase.ct.only; + +<refentry id="function.sybase-set-message-handler"> + <refnamediv> + <refname>sybase_set_message_handler</refname> + <refpurpose>Sets the handler called when a server message is raised</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>bool</type><methodname>sybase_set_message_handler</methodname> + <methodparam><type>callback</type><parameter>handler</parameter></methodparam> + <methodparam choice="opt"><type>resource</type><parameter>connection</parameter></methodparam> + </methodsynopsis> + <para> + <function>sybase_set_message_handler</function> sets a user function to + handle messages generated by the server. You may specify the name of a + global function, or use an array to specify an object reference and a + method name. + </para> + + &sybase.ct.only; - <para> - The handler expects five arguments in the following order: message - number, severity, state, line number and description. The first four are - integers. The last is a string. If the function returns &false;, PHP - generates an ordinary error message. - </para> - <para> - &return.success; - </para> - <note> - <para> - The <parameter>connection</parameter> parameter was added in - PHP 4.3.5. - </para> - </note> - <para> - <example> - <title><function>sybase_set_message_handler</function> callback function</title> - <programlisting role="php"> + <para> + The handler expects five arguments in the following order: message + number, severity, state, line number and description. The first four are + integers. The last is a string. If the function returns &false;, PHP + generates an ordinary error message. + </para> + <para> + &return.success; + </para> + <note> + <para> + The <parameter>connection</parameter> parameter was added in + PHP 4.3.5. + </para> + </note> + <para> + <example> + <title><function>sybase_set_message_handler</function> callback function</title> + <programlisting role="php"> <![CDATA[ <?php function msg_handler($msgnumber, $severity, $state, $line, $text) @@ -50,11 +50,11 @@ sybase_set_message_handler('msg_handler'); ?> ]]> - </programlisting> - </example> - <example> - <title><function>sybase_set_message_handler</function> callback to a class</title> - <programlisting role="php"> + </programlisting> + </example> + <example> + <title><function>sybase_set_message_handler</function> callback to a class</title> + <programlisting role="php"> <![CDATA[ <?php class Sybase { @@ -68,11 +68,11 @@ sybase_set_message_handler(array($sybase, 'handler')); ?> ]]> - </programlisting> - </example> - <example> - <title><function>sybase_set_message_handler</function> unhandled messages</title> - <programlisting role="php"> + </programlisting> + </example> + <example> + <title><function>sybase_set_message_handler</function> unhandled messages</title> + <programlisting role="php"> <![CDATA[ <?php // Return FALSE from this function to indicate you can't handle @@ -89,11 +89,11 @@ sybase_set_message_handler('msg_handler'); ?> ]]> - </programlisting> - </example> - </para> - </refsect1> - </refentry> + </programlisting> + </example> + </para> + </refsect1> +</refentry>  - <refentry id="function.sybase-unbuffered-query"> - <refnamediv> - <refname>sybase_unbuffered_query</refname> - <refpurpose>Send a Sybase query and do not block</refpurpose> - </refnamediv> - <refsect1> - <title>Description</title> - <methodsynopsis> - <type>resource</type><methodname>sybase_unbuffered_query</methodname> - <methodparam><type>string</type><parameter>query</parameter></methodparam> - <methodparam><type>resource</type><parameter>link_identifier</parameter></methodparam> - <methodparam choice="opt"><type>bool</type><parameter>store_result</parameter></methodparam> - </methodsynopsis> - <para> - Returns a positive Sybase result identifier on success, or - &false; on error. - </para> + +<refentry id="function.sybase-unbuffered-query"> + <refnamediv> + <refname>sybase_unbuffered_query</refname> + <refpurpose>Send a Sybase query and do not block</refpurpose> + </refnamediv> + <refsect1> + <title>Description</title> + <methodsynopsis> + <type>resource</type><methodname>sybase_unbuffered_query</methodname> + <methodparam><type>string</type><parameter>query</parameter></methodparam> + <methodparam><type>resource</type><parameter>link_identifier</parameter></methodparam> + <methodparam choice="opt"><type>bool</type><parameter>store_result</parameter></methodparam> + </methodsynopsis> + <para> + Returns a positive Sybase result identifier on success, or + &false; on error. + </para> + + &sybase.ct.only; - &sybase.ct.only; - - <para> - <function>sybase_unbuffered_query</function> sends a query to the - currently active database on the server that's associated with the specified - link identifier. If the link identifier isn't specified, the last - opened link is assumed. If no link is open, the function tries to - establish a link as if <function>sybase_connect</function> was - called, and use it. - </para> - <para> - Unlike <function>sybase_query</function>, - <function>sybase_unbuffered_query</function> reads only the first - row of the result set. <function>sybase_fetch_array</function> and similar - function read more rows as needed. <function>sybase_data_seek</function> - reads up to the target row. The behavior may produce better performance - for large result sets. - </para> - <para> - <function>sybase_num_rows</function> will only return the correct number - of rows if all result sets have been read. To Sybase, the number of rows - is not known and is therefore computed by the client implementation. - </para> - <note> - <para> - If you don't read all of the resultsets prior to executing the next query, - PHP will raise a warning and cancel all of the pending results. To get rid of - this, use <function>sybase_free_result</function> which will cancel pending - results of an unbuffered query. - </para> - </note> - <para> - The optional <parameter>store_result</parameter> can be &false; to indicate - the resultsets shouldn't be fetched into memory, thus minimizing memory usage - which is particularly interesting with very large resultsets. - </para> - <para> - <example> - <title><function>sybase_unbuffered_query</function> example</title> - <programlisting role="php"> + <para> + <function>sybase_unbuffered_query</function> sends a query to the + currently active database on the server that's associated with the specified + link identifier. If the link identifier isn't specified, the last + opened link is assumed. If no link is open, the function tries to + establish a link as if <function>sybase_connect</function> was + called, and use it. + </para> + <para> + Unlike <function>sybase_query</function>, + <function>sybase_unbuffered_query</function> reads only the first + row of the result set. <function>sybase_fetch_array</function> and similar + function read more rows as needed. <function>sybase_data_seek</function> + reads up to the target row. The behavior may produce better performance + for large result sets. + </para> + <para> + <function>sybase_num_rows</function> will only return the correct number + of rows if all result sets have been read. To Sybase, the number of rows + is not known and is therefore computed by the client implementation. + </para> + <note> + <para> + If you don't read all of the resultsets prior to executing the next query, + PHP will raise a warning and cancel all of the pending results. To get rid of + this, use <function>sybase_free_result</function> which will cancel pending + results of an unbuffered query. + </para> + </note> + <para> + The optional <parameter>store_result</parameter> can be &false; to indicate + the resultsets shouldn't be fetched into memory, thus minimizing memory usage + which is particularly interesting with very large resultsets. + </para> + <para> + <example> + <title><function>sybase_unbuffered_query</function> example</title> + <programlisting role="php"> <![CDATA[ <?php @@ -78,15 +78,15 @@ ?> ]]> - </programlisting> - </example> - </para> - <para> - See also - <function>sybase_query</function>. - </para> - </refsect1> - </refentry> + </programlisting> + </example> + </para> + <para> + See also + <function>sybase_query</function>. + </para> + </refsect1> +</refentry> <!-- Keep this comment at the end of the file Local variables: