# php_manual

id: ctype_alnum
type: function
doc:
<comment>Description:</comment>
  Check for alphanumeric character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are alphanumeric.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong> is either a letter or a digit, <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>ctype_alpha()</strong>
   * <strong>ctype_digit()</strong>
   * <strong>setlocale()</strong>


id: ctype_alpha
type: function
doc:
<comment>Description:</comment>
  Check for alphabetic character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are alphabetic. In the standard <return>C</return>
  locale letters are just  <return>[A-Za-z]</return> and <strong>ctype_alpha()</strong> is  equivalent to <return>(ctype_upper($text) ||
  ctype_lower($text))</return> if $text is just a single character, but other languages have letters that
  are considered neither upper nor lower case.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong> is  a letter from the current locale, <info>false</info>
        otherwise.

<comment>See Also:</comment>
   * <strong>ctype_upper()</strong>
   * <strong>ctype_lower()</strong>
   * <strong>setlocale()</strong>


id: ctype_cntrl
type: function
doc:
<comment>Description:</comment>
  Check for control character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are control characters. Control
  characters are e.g. line feed, tab, escape.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong> is  a control character from the current locale,
        <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>ctype_print()</strong>


id: ctype_digit
type: function
doc:
<comment>Description:</comment>
  Check for numeric character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are numerical.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in the string <strong>$text</strong> is a decimal digit, <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>ctype_alnum()</strong>
   * <strong>ctype_xdigit()</strong>
   * <strong>is_numeric()</strong>
   * <strong>is_int()</strong>
   * <strong>is_string()</strong>


id: ctype_graph
type: function
doc:
<comment>Description:</comment>
  Check for any printable character(s) except space
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, creates visible output.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong> is  printable and actually creates visible output
        (no white space), <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>ctype_alnum()</strong>
   * <strong>ctype_print()</strong>
   * <strong>ctype_punct()</strong>


id: ctype_lower
type: function
doc:
<comment>Description:</comment>
  Check for lowercase character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are lowercase letters.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong> is  a lowercase letter in the current locale.

<comment>See Also:</comment>
   * <strong>ctype_alpha()</strong>
   * <strong>ctype_upper()</strong>
   * <strong>setlocale()</strong>


id: ctype_print
type: function
doc:
<comment>Description:</comment>
  Check for printable character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are printable.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong>  will actually create output (including blanks).
        Returns <info>false</info> if  <strong>$text</strong> contains control characters or characters  that do not have any
        output or control function at all.

<comment>See Also:</comment>
   * <strong>ctype_cntrl()</strong>
   * <strong>ctype_graph()</strong>
   * <strong>ctype_punct()</strong>


id: ctype_punct
type: function
doc:
<comment>Description:</comment>
  Check for any printable character which is not whitespace or an
     alphanumeric character
    
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are punctuation character.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong>  is printable, but neither letter, digit or blank,
        <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>ctype_cntrl()</strong>
   * <strong>ctype_graph()</strong>


id: ctype_space
type: function
doc:
<comment>Description:</comment>
  Check for whitespace character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, creates whitespace.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong>  creates some sort of white space, <info>false</info> otherwise.
        Besides the  blank character this also includes tab, vertical tab, line feed, carriage
        return and form feed characters.

<comment>See Also:</comment>
   * <strong>ctype_cntrl()</strong>
   * <strong>ctype_graph()</strong>
   * <strong>ctype_punct()</strong>


id: ctype_upper
type: function
doc:
<comment>Description:</comment>
  Check for uppercase character(s)
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are uppercase characters.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong> is  an uppercase letter in the current locale.

<comment>See Also:</comment>
   * <strong>ctype_alpha()</strong>
   * <strong>ctype_lower()</strong>
   * <strong>setlocale()</strong>


id: ctype_xdigit
type: function
doc:
<comment>Description:</comment>
  Check for character(s) representing a hexadecimal digit
    
  
  Checks if all of the characters in the provided <info>string</info>, <strong>$text</strong>, are hexadecimal 'digits'.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$text</strong>  The tested string. 
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.
                
                
                Dacă e furnizat un <info>integer</info> cu valoarea între -128 și 255 inclusiv,
                el este interpretat ca o valoare ASCII a unui singur caracter (valorilor negative
                li se adaugă 256 pentru a permite caractere din domeniul ASCII extins). Orice alt
                întreg este interpretat ca un string conținând cifrele zecimale ale întregului.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if every character in <strong>$text</strong> is  a hexadecimal 'digit', that is a decimal digit
        or a character from  <return>[A-Fa-f]</return> , <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>ctype_digit()</strong>


id: cubrid_affected_rows
type: function
doc:
<comment>Description:</comment>
  Return the number of rows affected by the last SQL statement
  
  The <strong>cubrid_affected_rows()</strong> function is used to get the number of rows affected by the SQL
  statement (INSERT, DELETE, UPDATE).

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection. If the connection identifier is not specified,
                              the last link opend by <strong>cubrid_connect()</strong> is assumed.
  <info>resource</info>  <strong>$req_identifier </strong>  Request Identifier, could be returned from either <strong>cubrid_prepare()</strong> or
                              <strong>cubrid_execute()</strong>.  If the request identifier is not specified, the
                              last identifier requested by  <strong>cubrid_prepare()</strong> or <strong>cubrid_execute()</strong> is
                              assumed.

<comment>Return:</comment>
  <info>int</info>  Number of rows affected by the SQL statement, when process is successful.
       
       -1, when SQL statement is not INSERT, DELETE or UPDATE.
       
       <info>false</info>, when the request identifier is not specified, and there is no last request.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>


id: cubrid_bind
type: function
doc:
<comment>Description:</comment>
  Bind variables to a prepared statement as parameters
  
  The <strong>cubrid_bind()</strong> function is used to bind values to a corresponding named or question mark
  placeholder in the SQL statement that was passed to <strong>cubrid_prepare()</strong>. If <strong>$bind_value_type</strong> is not
  given, string will be the default.
  
  If the type of data to be bound is BLOB/CLOB, CUBRID will try to map the data as a PHP stream. If
  the actually bind value type is not stream, CUBRID will convert it to string, and use it as the
  full path and file name of a file on the client filesystem.
  
  If the type of data to be bound explicitly is ENUM, the $bind_value argument should be the enum
  element which is in string format.
  
  In CUBRID shard envrioment, the $bind_value_type must be included in  the cubrid_bind function.
  
  The following table shows the types of substitute values.
  
  CUBRID Bind Date TypesSupportBind TypeCorresponding SQL TypeSupportedSTRINGCHAR,
  VARCHARNCHARNCHAR, NVARCHARBITBIT, VARBITNUMERIC or NUMBERSHORT, INT,
  NUMERICFLOATFLOATDOUBLEDOUBLETIMETIMEDATEDATETIMESTAMPTIMESTAMPOBJECTOBJECTENUMENUMBLOBBLOBCLOBCLOBNULLNULLNot
  supportedSETSETMULTISETMULTISETSEQUENCESEQUENCE

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier </strong>  Request identifier as a result of <strong>cubrid_prepare()</strong>.
  <info>int     </info>  <strong>$bind_index     </strong>  Location of binding parameters. It starts with 1.
  <info>mixed   </info>  <strong>$bind_value     </strong>  Actual value for binding.
  <info>string  </info>  <strong>$bind_value_type</strong>  A type of the value to bind. (It is omitted by default. Thus, the
                              system internally uses string by default. However, you need to specify
                              the exact type of the value as an argument when they are NCHAR, BIT,
                              or BLOB/CLOB).

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_prepare()</strong>


id: cubrid_client_encoding
type: function
doc:
<comment>Description:</comment>
  Return the current CUBRID connection charset
  
  This function returns the current CUBRID connection charset and is similar to the CUBRID function
  <strong>cubrid_get_charset()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection. If the connection identifier is not specified,
                              the last link opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>string</info>  A string that represents the CUBRID connection charset; on success.
          
          <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_get_charset()</strong>


id: cubrid_close
type: function
doc:
<comment>Description:</comment>
  Close CUBRID connection
  
  The <strong>cubrid_close()</strong> function ends the transaction currently in process, closes the connection
  handle and disconnects from server. If there is any request handles not closed yet at this point,
  they will be closed. It is similar to the CUBRID function <strong>cubrid_disconnect()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection identifier. If the connection identifier is not
                              specified, the last connection opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_disconnect()</strong>
   * <strong>cubrid_connect()</strong>
   * <strong>cubrid_connect_with_url()</strong>


id: cubrid_close_prepare
type: function
doc:
<comment>Description:</comment>
  Close the request handle 
  
  The <strong>cubrid_close_prepare()</strong> function closes the request handle given by the <strong>$req_identifier</strong>
  argument, and releases the memory region related to the handle. It is an alias of
  <strong>cubrid_close_request()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.

<comment>Return:</comment>
  <info>bool</info>  Return <info>true</info> on success.

<comment>See Also:</comment>
   * <strong>cubrid_close_request()</strong>


id: cubrid_close_request
type: function
doc:
<comment>Description:</comment>
  Close the request handle 
  
  The <strong>cubrid_close_request()</strong> function closes the request handle given by the <strong>$req_identifier</strong>
  argument, and releases the memory region related to the handle. It is an alias of
  <strong>cubrid_close_prepare()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.

<comment>Return:</comment>
  <info>bool</info>  Return <info>true</info> on success.

<comment>See Also:</comment>
   * <strong>cubrid_close_prepare()</strong>


id: cubrid_col_get
type: function
doc:
<comment>Description:</comment>
  Get contents of collection type column using OID
  
  The <strong>cubrid_col_get()</strong> function is used to get contents of the elements of the collection type (set,
  multiset, sequence) attribute you requested as an array.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance that you want to read.
  <info>string  </info>  <strong>$attr_name      </strong>  Attribute name that you want to read from the instance.

<comment>Return:</comment>
  <info>array</info>  Array (0-based numerical array) containing the elements you requested, when process is
         successful;
         
         <info>false</info> (to distinguish the error from the situation of attribute having empty collection or
         NULL, in case of error, a warning message is shown; in such case you can check the error by
         using <strong>cubrid_error_code()</strong>), when process is unsuccessful.


id: cubrid_col_size
type: function
doc:
<comment>Description:</comment>
  Get the number of elements in collection type column using OID
  
  The <strong>cubrid_col_size()</strong> function is used to get the number of elements in a collection type (set,
  multiset, sequence) attribute.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID the instance that you want to work with.
  <info>string  </info>  <strong>$attr_name      </strong>  Name of the attribute that you want to work with.

<comment>Return:</comment>
  <info>int</info>  Number of elements, when process is successful.
       
       <info>false</info>, when process is unsuccessful.


id: cubrid_column_names
type: function
doc:
<comment>Description:</comment>
  Get the column names in result
  
  The <strong>cubrid_column_names()</strong> function is used to get the column names of the query result by using
  <strong>$req_identifier</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.

<comment>Return:</comment>
  <info>array</info>  Array of string values containing the column names, when process is successful.
         
         <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_prepare()</strong>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_column_types()</strong>


id: cubrid_column_types
type: function
doc:
<comment>Description:</comment>
  Get column types in result
  
  The <strong>cubrid_column_types()</strong> function gets column types of query results by using <strong>$req_identifier</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.

<comment>Return:</comment>
  <info>array</info>  Array of string values containing the column types, when process is successful.
         
         <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_column_names()</strong>
   * <strong>cubrid_prepare()</strong>
   * <strong>cubrid_execute()</strong>


id: cubrid_commit
type: function
doc:
<comment>Description:</comment>
  Commit a transaction
  
  The <strong>cubrid_commit()</strong> function is used to execute commit on the transaction pointed by
  <strong>$conn_identifier</strong>, currently in progress. Connection to the server is closed after the
  <strong>cubrid_commit()</strong> function is called; However,  the connection handle is still valid.
  
  In CUBRID PHP, auto-commit mode is disabled by default for transaction management.  You can set it
  by using <strong>cubrid_set_autocommit()</strong>.  You can get its status by using <strong>cubrid_get_autocommit()</strong>. Before
  you start a transaction,  remember to disable the auto-commit mode.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_rollback()</strong>
   * <strong>cubrid_get_autocommit()</strong>
   * <strong>cubrid_set_autocommit()</strong>


id: cubrid_connect
type: function
doc:
<comment>Description:</comment>
  Open a connection to a CUBRID Server
  
  The <strong>cubrid_connect()</strong> function is used to establish the environment for connecting to your server
  by using your server address, port number, database name, user name, and password. If the user
  name and password is not given, then the "PUBLIC" connection will be made by default.

<comment>Param:</comment>
  <info>string</info>  <strong>$host    </strong>  Host name or IP address of CUBRID CAS server.
  <info>int   </info>  <strong>$port    </strong>  Port number of CUBRID CAS server (BROKER_PORT configured in
                     $CUBRID/conf/cubrid_broker.conf).
  <info>string</info>  <strong>$dbname  </strong>  Name of database.
  <info>string</info>  <strong>$userid  </strong>  User name for the database. If not given, the default value is "public".
  <info>string</info>  <strong>$passwd  </strong>  User password. If not given, the default value is "".
  <info>bool  </info>  <strong>$new_link</strong>  If a second call is made to <strong>cubrid_connect()</strong> with the same arguments, no new
                     connection will be established, but instead, the connection identifier of the
                     already opened connection will be returned. The <strong>$new_link</strong> parameter modifies
                     this behavior and makes <strong>cubrid_connect()</strong> always open a new connection, even if
                     <strong>cubrid_connect()</strong> was called before with the same parameters.

<comment>Return:</comment>
  <info>resource</info>  Connection identifier, when process is successful.
            
            <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_pconnect()</strong>
   * <strong>cubrid_connect_with_url()</strong>
   * <strong>cubrid_pconnect_with_url()</strong>
   * <strong>cubrid_disconnect()</strong>
   * <strong>cubrid_close()</strong>


id: cubrid_connect_with_url
type: function
doc:
<comment>Description:</comment>
  Establish the environment for connecting to CUBRID server
  
  The <strong>cubrid_connect_with_url()</strong> function is used to establish the environment for connecting to your
  server by using connection information passed with an url string argument. If the HA feature is
  enabled in CUBRID, you must specify the connection information of the standby server, which is
  used for failover when failure occurs, in the url string argument of this function. If the user
  name and password is not given, then the "PUBLIC" connection will be made by default.
  
  \<url&gt; ::= CUBRID:\<host&gt;:\<db_name&gt;:\<db_user&gt;:\<db_password&gt;:[?\<properties&gt;]
  
  \<properties&gt; ::= \<property&gt; [&\<property&gt;]
  
  \<properties&gt; ::= alhosts=\<alternative_hosts&gt;[ &rctime=\<time&gt;]
  
  \<properties&gt; ::= login_timeout=\<milli_sec&gt;
  
  \<properties&gt; ::= query_timeout=\<milli_sec&gt;
  
  \<properties&gt; ::= disconnect_on_query_timeout=true|false
  
  \<alternative_hosts&gt; ::= \<standby_broker1_host&gt;:\<port&gt; [,\<standby_broker2_host&gt;:\<port&gt;]
  
  \<host&gt; := HOSTNAME | IP_ADDR
  
  \<time&gt; := SECOND
  
  \<milli_sec&gt; := MILLI SECOND
  
  host : A host name or IP address of the master databasedb_name : A name of the databasedb_user : A
  name of the database userdb_password : A database user password alhosts : Specifies the broker
  information of the standby server, which is used for failover when it is impossible to connect to
  the active server.  You can specify multiple brokers for failover, and the connection to the
  brokers is attempted in the order listed in alhosts rctime : An interval between the attempts to
  connect to the active broker in which failure occurred. After a failure occurs, the system
  connects to the  broker specified by althosts (failover), terminates the transaction, and then
  attempts to connect to the active broker of the master database at every rctime.  The default
  value is 600 seconds. login_timeout : Timeout value (unit: msec.) for database login. The default
  value is 0, which means infinite postponement.  query_timeout : Timeout value (unit: msec.) for
  query request. Upon timeout, a message to cancel requesting a query transferred to server is sent.
  The return  value can depend on the disconnect_on_query_timeout configuration; even though the
  message to cancel a request is sent to server, that request may succeed.
  disconnect_on_query_timeout : Configures a value whether to immediately return an error of
  function being executed upon timeout. The default value is false.
  
  <return>?</return> and <return>:</return> that are used as identifiers in PHP connection URL can't be included in the password. The
  following is an example of a password that is invalid to use as connection URL because it contains
  "<return>?:</return>".
  
  $url = "CUBRID:localhost:33000:tdb:dba:12?:?login_timeout=100";
  
  Passwords that contain <return>?</return> or <return>:</return> may be passed as a separate parameter.
  
  $url = "CUBRID:localhost:33000:tbd:::?login_timeout=100";
  
  $conn = cubrid_connect_with_url($url, "dba", "12?");
  
  If user or password is empty,you can't delete "<return>:</return>",the following is an example.
  
  $url = "CUBRID:localhost:33000:demodb:::";

<comment>Param:</comment>
  <info>string</info>  <strong>$conn_url</strong>  A character string that contains server connection information.
  <info>string</info>  <strong>$userid  </strong>  User name for the database.
  <info>string</info>  <strong>$passwd  </strong>  User password.
  <info>bool  </info>  <strong>$new_link</strong>  If a second call is made to <strong>cubrid_connect_with_url()</strong> with the same arguments,
                     no new connection will be established, but instead, the connection identifier
                     of the already opened connection will be returned. The <strong>$new_link</strong> parameter
                     modifies this behavior and makes <strong>cubrid_connect_with_url()</strong> always open a new
                     connection, even if <strong>cubrid_connect_with_url()</strong> was called before with the same
                     parameters.

<comment>Return:</comment>
  <info>resource</info>  Connection identifier, when process is successful.
            
            <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_connect()</strong>
   * <strong>cubrid_pconnect()</strong>
   * <strong>cubrid_pconnect_with_url()</strong>
   * <strong>cubrid_disconnect()</strong>
   * <strong>cubrid_close()</strong>


id: cubrid_current_oid
type: function
doc:
<comment>Description:</comment>
  Get OID of the current cursor location
  
  The <strong>cubrid_current_oid()</strong> function is used to get the oid of the current cursor location from the
  query result.  To use <strong>cubrid_current_oid()</strong>, the query executed must be a updatable query, and the
  CUBRID_INCLUDE_OID option must be included during the query execution.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.

<comment>Return:</comment>
  <info>string</info>  Oid of current cursor location, when process is successful
          
          <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>


id: cubrid_data_seek
type: function
doc:
<comment>Description:</comment>
  Move the internal row pointer of the CUBRID result
  
  This function performs the moving of the internal row pointer of the CUBRID result (associated
  with the specified result identifier) to point to a specific row number. There are functions, such
  as <strong>cubrid_fetch_assoc()</strong>, which use the current stored value of <strong>$row number</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result    </strong>  The result.
  <info>int     </info>  <strong>$row_number</strong>  This is the desired row number of the new result pointer.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success or <info>false</info> on failure.


id: cubrid_db_name
type: function
doc:
<comment>Description:</comment>
  Get db name from results of cubrid_list_dbs
  
  Retrieve the database name from a call to <strong>cubrid_list_dbs()</strong>.

<comment>Param:</comment>
  <info>array</info>  <strong>$result</strong>  The result pointer from a call to <strong>cubrid_list_dbs()</strong>.
  <info>int  </info>  <strong>$index </strong>  The index into the result set.

<comment>Return:</comment>
  <info>string</info>  Returns the database name on success, and <info>false</info> on failure. If <info>false</info> is returned, use
          <strong>cubrid_error()</strong> to determine the nature of the error.

<comment>See Also:</comment>
   * <strong>cubrid_list_dbs()</strong>


id: cubrid_disconnect
type: function
doc:
<comment>Description:</comment>
  Close a database connection
  
  The <strong>cubrid_disconnect()</strong> function closes the connection handle and disconnects from server. If any
  request handle is not closed at this point,  it will be closed. It is similar to the CUBRID MySQL
  compatible function <strong>cubrid_close()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_close()</strong>
   * <strong>cubrid_connect()</strong>
   * <strong>cubrid_connect_with_url()</strong>


id: cubrid_drop
type: function
doc:
<comment>Description:</comment>
  Delete an instance using OID
  
  The <strong>cubrid_drop()</strong> function is used to delete an instance from database by using the <strong>$oid</strong> of the
  instance.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  Oid of the instance that you want to delete.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_is_instance()</strong>


id: cubrid_errno
type: function
doc:
<comment>Description:</comment>
  Return the numerical value of the error message from previous CUBRID operation
  
  Returns the error number from the last CUBRID function.
  
  The <strong>cubrid_errno()</strong> function is used to get the error code of the error that occurred during the
  API execution.  Usually, it gets the error code when API returns false as its return value.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection identifier. If the connection identifier is not
                              specified, the last connection opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>int</info>  Returns the error number from the last CUBRID function, or <return>0</return> (zero) if no error occurred.

<comment>See Also:</comment>
   * <strong>cubrid_error()</strong>
   * <strong>cubrid_error_code()</strong>
   * <strong>cubrid_error_msg()</strong>


id: cubrid_error
type: function
doc:
<comment>Description:</comment>
  Get the error message
  
  The <strong>cubrid_error()</strong> function is used to get the error message that occurred during the use of
  CUBRID API. Usually, it gets error message when API returns false as its return value.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  The CUBRID connection.

<comment>Return:</comment>
  <info>string</info>  Error message that occurred.

<comment>See Also:</comment>
   * <strong>cubrid_errno()</strong>
   * <strong>cubrid_error_code()</strong>
   * <strong>cubrid_error_msg()</strong>


id: cubrid_error_code
type: function
doc:
<comment>Description:</comment>
  Get error code for the most recent function call
  
  The <strong>cubrid_error_code()</strong> function is used to get the error code of the error that occurred during
  the API execution. Usually, it gets the error code when API returns false as its return value.

<comment>Return:</comment>
  <info>int</info>  Error code of the error that occurred, or <return>0</return> (zero) if no error occurred.

<comment>See Also:</comment>
   * <strong>cubrid_error_code_facility()</strong>
   * <strong>cubrid_error_msg()</strong>


id: cubrid_error_code_facility
type: function
doc:
<comment>Description:</comment>
  Get the facility code of error
  
  The <strong>cubrid_error_code_facility()</strong> function is used to get the facility code (level in which the
  error occurred) from the error code of the error that occurred during the API execution. Usually,
  you can get the error code when API returns false as its return value.

<comment>Return:</comment>
  <info>int</info>  Facility code of the error code that occurred: CUBRID_FACILITY_DBMS, CUBRID_FACILITY_CAS,
       CUBRID_FACILITY_CCI, CUBRID_FACILITY_CLIENT

<comment>See Also:</comment>
   * <strong>cubrid_error_code()</strong>
   * <strong>cubrid_error_msg()</strong>


id: cubrid_error_msg
type: function
doc:
<comment>Description:</comment>
  Get last error message for the most recent function call
  
  The <strong>cubrid_error_msg()</strong> function is used to get the error message that occurred during the use of
  CUBRID API. Usually, it gets error message when API returns false as its return value.

<comment>Return:</comment>
  <info>string</info>  Error message that occurred.

<comment>See Also:</comment>
   * <strong>cubrid_error_code()</strong>
   * <strong>cubrid_error_code_facility()</strong>


id: cubrid_execute
type: function
doc:
<comment>Description:</comment>
  Execute a prepared SQL statement
  
  The <strong>cubrid_execute()</strong> function is used to execute the given SQL statement. It executes the query by
  using <strong>$conn_identifier</strong> and SQL, and then returns the request identifier created. It is used for
  simple execution of query, where the parameter binding is not needed. In addition, the
  <strong>cubrid_execute()</strong> function is used to execute the prepared statement by means of <strong>cubrid_prepare()</strong>
  and <strong>cubrid_bind()</strong>. At this time, you need to specify arguments of <strong>$request_identifier</strong> and <strong>$option</strong>.
  
  The <strong>$option</strong> is used to determine whether to get OID after query execution and whether to execute
  the query in synchronous or asynchronous mode. CUBRID_INCLUDE_OID and CUBRID_ASYNC (or
  CUBRID_EXEC_QUERY_ALL if you want to execute multiple SQL statements) can be specified by using a
  bitwise OR operator. If not specified, neither of them isselected. If the flag
  CUBRID_EXEC_QUERY_ALL is set, a synchronous mode (sync_mode) is used to retrieve query results,
  and in such cases the following rules are applied:
  
  The return value is the result of the first query. If an error occurs in any query, the execution
  is processed as a failure.  In a query composed of q1 q2 q3, if an error occurs in q2 after q1
  succeeds the execution, the result of q1 remains valid. That is, the previous successful query
  executions are not rolled back when an error occurs.  If a query is executed successfully, the
  result of the second query can be obtained using <strong>cubrid_next_result()</strong>.
  
  If the first argument is <strong>$request_identifier</strong> to execute the <strong>cubrid_prepare()</strong> function, you can
  specify an option, CUBRID_ASYNC only.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier   </strong>  Connection identifier.
  <info>string  </info>  <strong>$sql               </strong>  SQL to be executed.
  <info>int     </info>  <strong>$option            </strong>  Query execution option CUBRID_INCLUDE_OID, CUBRID_ASYNC,
                                 CUBRID_EXEC_QUERY_ALL.
  <info>resource</info>  <strong>$request_identifier</strong>  <strong>cubrid_prepare()</strong> identifier.

<comment>Return:</comment>
  <info>resource</info>  Request identifier, when process is successful and first param is conn_identifier; <info>true</info>,
            when process is successful and first argument is request_identifier.
            
            <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_prepare()</strong>
   * <strong>cubrid_bind()</strong>
   * <strong>cubrid_next_result()</strong>
   * <strong>cubrid_close_request()</strong>
   * <strong>cubrid_commit()</strong>
   * <strong>cubrid_rollback()</strong>


id: cubrid_fetch
type: function
doc:
<comment>Description:</comment>
  Fetch the next row from a result set
  
  The <strong>cubrid_fetch()</strong> function is used to get a single row from the query result.  The cursor
  automatically moves to the next row after getting the result.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$type  </strong>  Array type of the fetched result CUBRID_NUM, CUBRID_ASSOC, CUBRID_BOTH,
                     CUBRID_OBJECT. If you want to operate the lob object, you can use CUBRID_LOB.

<comment>Return:</comment>
  <info>mixed</info>  Result array or object, when process is successful.
         
         <info>false</info>, when there are no more rows; NULL, when process is unsuccessful.
         
         The result can be received either as an array or as an object, and you can decide which
         data type to use by setting the <strong>$type</strong> argument. The <strong>$type</strong> variable can be set to one of the
         following values:
         
         When <strong>$type</strong> argument is omitted, the result will be received using CUBRID_BOTH option as
         default. When you want to receive query result in object data type, the column name of the
         result must obey the naming rules for identifiers in PHP.  For example, column name such as
         "count(*)" cannot be received in object type.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_fetch_array()</strong>
   * <strong>cubrid_fetch_row()</strong>
   * <strong>cubrid_fetch_assoc()</strong>
   * <strong>cubrid_fetch_object()</strong>


id: cubrid_fetch_array
type: function
doc:
<comment>Description:</comment>
  Fetch a result row as an associative array, a numeric array, or both
  
  The <strong>cubrid_fetch_array()</strong> function is used to get a single row from the query result and returns an
  array. The cursor automatically moves to the next row after getting the result.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$Result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$type  </strong>  Array type of the fetched result CUBRID_NUM, CUBRID_ASSOC, CUBRID_BOTH. If you
                     need to operate the lob object, you can use CUBRID_LOB.

<comment>Return:</comment>
  <info>array</info>  Returns an array of strings that corresponds to the fetched row, when process is
         successful.
         
         <info>false</info>, when there are no more rows; NULL, when process is unsuccessful.
         
         The type of returned array depends on how type is defined. By using CUBRID_BOTH (default),
         you'll get an array with both associative and number indices, and you can decide which data
         type to use by setting the <strong>$type</strong> argument. The <strong>$type</strong> variable can be set to one of the
         following values:

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_fetch()</strong>
   * <strong>cubrid_fetch_row()</strong>
   * <strong>cubrid_fetch_assoc()</strong>
   * <strong>cubrid_fetch_object()</strong>


id: cubrid_fetch_assoc
type: function
doc:
<comment>Description:</comment>
  Return the associative array that corresponds to the fetched row
  
  This function returns the associative array, that corresponds to the fetched row, and then moves
  the internal data pointer ahead, or returns FALSE when the end is reached.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$type  </strong>  Type can only be CUBRID_LOB, this parameter will be used only when you need to
                     operate the lob object.

<comment>Return:</comment>
  <info>array</info>  Associative array, when process is successful.
         
         <info>false</info>, when there are no more rows; NULL, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_fetch()</strong>
   * <strong>cubrid_fetch_row()</strong>
   * <strong>cubrid_fetch_array()</strong>
   * <strong>cubrid_fetch_object()</strong>


id: cubrid_fetch_field
type: function
doc:
<comment>Description:</comment>
  Get column information from a result and return as an object
  
  This function returns an object with certain properties of the specific column. The properties of
  the object are:
  
  <strong>$name</strong>column name<strong>$table</strong>name of the table that the column belongs to<strong>$def</strong>default value of the
  column<strong>$max_length</strong>maximum length of the column<strong>$not_null</strong>1 if the column cannot be NULL<strong>$primary_key</strong>1
  if the column is a primary key<strong>$unique_key</strong>1 if the column is an unique key<strong>$multiple_key</strong>1 if the
  column is a non-unique key<strong>$numeric</strong>1 if the column is numeric<strong>$blob</strong>1 if the column is a BLOB<strong>$type</strong>the
  type of the column<strong>$unsigned</strong>1 if the column is unsigned<strong>$zerofill</strong>1 if the column is zero-filled
  
  column name
  
  name of the table that the column belongs to
  
  default value of the column
  
  maximum length of the column
  
  1 if the column cannot be NULL
  
  1 if the column is a primary key
  
  1 if the column is an unique key
  
  1 if the column is a non-unique key
  
  1 if the column is numeric
  
  1 if the column is a BLOB
  
  the type of the column
  
  1 if the column is unsigned
  
  1 if the column is zero-filled

<comment>Param:</comment>
  <info>resource</info>  <strong>$result      </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$field_offset</strong>  The numerical field offset. If the field offset is not specified, the
                           next field (that was not yet retrieved by this function) is retrieved.
                           The <strong>$field_offset</strong> starts at 0.

<comment>Return:</comment>
  <info>object</info>  Object with certain properties of the specific column, when process is successful.
          
          <info>false</info> on failure.


id: cubrid_fetch_lengths
type: function
doc:
<comment>Description:</comment>
  Return an array with the lengths of the values of each field from the current row
  
  This function returns an numeric array with the lengths of the values of each field from the
  current row of the result set or it returns FALSE on failure.
  
  If field data type is BLOB/CLOB, you should get its length by using <strong>cubrid_lob_size()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>

<comment>Return:</comment>
  <info>array</info>  An numeric array, when process is successful.
         
         <info>false</info> on failure.


id: cubrid_fetch_object
type: function
doc:
<comment>Description:</comment>
  Fetch the next row and return it as an object
  
  This function returns an object with the column names of the result set as properties. The values
  of these properties are extracted from the current row of the result.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result    </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>string  </info>  <strong>$class_name</strong>  The name of the class to instantiate. If not specified, a <class>stdClass</class>
                         (stdClass is PHP's generic empty class that's used when casting other types
                         to objects) object is returned.
  <info>array   </info>  <strong>$params    </strong>  An optional <info>array</info> of parameters to pass to the constructor for <strong>$class_name</strong>
                         objects.
  <info>int     </info>  <strong>$type      </strong>  Type can only be CUBRID_LOB, this parameter will be used only when you need
                         to operate the lob object.

<comment>Return:</comment>
  <info>object</info>  An object, when process is successful.
          
          <info>false</info>, when there are no more rows; NULL, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_fetch()</strong>
   * <strong>cubrid_fetch_array()</strong>
   * <strong>cubrid_fetch_assoc()</strong>
   * <strong>cubrid_fetch_row()</strong>


id: cubrid_fetch_row
type: function
doc:
<comment>Description:</comment>
  Return a numerical array with the values of the current row
  
  This function returns a numerical array with the values of the current row from the result set,
  starting from 0, and moves the internal data pointer ahead.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$type  </strong>  Type can only be CUBRID_LOB, this parameter will be used only when you need to
                     operate the lob object.

<comment>Return:</comment>
  <info>array</info>  A numerical array, when process is successful.
         
         <info>false</info>, when there are no more rows; NULL, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_fetch()</strong>
   * <strong>cubrid_fetch_array()</strong>
   * <strong>cubrid_fetch_assoc()</strong>
   * <strong>cubrid_fetch_object()</strong>


id: cubrid_field_flags
type: function
doc:
<comment>Description:</comment>
  Return a string with the flags of the given field offset
  
  This function returns a string with the flags of the given field offset separated by space. You
  can split the returned value using explode. The possible flags could be: <info>not_null</info>, <info>primary_key</info>,
  <info>unique_key</info>, <info>foreign_key</info>, <info>auto_increment</info>, <info>shared</info>, <info>reverse_index</info>, <info>reverse_unique</info> and <info>timestamp</info>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result      </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$field_offset</strong>  The numerical field offset. The <strong>$field_offset</strong> starts at 0. If
                           <strong>$field_offset</strong> does not exist, an error of level <info>E_WARNING</info> is also issued.

<comment>Return:</comment>
  <info>string</info>  A string with flags, when process is successful.
          
          <info>false</info> when invalid field_offset value.
          
          -1 if SQL sentence is not SELECT.


id: cubrid_field_len
type: function
doc:
<comment>Description:</comment>
  Get the maximum length of the specified field
  
  This function returns the maximum length of the specified field on success, or it returns FALSE on
  failure.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result      </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$field_offset</strong>  The numerical field offset. The <strong>$field_offset</strong> starts at 0. If
                           <strong>$field_offset</strong> does not exist, an error of level <info>E_WARNING</info> is also issued.

<comment>Return:</comment>
  <info>int</info>  Maximum length, when process is successful.
       
       <info>false</info> on failure.


id: cubrid_field_name
type: function
doc:
<comment>Description:</comment>
  Return the name of the specified field index
  
  This function returns the name of the specified field index on success or it returns FALSE on
  failure.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result      </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$field_offset</strong>  The numerical field offset. The <strong>$field_offset</strong> starts at 0. If
                           <strong>$field_offset</strong> does not exist, an error of level <info>E_WARNING</info> is also issued.

<comment>Return:</comment>
  <info>string</info>  Name of specified field index, on success.
          
          <info>false</info> on failure.


id: cubrid_field_seek
type: function
doc:
<comment>Description:</comment>
  Move the result set cursor to the specified field offset
  
  This function moves the result set cursor to the specified field offset. This offset is used by
  <strong>cubrid_fetch_field()</strong> if it doesn't include a field offset. It returns TRUE on success or FALSE on
  failure.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result      </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$field_offset</strong>  The numerical field offset. The <strong>$field_offset</strong> starts at 0. If
                           <strong>$field_offset</strong> does not exist, an error of level <info>E_WARNING</info> is also issued.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> on success.
        
        <info>false</info> on failure.


id: cubrid_field_table
type: function
doc:
<comment>Description:</comment>
  Return the name of the table of the specified field
  
  This function returns the name of the table of the specified field. This is useful when using
  large select queries with JOINS.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result      </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$field_offset</strong>  The numerical field offset. The <strong>$field_offset</strong> starts at 0. If
                           <strong>$field_offset</strong> does not exist, an error of level <info>E_WARNING</info> is also issued.

<comment>Return:</comment>
  <info>string</info>  Name of the table of the specified field, on success.
          
          <info>false</info> when invalid field_offset value.
          
          -1 if SQL sentence is not SELECT.


id: cubrid_field_type
type: function
doc:
<comment>Description:</comment>
  Return the type of the column corresponding to the given field offset
  
  This function returns the type of the column corresponding to the given field offset. The returned
  field type could be one of the following: "int", "real", "string", etc.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result      </strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$field_offset</strong>  The numerical field offset. The <strong>$field_offset</strong> starts at 0. If
                           <strong>$field_offset</strong> does not exist, an error of level <info>E_WARNING</info> is also issued.

<comment>Return:</comment>
  <info>string</info>  Type of the column, on success.
          
          <info>false</info> when invalid field_offset value.
          
          -1 if SQL sentence is not SELECT.


id: cubrid_free_result
type: function
doc:
<comment>Description:</comment>
  Free the memory occupied by the result data
  
  This function frees the memory occupied by the result data. It returns TRUE on success or FALSE on
  failure. Note that it can only frees the client fetch buffer now, and if you want free all memory,
  use function <strong>cubrid_close_request()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  This is the request identifier.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> on success.
        
        <info>false</info> on failure.


id: cubrid_get
type: function
doc:
<comment>Description:</comment>
  Get a column using OID
  
  The <strong>cubrid_get()</strong> function is used to get the attribute of the instance of the given <strong>$oid</strong>.  You can
  get single attribute by using string data type for the <strong>$attr</strong> argument, or many attributes by using
  array data type for the <strong>$attr</strong> argument.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance that you want to read.
  <info>mixed   </info>  <strong>$attr           </strong>  Name of the attribute that you want to read.

<comment>Return:</comment>
  <info>mixed</info>  Content of the requested attribute, when process is successful; When <strong>$attr</strong> is set with
         string data type, the result is returned as a string; when <strong>$attr</strong> is set with array data
         type (0-based numerical array), then the result is returned in associative array. When
         <strong>$attr</strong> is omitted, then all attributes are received in array form.
         
         <info>false</info> when process is unsuccessful or result is NULL (If error occurs to distinguish empty
         string from NULL, then it prints the warning message. You can check the error by using
         <strong>cubrid_error_code()</strong>)

<comment>See Also:</comment>
   * <strong>cubrid_put()</strong>


id: cubrid_get_autocommit
type: function
doc:
<comment>Description:</comment>
  Get auto-commit mode of the connection
  
  The <strong>cubrid_get_autocommit()</strong> function is used to get the status of CUBRID database connection
  auto-commit mode.
  
  For CUBRID 8.4.0, auto-commit mode is disabled by default for transaction management.
  
  For CUBRID 8.4.1, auto-commit mode is enabled by default for transaction management.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when auto-commit is on.
        
        <info>false</info>, when auto-commit is off.
        
        <info>null</info> on error.

<comment>See Also:</comment>
   * <strong>cubrid_set_autocommit()</strong>
   * <strong>cubrid_commit()</strong>


id: cubrid_get_charset
type: function
doc:
<comment>Description:</comment>
  Return the current CUBRID connection charset
  
  This function returns the current CUBRID connection charset and is similar to the CUBRID MySQL
  compatible function <strong>cubrid_client_encoding()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection.

<comment>Return:</comment>
  <info>string</info>  A string that represents the CUBRID connection charset; on success.
          
          <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_client_encoding()</strong>


id: cubrid_get_class_name
type: function
doc:
<comment>Description:</comment>
  Get the class name using OID
  
  The <strong>cubrid_get_class_name()</strong> function is used to get the class name from <strong>$oid</strong>. It doesn't work when
  selecting data from the system tables, for example db_class.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance that you want to check the existence.

<comment>Return:</comment>
  <info>string</info>  Class name when process is successful.
          
          <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_is_instance()</strong>
   * <strong>cubrid_drop()</strong>


id: cubrid_get_client_info
type: function
doc:
<comment>Description:</comment>
  Return the client library version
  
  This function returns a string that represents the client library version.

<comment>Return:</comment>
  <info>string</info>  A string that represents the client library version; on success.
          
          <info>false</info> on failure.


id: cubrid_get_db_parameter
type: function
doc:
<comment>Description:</comment>
  Returns the CUBRID database parameters
  
  This function returns the CUBRID database parameters or it returns FALSE on failure. It returns an
  associative array with the values for the following parameters:
  
  <info>PARAM_ISOLATION_LEVEL</info><info>PARAM_LOCK_TIMEOUT</info><info>PARAM_MAX_STRING_LENGTH</info><info>PARAM_AUTO_COMMIT</info>
  
  Database parametersParameterDescriptionPARAM_ISOLATION_LEVELThe transaction isolation
  level.LOCK_TIMEOUTCUBRID provides the lock timeout feature, which sets the waiting time (in
  seconds) for the lock until the transaction lock setting is allowed. The default value of the
  lock_timeout_in_secs parameter is -1, which means the application client will wait indefinitely
  until the transaction lock is allowed. PARAM_AUTO_COMMITIn CUBRID PHP, auto-commit mode is
  disabled by default for transaction management. It can be set by using <strong>cubrid_set_autocommit()</strong>.
  
  The following table shows the isolation levels from 1 to 6. It consists of table schema (row) and
  isolation level: Levels of Isolation Supported by CUBRIDNameDescriptionSERIALIZABLE (6)In this
  isolation level, problems concerning concurrency (e.g. dirty read, non-repeatable read, phantom
  read, etc.) do not occur.REPEATABLE READ CLASS with REPEATABLE READ INSTANCES (5)Another
  transaction T2 cannot update the schema of table A while transaction T1 is viewing table A.
  Transaction T1 may experience phantom read for the record R that was inserted by another
  transaction T2 when it is repeatedly retrieving a specific record.REPEATABLE READ CLASS with READ
  COMMITTED INSTANCES (or CURSOR STABILITY) (4)Another transaction T2 cannot update the schema of
  table A while transaction T1 is viewing table A. Transaction T1 may experience R read
  (non-repeatable read) that was updated and committed by another transaction T2 when it is
  repeatedly retrieving the record R.REPEATABLE READ CLASS with READ UNCOMMITTED INSTANCES
  (3)Default isolation level.  Another transaction T2 cannot update the schema of table A  while
  transaction T1 is viewing table A. Transaction T1 may experience R' read (dirty read) for the
  record that was updated but not committed by another transaction T2.READ COMMITTED CLASS with READ
  COMMITTED INSTANCES (2)Transaction T1 may experience A' read (non-repeatable read) for the table
  that was updated and committed by another transaction  T2 while it is viewing table A repeatedly.
  Transaction T1 may experience R' read (non-repeatable read) for the record that was updated and
  committed by another transaction T2 while it is retrieving the record R repeatedly.READ COMMITTED
  CLASS with READ UNCOMMITTED INSTANCES (1)Transaction T1 may experience A' read (non-repeatable
  read) for the table that was updated and committed by another transaction T2 while it is
  repeatedly viewing table A.  Transaction T1 may experience R' read (dirty read) for the record
  that was updated but not committed by another transaction T2.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection. If the connection identifier is not specified,
                              the last link opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>array</info>  An associative array with CUBRID database parameters; on success.
         
         <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_set_db_parameter()</strong>
   * <strong>cubrid_get_autocommit()</strong>


id: cubrid_get_query_timeout
type: function
doc:
<comment>Description:</comment>
  Get the query timeout value of the request
  
  The <strong>cubrid_get_query_timeout()</strong> function is used to get the query timeout of the request.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.

<comment>Return:</comment>
  <info>int</info>  Success: the query timeout value of the current request. Units of msec.
       
       Failure: FALSE

<comment>See Also:</comment>
   * <strong>cubrid_set_query_timeout()</strong>


id: cubrid_get_server_info
type: function
doc:
<comment>Description:</comment>
  Return the CUBRID server version
  
  This function returns a string that represents the CUBRID server version.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection.

<comment>Return:</comment>
  <info>string</info>  A string that represents the CUBRID server version; on success.
          
          <info>false</info> on failure.


id: cubrid_insert_id
type: function
doc:
<comment>Description:</comment>
  Return the ID generated for the last updated AUTO_INCREMENT column
  
  The <strong>cubrid_insert_id()</strong> function retrieves the ID generated for the AUTO_INCREMENT column which is
  updated by the previous INSERT query. It returns 0 if the previous query does not generate new
  rows, or FALSE on failure.
  
  CUBRID supports AUTO_INCREMENT for more than one columns in a table. In most cases, there will be
  a single AUTO_INCREMENT column in a table. If there are multiple AUTO_INCREMENT columns, this
  function should not be used even if it will return a value.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The connection identifier previously obtained by a call to
                              <strong>cubrid_connect()</strong>.

<comment>Return:</comment>
  <info>string</info>  A string representing the ID generated for an AUTO_INCREMENT column by the previous query,
          on success.
          
          0, if the previous query does not generate new rows.
          
          <info>false</info> on failure.


id: cubrid_is_instance
type: function
doc:
<comment>Description:</comment>
  Check whether the instance pointed by OID exists
  
  The <strong>cubrid_is_instance()</strong> function is used to check whether the instance pointed by the given <strong>$oid</strong>
  exists or not.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance that you want to check the existence.

<comment>Return:</comment>
  <info>int</info>  1, if such instance exists;
       
       0, if such instance does not exist;
       
       -1, in case of error

<comment>See Also:</comment>
   * <strong>cubrid_drop()</strong>
   * <strong>cubrid_get_class_name()</strong>


id: cubrid_list_dbs
type: function
doc:
<comment>Description:</comment>
  Return an array with the list of all existing CUBRID databases
  
  This function returns an array with the list of all existing Cubrid databases.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection.

<comment>Return:</comment>
  <info>array</info>  An numeric array with all existing Cubrid databases; on success.
         
         <info>false</info> on failure.


id: cubrid_load_from_glo
type: function
doc:
<comment>Description:</comment>
  Read data from a GLO instance and save it in a file
  
  The <strong>cubrid_load_from_glo()</strong> function is used to read a data from a glo instance, and saves it in a
  designated file.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  Oid of the glo instance that you want to read the data from.
  <info>string  </info>  <strong>$file_name      </strong>  Name of the file where you want to save the data in.

<comment>Return:</comment>
  <info>int</info>  <info>true</info>, when process is successful.
       
       <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_new_glo()</strong>
   * <strong>cubrid_save_to_glo()</strong>
   * <strong>cubrid_send_glo()</strong>


id: cubrid_lob2_bind
type: function
doc:
<comment>Description:</comment>
  Bind a lob object or a string as a lob object to a prepared statement as parameters
  
  The <strong>cubrid_lob2_bind()</strong> function is used to bind BLOB/CLOB datas to a corresponding question mark
  placeholder in the SQL statement that was passed  to <strong>cubrid_prepare()</strong>. If <strong>$bind_value_type</strong>  is not
  given, string will be "BLOB" as the default. But if you use <strong>cubrid_lob2_new()</strong> before,
  <strong>$bind_value_type</strong> will be consistent with <strong>$type</strong> in <strong>cubrid_lob2_new()</strong> as the default.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier </strong>  Request identifier as a result of <strong>cubrid_prepare()</strong>.
  <info>int     </info>  <strong>$bind_index     </strong>  Location of binding parameters. It starts with 1.
  <info>mixed   </info>  <strong>$bind_value     </strong>  Actual value for binding.
  <info>string  </info>  <strong>$bind_value_type</strong>  It must be "BLOB" or "CLOB" and it won't be case-sensitive. If it not
                              be given, the default value is "BLOB".

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_new()</strong>
   * <strong>cubrid_lob2_close()</strong>


id: cubrid_lob2_close
type: function
doc:
<comment>Description:</comment>
  Close LOB object
  
  The <strong>cubrid_lob2_close()</strong> function is used to close LOB object returned from <strong>cubrid_lob2_new()</strong> or
  got from the result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, on success.
        
        <info>false</info>, on failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_new()</strong>


id: cubrid_lob2_export
type: function
doc:
<comment>Description:</comment>
  Export the lob object to a file
  
  The <strong>cubrid_lob2_export()</strong> function is used to save the  contents of BLOB/CLOB data to a file. To
  use this function, you must use <strong>cubrid_lob2_new()</strong> or fetch a lob object from CUBRID  database
  first. If the file already exists, the operation will fail.  This function will not influence the
  cursor position of the lob object.  It operates the entire lob object.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.
  <info>        </info>  <strong>$filename      </strong>  File name you want to store BLOB/CLOB data. It also supports the path
                             of the file.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the process is successful and <info>false</info> for failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_new()</strong>
   * <strong>cubrid_lob2_close()</strong>
   * <strong>cubrid_lob2_import()</strong>
   * <strong>cubrid_lob2_bind()</strong>


id: cubrid_lob2_import
type: function
doc:
<comment>Description:</comment>
  Import BLOB/CLOB data from a file
  
  The <strong>cubrid_lob2_import()</strong> function is used to save the contents of BLOB/CLOB data from a file. To
  use this function, you must use <strong>cubrid_lob2_new()</strong> or fetch a lob object from CUBRID database
  first. If the file already exists, the operation will fail.  This function will not influence the
  cursor position of the lob object.  It operates the entire lob object.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.
  <info>        </info>  <strong>$filename      </strong>  File name you want to import BLOB/CLOB data. It also supports the path
                             of the file.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the process is successful and <info>false</info> for failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_new()</strong>
   * <strong>cubrid_lob2_close()</strong>
   * <strong>cubrid_lob2_export()</strong>
   * <strong>cubrid_lob2_bind()</strong>


id: cubrid_lob2_new
type: function
doc:
<comment>Description:</comment>
  Create a lob object
  
  The <strong>cubrid_lob2_new()</strong> function is used to create a lob object (both BLOB and CLOB).  This function
  should be used before you bind a lob object.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier. If the connection identifier is not specified,
                              the last connection opened by <strong>cubrid_connect()</strong> or
                              <strong>cubrid_connect_with_url()</strong> is assumed.
  <info>string  </info>  <strong>$type           </strong>  It may be "BLOB" or "CLOB", it won't be case-sensitive. The default
                              value is "BLOB".

<comment>Return:</comment>
  <info>resource</info>  Lob identifier when it is successful.
            
            <info>false</info>  on failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_close()</strong>


id: cubrid_lob2_read
type: function
doc:
<comment>Description:</comment>
  Read from BLOB/CLOB data
  
  The <strong>cubrid_lob2_read()</strong> function reads <strong>$len</strong> bytes from the  LOB data and returns the bytes read.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.
  <info>int     </info>  <strong>$len           </strong>  Length from buffer you want to read from the lob data.

<comment>Return:</comment>
  <info>string</info>  Returns the contents as a string.
          
          <info>false</info> when there is no more data.
          
          NULL on failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_write()</strong>
   * <strong>cubrid_lob2_seek()</strong>
   * <strong>cubrid_lob2_seek64()</strong>
   * <strong>cubrid_lob2_tell()</strong>
   * <strong>cubrid_lob2_tell64()</strong>
   * <strong>cubrid_lob2_size()</strong>
   * <strong>cubrid_lob2_size64()</strong>


id: cubrid_lob2_seek
type: function
doc:
<comment>Description:</comment>
  Move the cursor of a lob object
  
  The <strong>cubrid_lob2_seek()</strong> function is used to move the cursor position of a lob object by the value
  set in the <strong>$offset</strong> argument, to the direction set in the <strong>$origin</strong> argument.
  
  To set the <strong>$origin</strong> argument, you can use CUBRID_CURSOR_FIRST to set the cursor position moving
  forward <strong>$offset</strong> units from the first beginning. In this case, <strong>$offset</strong> must be a positive value.
  
  If you use CUBRID_CURSOR_CURRENT for <strong>$origin</strong>, you can move  forward or backward. and <strong>$offset</strong> can
  be positive or negative.
  
  If you use CUBRID_CURSOR_LAST for <strong>$origin</strong>, you can move  backward <strong>$offset</strong> units from the end of
  LOB object and <strong>$offset</strong> only can be positive.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.
  <info>int     </info>  <strong>$offset        </strong>  Number of units you want to move the cursor.
  <info>int     </info>  <strong>$origin        </strong>  This parameter can be the following values:
                             
                             CUBRID_CURSOR_FIRST: move forward from the first beginning.
                             
                             CUBRID_CURSOR_CURRENT: move forward or backward from the current
                             position.
                             
                             CUBRID_CURSOR_LAST: move backward at the end of LOB object.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the process is successful and <info>false</info> for failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_read()</strong>
   * <strong>cubrid_lob2_write()</strong>
   * <strong>cubrid_lob2_seek64()</strong>
   * <strong>cubrid_lob2_tell()</strong>
   * <strong>cubrid_lob2_tell64()</strong>
   * <strong>cubrid_lob2_size()</strong>
   * <strong>cubrid_lob2_size64()</strong>


id: cubrid_lob2_seek64
type: function
doc:
<comment>Description:</comment>
  Move the cursor of a lob object
  
  The <strong>cubrid_lob2_seek64()</strong> function is used to move the cursor position of a lob object by the value
  set in the <strong>$offset</strong>  argument, to the direction set in the <strong>$origin</strong> argument.  If the <strong>$offset</strong> you
  want to move is larger than an integer  data can be stored, you can use this function.
  
  To set the <strong>$origin</strong> argument, you can use CUBRID_CURSOR_FIRST to set the cursor position moving
  forward <strong>$offset</strong> units from the first beginning. In this case, <strong>$offset</strong> must be a positive value.
  
  If you use CUBRID_CURSOR_CURRENT for <strong>$origin</strong>, you can move forward or backward. and <strong>$offset</strong> can be
  positive or negative.
  
  If you use CUBRID_CURSOR_LAST for <strong>$origin</strong>, you can move backward <strong>$offset</strong> units from the end of LOB
  object and <strong>$offset</strong> only can be positive.
  
  If you use this function to move the cursor position of the lob object, you should pass <strong>$offset</strong> as
  a string.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.
  <info>string  </info>  <strong>$offset        </strong>  Number of units you want to move the cursor.
  <info>int     </info>  <strong>$origin        </strong>  This parameter can be the following values:
                             
                             CUBRID_CURSOR_FIRST: move forward from the first beginning.
                             
                             CUBRID_CURSOR_CURRENT: move forward or backward from the current
                             position.
                             
                             CUBRID_CURSOR_LAST: move backward at the end of LOB object.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the process is successful and <info>false</info> for failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_read()</strong>
   * <strong>cubrid_lob2_write()</strong>
   * <strong>cubrid_lob2_seek()</strong>
   * <strong>cubrid_lob2_tell()</strong>
   * <strong>cubrid_lob2_tell64()</strong>
   * <strong>cubrid_lob2_size()</strong>
   * <strong>cubrid_lob2_size64()</strong>


id: cubrid_lob2_size
type: function
doc:
<comment>Description:</comment>
  Get a lob object's size
  
  The <strong>cubrid_lob2_size()</strong> function is used to get the size of a lob object.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.

<comment>Return:</comment>
  <info>int</info>  It will return the size of the LOB object when it processes successfully.
       
       <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_read()</strong>
   * <strong>cubrid_lob2_write()</strong>
   * <strong>cubrid_lob2_seek()</strong>
   * <strong>cubrid_lob2_seek64()</strong>
   * <strong>cubrid_lob2_tell()</strong>
   * <strong>cubrid_lob2_tell64()</strong>
   * <strong>cubrid_lob2_size64()</strong>


id: cubrid_lob2_size64
type: function
doc:
<comment>Description:</comment>
  Get a lob object's size
  
  The <strong>cubrid_lob2_size64()</strong> function is used to get the size of a lob object.  If the size of a lob
  object is larger than an integer data can be stored, you can use this function and it will return
  the size as a string.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.

<comment>Return:</comment>
  <info>string</info>  It will return the size of the LOB object as a string when it processes successfully.
          
          <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_read()</strong>
   * <strong>cubrid_lob2_write()</strong>
   * <strong>cubrid_lob2_seek()</strong>
   * <strong>cubrid_lob2_seek64()</strong>
   * <strong>cubrid_lob2_tell()</strong>
   * <strong>cubrid_lob2_tell64()</strong>
   * <strong>cubrid_lob2_size()</strong>


id: cubrid_lob2_tell
type: function
doc:
<comment>Description:</comment>
  Tell the cursor position of the LOB object
  
  The <strong>cubrid_lob2_tell()</strong> function is used to tell the cursor position of the LOB object.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.

<comment>Return:</comment>
  <info>int</info>  It will return the cursor position on the LOB object when it processes successfully.
       
       <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_read()</strong>
   * <strong>cubrid_lob2_write()</strong>
   * <strong>cubrid_lob2_seek()</strong>
   * <strong>cubrid_lob2_seek64()</strong>
   * <strong>cubrid_lob2_tell64()</strong>
   * <strong>cubrid_lob2_size()</strong>
   * <strong>cubrid_lob2_size64()</strong>


id: cubrid_lob2_tell64
type: function
doc:
<comment>Description:</comment>
  Tell the cursor position of the LOB object
  
  The <strong>cubrid_lob2_tell64()</strong> function is used to tell the  cursor position of the LOB object. If the
  size of a lob object is larger than an integer data can be stored, you can use this function and
  it will return the position information as a string.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.

<comment>Return:</comment>
  <info>string</info>  It will return the cursor position on the LOB object as a string when it processes
          successfully.
          
          <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_read()</strong>
   * <strong>cubrid_lob2_write()</strong>
   * <strong>cubrid_lob2_seek()</strong>
   * <strong>cubrid_lob2_seek64()</strong>
   * <strong>cubrid_lob2_tell()</strong>
   * <strong>cubrid_lob2_size()</strong>
   * <strong>cubrid_lob2_size64()</strong>


id: cubrid_lob2_write
type: function
doc:
<comment>Description:</comment>
  Write to a lob object
  
  The <strong>cubrid_lob2_write()</strong> function reads as much as data from <strong>$buf</strong> and stores it to the LOB object.
  Note that this function can only append characters now.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  Lob identifier as a result of <strong>cubrid_lob2_new()</strong> or get from the result
                             set.
  <info>string  </info>  <strong>$buf           </strong>  Data that need to be written to the lob object.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the process is successful and <info>false</info> for failure.

<comment>See Also:</comment>
   * <strong>cubrid_lob2_read()</strong>
   * <strong>cubrid_lob2_seek()</strong>
   * <strong>cubrid_lob2_seek64()</strong>
   * <strong>cubrid_lob2_tell()</strong>
   * <strong>cubrid_lob2_tell64()</strong>
   * <strong>cubrid_lob2_size()</strong>
   * <strong>cubrid_lob2_size64()</strong>


id: cubrid_lob_close
type: function
doc:
<comment>Description:</comment>
  Close BLOB/CLOB data
  
  <strong>cubrid_lob_close()</strong> is used to close all BLOB/CLOB returned from <strong>cubrid_lob_get()</strong>.

<comment>Param:</comment>
  <info>array</info>  <strong>$lob_identifier_array</strong>  LOB identifier array return from cubrid_lob_get.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lob_get()</strong>
   * <strong>cubrid_lob_size()</strong>
   * <strong>cubrid_lob_export()</strong>
   * <strong>cubrid_lob_send()</strong>


id: cubrid_lob_export
type: function
doc:
<comment>Description:</comment>
  Export BLOB/CLOB data to file
  
  <strong>cubrid_lob_export()</strong> is used to get BLOB/CLOB data from CUBRID database, and saves its contents to
  a file. To use this function, you must use <strong>cubrid_lob_get()</strong> first to get BLOB/CLOB info from
  CUBRID.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>resource</info>  <strong>$lob_identifier </strong>  LOB identifier.
  <info>string  </info>  <strong>$path_name      </strong>  Path name of the file.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lob_get()</strong>
   * <strong>cubrid_lob_close()</strong>
   * <strong>cubrid_lob_size()</strong>
   * <strong>cubrid_lob_send()</strong>


id: cubrid_lob_get
type: function
doc:
<comment>Description:</comment>
  Get BLOB/CLOB data
  
  <strong>cubrid_lob_get()</strong> is used to get BLOB/CLOB meta info from CUBRID database,  CUBRID gets BLOB/CLOB
  by executing the SQL statement, and returns all LOBs as a resource array.  Be sure that the SQL
  retrieves only one column and its data type is BLOB or CLOB.
  
  Remember to use <strong>cubrid_lob_close()</strong> to release the LOBs if you don't need it any more.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$sql            </strong>  SQL statement to be executed.

<comment>Return:</comment>
  <info>array</info>  Return an array of LOB resources, when process is successful.
         
         <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lob_close()</strong>
   * <strong>cubrid_lob_size()</strong>
   * <strong>cubrid_lob_export()</strong>
   * <strong>cubrid_lob_send()</strong>


id: cubrid_lob_send
type: function
doc:
<comment>Description:</comment>
  Read BLOB/CLOB data and send straight to browser
  
  <strong>cubrid_lob_send()</strong> reads BLOB/CLOB data and passes it straight through to the browser.   To use
  this function, you must use <strong>cubrid_lob_get()</strong> first to get BLOB/CLOB info from CUBRID.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>resource</info>  <strong>$lob_identifier </strong>  LOB identifier.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lob_get()</strong>
   * <strong>cubrid_lob_close()</strong>
   * <strong>cubrid_lob_size()</strong>
   * <strong>cubrid_lob_export()</strong>


id: cubrid_lob_size
type: function
doc:
<comment>Description:</comment>
  Get BLOB/CLOB data size
  
  <strong>cubrid_lob_size()</strong> is used to get BLOB/CLOB data size.

<comment>Param:</comment>
  <info>resource</info>  <strong>$lob_identifier</strong>  LOB identifier.

<comment>Return:</comment>
  <info>string</info>  A string representing LOB data size, when process is successful.
          
          <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lob_get()</strong>
   * <strong>cubrid_lob_close()</strong>
   * <strong>cubrid_lob_export()</strong>
   * <strong>cubrid_lob_send()</strong>


id: cubrid_lock_read
type: function
doc:
<comment>Description:</comment>
  Set a read lock on the given OID
  
  The <strong>cubrid_lock_read()</strong> function is used to put read lock on the instance pointed by given <strong>$oid</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance that you want to put read lock on.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lock_write()</strong>


id: cubrid_lock_write
type: function
doc:
<comment>Description:</comment>
  Set a write lock on the given OID
  
  The <strong>cubrid_lock_write()</strong> function is used to put write lock on the instance pointed by the given
  <strong>$oid</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance that you want to put write lock on.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_lock_read()</strong>


id: cubrid_move_cursor
type: function
doc:
<comment>Description:</comment>
  Move the cursor in the result
  
  The <strong>cubrid_move_cursor()</strong> function is used to move the current cursor location of <strong>$req_identifier</strong>
  by the value set in the <strong>$offset</strong> argument, to the direction set in the <strong>$origin</strong> argument. To set the
  <strong>$origin</strong> argument, you can use CUBRID_CURSOR_FIRST for the first part of the result,
  CUBRID_CURSOR_CURRENT for the current location of the result, or CUBRID_CURSOR_LAST for the last
  part of the result.  If <strong>$origin</strong> argument is not explicitly designated, then the function uses
  CUBRID_CURSOR_CURRENT as its default value.
  
  If the value of cursor movement range goes over the valid limit, then the cursor moves to the next
  location after the valid range for the cursor. For example, if you move 20 units in the result
  with the size of 10, then the cursor will move to 11th place and return CUBRID_NO_MORE_DATA.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.
  <info>int     </info>  <strong>$offset        </strong>  Number of units you want to move the cursor.
  <info>int     </info>  <strong>$origin        </strong>  Location where you want to move the cursor from CUBRID_CURSOR_FIRST,
                             CUBRID_CURSOR_CURRENT, CUBRID_CURSOR_LAST.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsucceful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>


id: cubrid_new_glo
type: function
doc:
<comment>Description:</comment>
  Create a glo instance
  
  The <strong>cubrid_new_glo()</strong> function is used to create a glo instance in the requested class (glo class).
  The glo created is a LO type, and is stored in the <strong>$file_name</strong> file.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$class_name     </strong>  Name of the class that you want to create a glo in.
  <info>string  </info>  <strong>$file_name      </strong>  The file name that you want to save in the newly created glo.

<comment>Return:</comment>
  <info>string</info>  Oid of the instance created, when process is successful.
          
          <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_save_to_glo()</strong>
   * <strong>cubrid_load_from_glo()</strong>
   * <strong>cubrid_send_glo()</strong>


id: cubrid_next_result
type: function
doc:
<comment>Description:</comment>
  Get result of next query when executing multiple SQL statements
  
  The <strong>cubrid_next_result()</strong> function is used to get results of next query if multiple SQL statements
  are executed and CUBRID_EXEC_QUERY_ALL flag is set upon <strong>cubrid_execute()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>


id: cubrid_num_cols
type: function
doc:
<comment>Description:</comment>
  Return the number of columns in the result set
  
  The <strong>cubrid_num_cols()</strong> function is used to get the number of columns from the query result. It can
  only be used when the query executed is a select statement.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  Result.

<comment>Return:</comment>
  <info>int</info>  Number of columns, when process is successful.
       
       <info>false</info>, if SQL statement is not SELECT.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_num_rows()</strong>


id: cubrid_num_fields
type: function
doc:
<comment>Description:</comment>
  Return the number of columns in the result set
  
  This function returns the number of columns in the result set, on success, or it returns FALSE on
  failure.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>, <strong>cubrid_query()</strong> and
                     <strong>cubrid_prepare()</strong>

<comment>Return:</comment>
  <info>int</info>  Number of columns, on success.
       
       -1 if SQL sentence is not SELECT.
       
       <info>false</info> when process is unsuccessful.


id: cubrid_num_rows
type: function
doc:
<comment>Description:</comment>
  Get the number of rows in the result set
  
  The <strong>cubrid_num_rows()</strong> function is used to get the number of rows from the query result.  You can
  use it only when the query executed is a select statement.  When you want to know such value for
  INSERT, UPDATE, or DELETE query, you have to use the <strong>cubrid_affected_rows()</strong> function.
  
  Note: The <strong>cubrid_num_rows()</strong> function can only be used for synchronous query; it returns 0 when it
  is used for asynchronous query.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>, <strong>cubrid_query()</strong> and
                     <strong>cubrid_prepare()</strong>

<comment>Return:</comment>
  <info>int</info>  Number of rows, when process is successful.
       
       0 when the query was done in async mode.
       
       -1, if SQL statement is not SELECT.
       
       <info>false</info> when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_num_cols()</strong>
   * <strong>cubrid_affected_rows()</strong>


id: cubrid_pconnect
type: function
doc:
<comment>Description:</comment>
  Open a persistent connection to a CUBRID server
  
  Establishes a persistent connection to a CUBRID server.
  
  <strong>cubrid_pconnect()</strong> acts very much like <strong>cubrid_connect()</strong> with two major differences.
  
  First, when connecting, the function would first try to find a (persistent) link that's already
  open with the same host, port, dbname and userid. If one is found, an identifier for it will be
  returned instead of opening a new connection.
  
  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 (<strong>cubrid_close()</strong> or <strong>cubrid_disconnect()</strong> will not
  close links established by <strong>cubrid_pconnect()</strong>).
  
  This type of link is therefore called 'persistent'.

<comment>Param:</comment>
  <info>string</info>  <strong>$host  </strong>  Host name or IP address of CUBRID CAS server.
  <info>int   </info>  <strong>$port  </strong>  Port number of CUBRID CAS server (BROKER_PORT configured in
                   $CUBRID/conf/cubrid_broker.conf).
  <info>string</info>  <strong>$dbname</strong>  Name of database.
  <info>string</info>  <strong>$userid</strong>  User name for the database.
  <info>string</info>  <strong>$passwd</strong>  User password.

<comment>Return:</comment>
  <info>resource</info>  Connection identifier, when process is successful.
            
            <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_connect()</strong>
   * <strong>cubrid_connect_with_url()</strong>
   * <strong>cubrid_pconnect_with_url()</strong>
   * <strong>cubrid_disconnect()</strong>
   * <strong>cubrid_close()</strong>


id: cubrid_pconnect_with_url
type: function
doc:
<comment>Description:</comment>
  Open a persistent connection to CUBRID server
  
  Establishes a persistent connection to a CUBRID server.
  
  <strong>cubrid_pconnect_with_url()</strong> acts very much like <strong>cubrid_connect_with_url()</strong> with two major
  differences.
  
  First, when connecting, the function would first try to find a (persistent) link that's already
  open with the same host, port, dbname and userid. If one is found, an identifier for it will be
  returned instead of opening a new connection.
  
  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 (<strong>cubrid_close()</strong> or <strong>cubrid_disconnect()</strong> will not
  close links established by <strong>cubrid_pconnect_with_url()</strong>).
  
  This type of link is therefore called 'persistent'.
  
  \<url&gt; ::= CUBRID:\<host&gt;:\<db_name&gt;:\<db_user&gt;:\<db_password&gt;:[?\<properties&gt;]
  
  \<properties&gt; ::= \<property&gt; [&\<property&gt;]
  
  \<properties&gt; ::= alhosts=\<alternative_hosts&gt;[ &rctime=\<time&gt;]
  
  \<properties&gt; ::= login_timeout=\<milli_sec&gt;
  
  \<properties&gt; ::= query_timeout=\<milli_sec&gt;
  
  \<properties&gt; ::= disconnect_on_query_timeout=true|false
  
  \<alternative_hosts&gt; ::= \<standby_broker1_host&gt;:\<port&gt; [,\<standby_broker2_host&gt;:\<port&gt;]
  
  \<host&gt; := HOSTNAME | IP_ADDR
  
  \<time&gt; := SECOND
  
  \<milli_sec&gt; := MILLI SECOND
  
  host : A host name or IP address of the master databasedb_name : A name of the databasedb_user : A
  name of the database userdb_password : A database user password alhosts : Specifies the broker
  information of the standby server, which is used for failover when it is impossible to connect to
  the active server.  You can specify multiple brokers for failover, and the connection to the
  brokers is attempted in the order listed in alhosts rctime : An interval between the attempts to
  connect to the active broker in which failure occurred. After a failure occurs, the system
  connects to the  broker specified by althosts (failover), terminates the transaction, and then
  attempts to connect to the active broker of the master database at every rctime.  The default
  value is 600 seconds. login_timeout : Timeout value (unit: msec.) for database login. The default
  value is 0, which means infinite postponement.  query_timeout : Timeout value (unit: msec.) for
  query request. Upon timeout, a message to cancel requesting a query transferred to server is sent.
  The return  value can depend on the disconnect_on_query_timeout configuration; even though the
  message to cancel a request is sent to server, that request may succeed.
  disconnect_on_query_timeout : Configures a value whether to immediately return an error of
  function being executed upon timeout. The default value is false.
  
  <return>?</return> and <return>:</return> that are used as identifiers in PHP connection URL can't be included in the password. The
  following is an example of a password that is invalid to use as connection URL because it contains
  "<return>?:</return>".
  
  $url = "CUBRID:localhost:33000:tdb:dba:12?:?login_timeout=100";
  
  Passwords that contain <return>?</return> or <return>:</return> may be passed as a separate parameter.
  
  $url = "CUBRID:localhost:33000:tbd:::?login_timeout=100";
  
  $conn = cubrid_pconnect_with_url ($url, "dba", "12?");
  
  If user or password is empty,you can't delete "<return>:</return>",the following is an example.
  
  $url = "CUBRID:localhost:33000:demodb:::";

<comment>Param:</comment>
  <info>string</info>  <strong>$conn_url</strong>  A character string that contains server connection information.
  <info>string</info>  <strong>$userid  </strong>  User name for the database.
  <info>string</info>  <strong>$passwd  </strong>  User password.

<comment>Return:</comment>
  <info>resource</info>  Connection identifier, when process is successful.
            
            <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_connect()</strong>
   * <strong>cubrid_connect_with_url()</strong>
   * <strong>cubrid_pconnect()</strong>
   * <strong>cubrid_disconnect()</strong>
   * <strong>cubrid_close()</strong>


id: cubrid_ping
type: function
doc:
<comment>Description:</comment>
  Ping a server connection or reconnect if there is no connection
  
  Checks whether or not the connection to the server is working.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection identifier. If the connection identifier is not
                              specified, the last connection opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the connection to the server CUBRID server is working, otherwise <info>false</info>.


id: cubrid_prepare
type: function
doc:
<comment>Description:</comment>
  Prepare a SQL statement for execution
  
  The <strong>cubrid_prepare()</strong> function is a sort of API which represents SQL statements  compiled
  previously to a given connection handle. This pre-compiled SQL statement will be included  in the
  <strong>cubrid_prepare()</strong>.
  
  Accordingly, you can use this statement effectively to execute several times repeatedly or to
  process long data. Only a single statement can be used and a parameter may put a question mark (?)
  to appropriate area in the SQL statement. Add a parameter when you bind a value in the VALUES
  clause of INSERT statement or in the WHERE clause. Note that it is allowed to bind a value to a
  MARK(?) by using the <strong>cubrid_bind()</strong> function only.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$prepare_stmt   </strong>  Prepare query.
  <info>int     </info>  <strong>$option         </strong>  OID return option CUBRID_INCLUDE_OID.

<comment>Return:</comment>
  <info>resource</info>  Request identifier, if process is successful;
            
            <info>false</info>, if process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_execute()</strong>
   * <strong>cubrid_bind()</strong>


id: cubrid_put
type: function
doc:
<comment>Description:</comment>
  Update a column using OID
  
  The <strong>cubrid_put()</strong> function is used to update an attribute of the instance of the given <strong>$oid</strong>.
  
  You can update single attribute by using string data type to set <strong>$attr</strong>.  In such case, you can use
  integer, floating point or string type data for the <strong>$value</strong> argument. To update multiple number of
  attributes, you can disregard the <strong>$attr</strong> argument, and set <strong>$value</strong> argument with associative array
  data type.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance that you want to update.
  <info>string  </info>  <strong>$attr           </strong>  Name of the attribute that you want to update.
  <info>mixed   </info>  <strong>$value          </strong>  New value that you want to assign to the attribute.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_get()</strong>
   * <strong>cubrid_set_add()</strong>
   * <strong>cubrid_set_drop()</strong>
   * <strong>cubrid_seq_insert()</strong>
   * <strong>cubrid_seq_drop()</strong>
   * <strong>cubrid_seq_put()</strong>


id: cubrid_query
type: function
doc:
<comment>Description:</comment>
  Send a CUBRID query
  
  <strong>cubrid_query()</strong> sends a unique query (multiple queries are not supported) to the  currently active
  database on the server that's associated with the specified <strong>$conn_identifier</strong>.

<comment>Param:</comment>
  <info>string  </info>  <strong>$query          </strong>  An SQL query
                              
                              Data inside the query should be properly escaped.
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection. If the connection identifier is not specified,
                              the last connection opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>resource</info>  For SELECT, SHOW, DESCRIBE, EXPLAIN and other statements returning resultset,
            <strong>cubrid_query()</strong> returns a <info>resource</info> on success, or <info>false</info> on error.
            
            For other type of SQL statements, INSERT, UPDATE, DELETE, DROP, etc, <strong>cubrid_query()</strong>
            returns <info>true</info> on success or <info>false</info> on error.
            
            The returned result resource should be passed to <strong>cubrid_fetch_array()</strong>, and other
            functions for dealing with result tables, to access the returned data.
            
            Use <strong>cubrid_num_rows()</strong> to find out how many rows were returned for a SELECT statement or
            <strong>cubrid_affected_rows()</strong> to find out how many rows were affected by a DELETE, INSERT,
            REPLACE, or UPDATE statement.
            
            <strong>cubrid_query()</strong> will also fail and return <info>false</info> if the user does not have permission to
            access the table(s) referenced by the query.

<comment>See Also:</comment>
   * <strong>cubrid_connect()</strong>
   * <strong>cubrid_error()</strong>
   * <strong>cubrid_real_escape_string()</strong>
   * <strong>cubrid_result()</strong>
   * <strong>cubrid_fetch_assoc()</strong>
   * <strong>cubrid_unbuffered_query()</strong>


id: cubrid_real_escape_string
type: function
doc:
<comment>Description:</comment>
  Escape special characters in a string for use in an SQL statement
  
  This function returns the escaped string version of the given string. It will escape the following
  characters: <info>'</info>.
   In general, single quotations are used to enclose character string. Double quotations may be used
  as well depending on the value of ansi_quotes, which is a parameter related to SQL statement. If
  the ansi_quotes value is set to no, character string enclosed by double quotations is handled as
  character string, not as an identifier. The default value is yes.
   If you want to include a single quote as part of a character string, enter two single quotes in a
  row.

<comment>Param:</comment>
  <info>string  </info>  <strong>$unescaped_string</strong>  The string that is to be escaped.
  <info>resource</info>  <strong>$conn_identifier </strong>  The CUBRID connection. If the connection identifier is not specified,
                               the last connection opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>string</info>  Escaped string version of the given string, on success.
          
          <info>false</info> on failure.


id: cubrid_result
type: function
doc:
<comment>Description:</comment>
  Return the value of a specific field in a specific row
  
  This function returns the value of a specific field in a specific row from a result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$result</strong>  <strong>$result</strong> comes from a call to <strong>cubrid_execute()</strong>
  <info>int     </info>  <strong>$row   </strong>  The row number from the result that is being retrieved. Row numbers start at 0.
  <info>mixed   </info>  <strong>$field </strong>  The name or offset of the <strong>$field</strong> being retrieved. It can be the field's offset,
                     the field's name, or the field's table dot field name (tablename.fieldname). If
                     the column name has been aliased ('select foo as bar from...'), use the alias
                     instead of the column name. If undefined, the first field is retrieved.

<comment>Return:</comment>
  <info>string</info>  Value of a specific field, on success (NULL if value if null).
          
          <info>false</info> on failure.


id: cubrid_rollback
type: function
doc:
<comment>Description:</comment>
  Roll back a transaction
  
  The <strong>cubrid_rollback()</strong> function executes rollback on the transaction pointed by <strong>$conn_identifier</strong>,
  currently in progress.
  
  Connection to server is closed after calling <strong>cubrid_rollback()</strong>. Connection handle, however, is
  still valid.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_commit()</strong>
   * <strong>cubrid_disconnect()</strong>


id: cubrid_save_to_glo
type: function
doc:
<comment>Description:</comment>
  Save requested file in a GLO instance
  
  The <strong>cubrid_save_to_glo()</strong> function is used to save requested file in a glo instance.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  Oid of the glo instance that you want to save a file in.
  <info>string  </info>  <strong>$file_name      </strong>  The name of the file that you want to save.

<comment>Return:</comment>
  <info>int</info>  <info>true</info>, when process is successful.
       
       <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_new_glo()</strong>
   * <strong>cubrid_load_from_glo()</strong>
   * <strong>cubrid_send_glo()</strong>


id: cubrid_schema
type: function
doc:
<comment>Description:</comment>
  Get the requested schema information
  
  The <strong>cubrid_schema()</strong> function is used to get the requested schema information from database. You
  have to designate <strong>$class_name</strong>, if you want to get information on certain class, <strong>$attr_name</strong>, if you
  want to get information on certain attribute (can be used only with CUBRID_ SCH_ATTR_PRIVILEGE).
  
  The result of the cubrid_schema function is returned as a two-dimensional array (column
  (associative array) * row (numeric array)). The following tables shows types of schema and the
  column structure of the result array to be returned based on the schema type.
  
  Result Composition of Each TypeSchemaColumn NumberColumn
  NameValueCUBRID_SCH_CLASS1NAME2TYPE0:system class 1:vclass
  2:classCUBRID_SCH_VCLASS1NAME2TYPE1:vclassCUBRID_SCH_QUERY_SPEC1QUERY_SPECCUBRID_SCH_ATTRIBUTE /
  CUBRID_SCH_CLASS_ATTRIBUTE1ATTR_NAME2DOMAIN3SCALE4PRECISION5INDEXED1:indexed6NOT NULL1:not
  null7SHARED1:shared8UNIQUE1:unique9DEFAULT10ATTR_ORDERbase:111CLASS_NAME12SOURCE_CLASS13IS_KEY1:keyCUBRID_SCH_METHOD
  /
  CUBRID_SCH_CLASS_METHOD1NAME2RET_DOMAIN3ARG_DOMAINCUBRID_SCH_METHOD_FILE1METHOD_FILECUBRID_SCH_SUPERCLASS
  / CUBRID_SCH_DIRECT_SUPER_CLASS / CUBRID_SCH_SUBCLASS1CLASS_NAME2TYPE0:system class 1:vclass
  2:classCUBRID_SCH_CONSTRAINT1TYPE0:unique 1:index 2:reverse unique 3:reverse
  index2NAME3ATTR_NAME4NUM_PAGES5NUM_KEYS6PRIMARY_KEY1:primary
  key7KEY_ORDERbase:1CUBRID_SCH_TRIGGER1NAME2STATUS3EVENT4TARGET_CLASS5TARGET_ATTR6ACTION_TIME7ACTION8PRIORITY9CONDITION_TIME10CONDITIONCUBRID_SCH_CLASS_PRIVILEGE
  / CUBRID_SCH_ATTR_PRIVILEGE1CLASS_NAME /
  ATTR_NAME2PRIVILEGE3GRANTABLECUBRID_SCH_PRIMARY_KEY1CLASS_NAME2ATTR_NAME3KEY_SEQbase:14KEY_NAMECUBRID_SCH_IMPORTED_KEYS
  / CUBRID_SCH_EXPORTED_KEYS /
  CUBRID_SCH_CROSS_REFERENCE1PKTABLE_NAME2PKCOLUMN_NAME3FKTABLE_NAMEbase:14FKCOLUMN_NAME5KEY_SEQbase:16UPDATE_ACTION0:cascade
  1:restrict 2:no action 3:set null7DELETE_ACTION0:cascade 1:restrict 2:no action 3:set
  null8FK_NAME9PK_NAME

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>int     </info>  <strong>$schema_type    </strong>  Schema data that you want to know.
  <info>string  </info>  <strong>$class_name     </strong>  Class you want to know the schema of.
  <info>string  </info>  <strong>$attr_name      </strong>  Attribute you want to know the schema of.

<comment>Return:</comment>
  <info>array</info>  Array containing the schema information, when process is successful;
         
         <info>false</info>, when process is unsuccessful


id: cubrid_send_glo
type: function
doc:
<comment>Description:</comment>
  Read data from glo and send it to std output
  
  The <strong>cubrid_send_glo()</strong> function is used to read data from glo instance and sends it to the PHP
  standard output.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  Oid of the glo instance that you want to read data from.

<comment>Return:</comment>
  <info>int</info>  <info>true</info>, when process is successful.
       
       <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_new_glo()</strong>
   * <strong>cubrid_save_to_glo()</strong>
   * <strong>cubrid_load_from_glo()</strong>


id: cubrid_seq_drop
type: function
doc:
<comment>Description:</comment>
  Delete an element from sequence type column using OID
  
  The <strong>cubrid_seq_drop()</strong> function is used to delete an element you request from the given sequence
  type attribute in the database.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance you want to work with.
  <info>string  </info>  <strong>$attr_name      </strong>  Name of the attribute that you want to delete an element from.
  <info>int     </info>  <strong>$index          </strong>  Index of the element that you want to delete (1-based).

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_seq_insert()</strong>
   * <strong>cubrid_seq_put()</strong>


id: cubrid_seq_insert
type: function
doc:
<comment>Description:</comment>
  Insert an element to a sequence type column using OID
  
  The <strong>cubrid_col_insert()</strong> function is used to insert an element to a sequence type attribute in a
  requested location.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance you want to work with.
  <info>string  </info>  <strong>$attr_name      </strong>  Name of the attribute you want to insert an instance to.
  <info>int     </info>  <strong>$index          </strong>  Location of the element, you want to insert the element to (1-based).
  <info>string  </info>  <strong>$seq_element    </strong>  Content of the element that you want to insert.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_seq_drop()</strong>
   * <strong>cubrid_seq_put()</strong>


id: cubrid_seq_put
type: function
doc:
<comment>Description:</comment>
  Update the element value of sequence type column using OID
  
  The <strong>cubrid_seq_put()</strong> function is used to update the content of the requested element in a sequent
  type attribute using OID.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance you want to work with.
  <info>string  </info>  <strong>$attr_name      </strong>  Name of the attribute that you want to update an element.
  <info>int     </info>  <strong>$index          </strong>  Index (1-based) of the element that you want to update.
  <info>string  </info>  <strong>$seq_element    </strong>  New content that you want to use for the update.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_seq_drop()</strong>
   * <strong>cubrid_seq_insert()</strong>


id: cubrid_set_add
type: function
doc:
<comment>Description:</comment>
  Insert a single element to set type column using OID
  
  The <strong>cubrid_set_add()</strong> function is used to insert a single element to a set type attribute (set,
  multiset, sequence) you requested.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance you want to work with.
  <info>string  </info>  <strong>$attr_name      </strong>  Name of the attribute you want to insert an element.
  <info>string  </info>  <strong>$set_element    </strong>  Content of the element you want to insert.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_seq_drop()</strong>


id: cubrid_set_autocommit
type: function
doc:
<comment>Description:</comment>
  Set autocommit mode of the connection
  
  The <strong>cubrid_set_autocommit()</strong> function is used to set the CUBRID database auto-commit mode of the
  current database connection.
  
  In CUBRID PHP, auto-commit mode is disabled by default for transaction management. When
  auto-commit mode is truned from off to on, any pending work is automatically committed.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>bool    </info>  <strong>$mode           </strong>  Auto-commit mode. The following constants can be used:
                              
                              <info>CUBRID_AUTOCOMMIT_FALSE</info><info>CUBRID_AUTOCOMMIT_TRUE</info>

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_get_autocommit()</strong>
   * <strong>cubrid_commit()</strong>


id: cubrid_set_db_parameter
type: function
doc:
<comment>Description:</comment>
  Sets the CUBRID database parameters
  
  The <strong>cubrid_set_db_parameter()</strong> function is used to set the CUBRID database parameters. It can set
  the following CUBRID database parameters:
  
  <info>PARAM_ISOLATION_LEVEL</info><info>PARAM_LOCK_TIMEOUT</info>
  
  The auto-commit mode can be set by using <strong>cubrid_set_autocommit()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection. If the connection identifier is not specified,
                              the last link opened by <strong>cubrid_connect()</strong> is assumed.
  <info>int     </info>  <strong>$param_type     </strong>  Database parameter type.
  <info>int     </info>  <strong>$param_value    </strong>  Isolation level value (1-6) or lock timeout (in seconds) value.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> on success.
        
        <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>cubrid_get_db_parameter()</strong>
   * <strong>cubrid_set_autocommit()</strong>


id: cubrid_set_drop
type: function
doc:
<comment>Description:</comment>
  Delete an element from set type column using OID
  
  The <strong>cubrid_set_drop()</strong> function is used to delete an element that you request from the given set
  type (set, multiset) attribute of the database.

<comment>Param:</comment>
  <info>resource</info>  <strong>$conn_identifier</strong>  Connection identifier.
  <info>string  </info>  <strong>$oid            </strong>  OID of the instance you want to work with.
  <info>string  </info>  <strong>$attr_name      </strong>  Name of the attribute you want to delete an element from.
  <info>string  </info>  <strong>$set_element    </strong>  Content of the element you want to delete.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_set_add()</strong>


id: cubrid_set_query_timeout
type: function
doc:
<comment>Description:</comment>
  Set the timeout time of query execution
  
  The <strong>cubrid_set_query_timeout()</strong> function is used to set the timeout time of query execution.

<comment>Param:</comment>
  <info>resource</info>  <strong>$req_identifier</strong>  Request identifier.
  <info>int     </info>  <strong>$timeout       </strong>  Timeout time, unit of msec.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>, when process is successful.
        
        <info>false</info>, when process is unsuccessful.

<comment>See Also:</comment>
   * <strong>cubrid_get_query_timeout()</strong>


id: cubrid_unbuffered_query
type: function
doc:
<comment>Description:</comment>
  Perform a query without fetching the results into memory
  
  This function performs a query without waiting for that all query results have been complete. It
  will return  when the results are being generated.

<comment>Param:</comment>
  <info>string  </info>  <strong>$query          </strong>  A SQL query.
  <info>resource</info>  <strong>$conn_identifier</strong>  The CUBRID connection. If the connection identifier is not specified,
                              the last connection opened by <strong>cubrid_connect()</strong> is assumed.

<comment>Return:</comment>
  <info>resource</info>  For SELECT, SHOW, DESCRIBE or EXPLAIN statements returns a request identifier resource
            on success.
            
            For other type of SQL statements, UPDATE, DELETE, DROP, etc, returns <info>true</info> on success.
            
            <info>false</info> on failure.


id: cubrid_version
type: function
doc:
<comment>Description:</comment>
  Get the CUBRID PHP module's version
  
  The <strong>cubrid_version()</strong> function is used to get the CUBRID PHP module's version.

<comment>Return:</comment>
  <info>string</info>  Version information (eg. "8.3.1.0001").

<comment>See Also:</comment>
   * <strong>cubrid_error_code()</strong>
   * <strong>cubrid_error_code_facility()</strong>


id: curl_close
type: function
doc:
<comment>Description:</comment>
  Close a cURL session
  
  Closes a cURL session and frees all resources.  The cURL handle, <strong>$handle</strong>, is also deleted.

<comment>Param:</comment>
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>void</info>  Nu este întoarsă nici o valoare.

<comment>See Also:</comment>
   * <strong>curl_init()</strong>
   * <strong>curl_multi_close()</strong>


id: curl_copy_handle
type: function
doc:
<comment>Description:</comment>
  Copy a cURL handle along with all of its preferences
  
  Copies a cURL handle keeping the same preferences.

<comment>Param:</comment>
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>CurlHandlefalse</info>  Returns a new cURL handle,  sau <info>false</info> în cazul eșecului.


id: curl_errno
type: function
doc:
<comment>Description:</comment>
  Return the last error number
  
  Returns the error number for the last cURL operation.

<comment>Param:</comment>
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>int</info>  Returns the error number or <return>0</return> (zero) if no error occurred.

<comment>See Also:</comment>
   * <strong>curl_error()</strong>
   * Curl error codes


id: curl_error
type: function
doc:
<comment>Description:</comment>
  Return a string containing the last error for the current session
  
  Returns a clear text error message for the last cURL operation.

<comment>Param:</comment>
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>string</info>  Returns the error message or <return>''</return> (the empty string) if no error occurred.

<comment>See Also:</comment>
   * <strong>curl_errno()</strong>
   * Curl error codes


id: curl_escape
type: function
doc:
<comment>Description:</comment>
  URL encodes the given string
  
  This function URL encodes the given string according to RFC 3986.

<comment>Param:</comment>
  <info>      </info>  <strong>$ch    </strong>  Un handle cURL întors de
                   <strong>curl_init()</strong>.
  <info>string</info>  <strong>$string</strong>  The string to be encoded.

<comment>Return:</comment>
  <info>stringfalse</info>  Returns escaped string sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>curl_unescape()</strong>
   * <strong>urlencode()</strong>
   * <strong>rawurlencode()</strong>
   * RFC 3986


id: curl_exec
type: function
doc:
<comment>Description:</comment>
  Perform a cURL session
  
  Execute the given cURL session.
  
  This function should be called after initializing a cURL session and all the options for the
  session are set.

<comment>Param:</comment>
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>stringbool</info>  Întoarce valoarea <info>true</info> în cazul
              succesului sau <info>false</info> în cazul eșecului. However, if the <info>CURLOPT_RETURNTRANSFER</info> option
              is set, it will return the result on success, <info>false</info> on failure.
              
              Această funcție poate întoarce valoarea Boolean <info>false</info>, dar poate de
              asemenea întoarce o valoare non-Boolean care evaluează în <info>false</info>. Vă rugăm să
              citiți secțiunea despre tipul Boolean
              pentru informații suplimentare. Utilizați
              operatorul === pentru a
              verifica valoarea întoarsă de această funcție.
              
              Note that response status codes which indicate errors (such as <return>404 Not found</return>) are not
              regarded as failure. <strong>curl_getinfo()</strong> can be used to check for these.

<comment>See Also:</comment>
   * <strong>curl_multi_exec()</strong>


id: curl_getinfo
type: function
doc:
<comment>Description:</comment>
  Get information regarding a specific transfer
  
  Gets information about the last transfer.

<comment>Param:</comment>
  <info>       </info>  <strong>$ch    </strong>  Un handle cURL întors de
                    <strong>curl_init()</strong>.
  <info>intnull</info>  <strong>$option</strong>  This may be one of the following constants: <info>CURLINFO_EFFECTIVE_URL</info> - Last
                    effective URL <info>CURLINFO_HTTP_CODE</info> -  The last response code. As of PHP 5.5.0 and
                    cURL 7.10.8, this is a legacy alias of <info>CURLINFO_RESPONSE_CODE</info> <info>CURLINFO_FILETIME</info>
                    - Remote time of the retrieved document, with the <info>CURLOPT_FILETIME</info> enabled; if
                    -1 is returned the time of the document is unknown <info>CURLINFO_TOTAL_TIME</info> - Total
                    transaction time in seconds for last transfer <info>CURLINFO_NAMELOOKUP_TIME</info> - Time in
                    seconds until name resolving was complete <info>CURLINFO_CONNECT_TIME</info> - Time in
                    seconds it took to establish the connection <info>CURLINFO_PRETRANSFER_TIME</info> - Time in
                    seconds from start until just before file transfer begins
                    <info>CURLINFO_STARTTRANSFER_TIME</info> - Time in seconds until the first byte is about to
                    be transferred <info>CURLINFO_REDIRECT_COUNT</info> - Number of redirects, with the
                    <info>CURLOPT_FOLLOWLOCATION</info> option enabled <info>CURLINFO_REDIRECT_TIME</info> - Time in seconds
                    of all redirection steps before final transaction was started, with the
                    <info>CURLOPT_FOLLOWLOCATION</info> option enabled <info>CURLINFO_REDIRECT_URL</info> - With the
                    <info>CURLOPT_FOLLOWLOCATION</info> option disabled: redirect URL found in the last
                    transaction, that should be requested manually next. With the
                    <info>CURLOPT_FOLLOWLOCATION</info> option enabled: this is empty. The redirect URL in this
                    case is available in <info>CURLINFO_EFFECTIVE_URL</info>  <info>CURLINFO_PRIMARY_IP</info> - IP address of
                    the most recent connection <info>CURLINFO_PRIMARY_PORT</info> - Destination port of the most
                    recent connection <info>CURLINFO_LOCAL_IP</info> - Local (source) IP address of the most
                    recent connection <info>CURLINFO_LOCAL_PORT</info> - Local (source) port of the most recent
                    connection <info>CURLINFO_SIZE_UPLOAD</info> - Total number of bytes uploaded
                    <info>CURLINFO_SIZE_DOWNLOAD</info> - Total number of bytes downloaded
                    <info>CURLINFO_SPEED_DOWNLOAD</info> - Average download speed <info>CURLINFO_SPEED_UPLOAD</info> - Average
                    upload speed <info>CURLINFO_HEADER_SIZE</info> - Total size of all headers received
                    <info>CURLINFO_HEADER_OUT</info> - The request string sent. For this to  work, add the
                    <info>CURLINFO_HEADER_OUT</info> option to the handle by calling  <strong>curl_setopt()</strong>
                    <info>CURLINFO_REQUEST_SIZE</info> - Total size of issued requests, currently only for HTTP
                    requests <info>CURLINFO_SSL_VERIFYRESULT</info> - Result of SSL certification verification
                    requested by setting <info>CURLOPT_SSL_VERIFYPEER</info> <info>CURLINFO_CONTENT_LENGTH_DOWNLOAD</info> -
                    Content length of download, read from <return>Content-Length:</return> field
                    <info>CURLINFO_CONTENT_LENGTH_UPLOAD</info> - Specified size of upload <info>CURLINFO_CONTENT_TYPE</info>
                    - <return>Content-Type:</return> of the requested document. NULL indicates server did not send
                    valid <return>Content-Type:</return> header <info>CURLINFO_PRIVATE</info> - Private data associated with this
                    cURL handle, previously set with the <info>CURLOPT_PRIVATE</info> option of <strong>curl_setopt()</strong>
                    <info>CURLINFO_RESPONSE_CODE</info> - The last response code <info>CURLINFO_HTTP_CONNECTCODE</info> - The
                    CONNECT response code <info>CURLINFO_HTTPAUTH_AVAIL</info> - Bitmask indicating the
                    authentication method(s) available according to the previous response
                    <info>CURLINFO_PROXYAUTH_AVAIL</info> - Bitmask indicating the proxy authentication method(s)
                    available according to the previous response <info>CURLINFO_OS_ERRNO</info> - Errno from a
                    connect failure. The number is OS and system specific. <info>CURLINFO_NUM_CONNECTS</info> -
                    Number of connections curl had to create to achieve the previous transfer
                    <info>CURLINFO_SSL_ENGINES</info> - OpenSSL crypto-engines supported <info>CURLINFO_COOKIELIST</info> -
                    All known cookies <info>CURLINFO_FTP_ENTRY_PATH</info> - Entry path in FTP server
                    <info>CURLINFO_APPCONNECT_TIME</info> - Time in seconds it took from the start until the
                    SSL/SSH connect/handshake to the remote host was completed <info>CURLINFO_CERTINFO</info> -
                    TLS certificate chain <info>CURLINFO_CONDITION_UNMET</info> - Info on unmet time conditional
                    <info>CURLINFO_RTSP_CLIENT_CSEQ</info> - Next RTSP client CSeq <info>CURLINFO_RTSP_CSEQ_RECV</info> -
                    Recently received CSeq <info>CURLINFO_RTSP_SERVER_CSEQ</info> - Next RTSP server CSeq
                    <info>CURLINFO_RTSP_SESSION_ID</info> - RTSP session ID <info>CURLINFO_CONTENT_LENGTH_DOWNLOAD_T</info> -
                    The content-length of the download. This is the value read from the
                    <return>Content-Type:</return> field. -1 if the size isn't known <info>CURLINFO_CONTENT_LENGTH_UPLOAD_T</info>
                    - The specified size of the upload. -1 if the size isn't known
                    <info>CURLINFO_HTTP_VERSION</info> - The version used in the last HTTP connection. The return
                    value will be one of the defined <info>CURL_HTTP_VERSION_*</info> constants or 0 if the
                    version can't be determined <info>CURLINFO_PROTOCOL</info> - The protocol used in the last
                    HTTP connection. The returned value will be exactly one of the <info>CURLPROTO_*</info>
                    values <info>CURLINFO_PROXY_SSL_VERIFYRESULT</info> - The result of the certificate
                    verification that was requested (using the <info>CURLOPT_PROXY_SSL_VERIFYPEER</info> option).
                    Only used for HTTPS proxies <info>CURLINFO_SCHEME</info> - The URL scheme used for the most
                    recent connection <info>CURLINFO_SIZE_DOWNLOAD_T</info> - Total number of bytes that were
                    downloaded. The number is only for the latest transfer and will be reset again
                    for each new transfer <info>CURLINFO_SIZE_UPLOAD_T</info> - Total number of bytes that were
                    uploaded <info>CURLINFO_SPEED_DOWNLOAD_T</info> - The average download speed in bytes/second
                    that curl measured for the complete download <info>CURLINFO_SPEED_UPLOAD_T</info> - The
                    average upload speed in bytes/second that curl measured for the complete upload
                    <info>CURLINFO_APPCONNECT_TIME_T</info> - Time, in microseconds, it took from the start until
                    the SSL/SSH connect/handshake to the remote host was completed
                    <info>CURLINFO_CONNECT_TIME_T</info> - Total time taken, in microseconds, from the start
                    until the connection to the remote host (or proxy) was completed
                    <info>CURLINFO_FILETIME_T</info> - Remote time of the retrieved document (as Unix timestamp),
                    an alternative to <info>CURLINFO_FILETIME</info> to allow systems with 32 bit long variables
                    to extract dates outside of the 32bit timestamp range <info>CURLINFO_NAMELOOKUP_TIME_T</info>
                    - Time in microseconds from the start until the name resolving was completed
                    <info>CURLINFO_PRETRANSFER_TIME_T</info> - Time taken from the start until the file transfer
                    is just about to begin, in microseconds <info>CURLINFO_REDIRECT_TIME_T</info> - Total time,
                    in microseconds, it took for all redirection steps include name lookup, connect,
                    pretransfer and transfer before final transaction was started
                    <info>CURLINFO_STARTTRANSFER_TIME_T</info> - Time, in microseconds, it took from the start
                    until the first byte is received <info>CURLINFO_TOTAL_TIME_T</info> - Total time in
                    microseconds for the previous transfer, including name resolving, TCP connect
                    etc.
                    
                    <info>CURLINFO_EFFECTIVE_URL</info> - Last effective URL
                    
                    <info>CURLINFO_HTTP_CODE</info> -  The last response code. As of PHP 5.5.0 and cURL 7.10.8,
                    this is a legacy alias of <info>CURLINFO_RESPONSE_CODE</info>
                    
                    <info>CURLINFO_FILETIME</info> - Remote time of the retrieved document, with the
                    <info>CURLOPT_FILETIME</info> enabled; if -1 is returned the time of the document is unknown
                    
                    <info>CURLINFO_TOTAL_TIME</info> - Total transaction time in seconds for last transfer
                    
                    <info>CURLINFO_NAMELOOKUP_TIME</info> - Time in seconds until name resolving was complete
                    
                    <info>CURLINFO_CONNECT_TIME</info> - Time in seconds it took to establish the connection
                    
                    <info>CURLINFO_PRETRANSFER_TIME</info> - Time in seconds from start until just before file
                    transfer begins
                    
                    <info>CURLINFO_STARTTRANSFER_TIME</info> - Time in seconds until the first byte is about to
                    be transferred
                    
                    <info>CURLINFO_REDIRECT_COUNT</info> - Number of redirects, with the <info>CURLOPT_FOLLOWLOCATION</info>
                    option enabled
                    
                    <info>CURLINFO_REDIRECT_TIME</info> - Time in seconds of all redirection steps before final
                    transaction was started, with the <info>CURLOPT_FOLLOWLOCATION</info> option enabled
                    
                    <info>CURLINFO_REDIRECT_URL</info> - With the <info>CURLOPT_FOLLOWLOCATION</info> option disabled:
                    redirect URL found in the last transaction, that should be requested manually
                    next. With the <info>CURLOPT_FOLLOWLOCATION</info> option enabled: this is empty. The
                    redirect URL in this case is available in <info>CURLINFO_EFFECTIVE_URL</info>
                    
                    <info>CURLINFO_PRIMARY_IP</info> - IP address of the most recent connection
                    
                    <info>CURLINFO_PRIMARY_PORT</info> - Destination port of the most recent connection
                    
                    <info>CURLINFO_LOCAL_IP</info> - Local (source) IP address of the most recent connection
                    
                    <info>CURLINFO_LOCAL_PORT</info> - Local (source) port of the most recent connection
                    
                    <info>CURLINFO_SIZE_UPLOAD</info> - Total number of bytes uploaded
                    
                    <info>CURLINFO_SIZE_DOWNLOAD</info> - Total number of bytes downloaded
                    
                    <info>CURLINFO_SPEED_DOWNLOAD</info> - Average download speed
                    
                    <info>CURLINFO_SPEED_UPLOAD</info> - Average upload speed
                    
                    <info>CURLINFO_HEADER_SIZE</info> - Total size of all headers received
                    
                    <info>CURLINFO_HEADER_OUT</info> - The request string sent. For this to  work, add the
                    <info>CURLINFO_HEADER_OUT</info> option to the handle by calling  <strong>curl_setopt()</strong>
                    
                    <info>CURLINFO_REQUEST_SIZE</info> - Total size of issued requests, currently only for HTTP
                    requests
                    
                    <info>CURLINFO_SSL_VERIFYRESULT</info> - Result of SSL certification verification requested
                    by setting <info>CURLOPT_SSL_VERIFYPEER</info>
                    
                    <info>CURLINFO_CONTENT_LENGTH_DOWNLOAD</info> - Content length of download, read from
                    <return>Content-Length:</return> field
                    
                    <info>CURLINFO_CONTENT_LENGTH_UPLOAD</info> - Specified size of upload
                    
                    <info>CURLINFO_CONTENT_TYPE</info> - <return>Content-Type:</return> of the requested document. NULL indicates
                    server did not send valid <return>Content-Type:</return> header
                    
                    <info>CURLINFO_PRIVATE</info> - Private data associated with this cURL handle, previously set
                    with the <info>CURLOPT_PRIVATE</info> option of <strong>curl_setopt()</strong>
                    
                    <info>CURLINFO_RESPONSE_CODE</info> - The last response code
                    
                    <info>CURLINFO_HTTP_CONNECTCODE</info> - The CONNECT response code
                    
                    <info>CURLINFO_HTTPAUTH_AVAIL</info> - Bitmask indicating the authentication method(s)
                    available according to the previous response
                    
                    <info>CURLINFO_PROXYAUTH_AVAIL</info> - Bitmask indicating the proxy authentication method(s)
                    available according to the previous response
                    
                    <info>CURLINFO_OS_ERRNO</info> - Errno from a connect failure. The number is OS and system
                    specific.
                    
                    <info>CURLINFO_NUM_CONNECTS</info> - Number of connections curl had to create to achieve the
                    previous transfer
                    
                    <info>CURLINFO_SSL_ENGINES</info> - OpenSSL crypto-engines supported
                    
                    <info>CURLINFO_COOKIELIST</info> - All known cookies
                    
                    <info>CURLINFO_FTP_ENTRY_PATH</info> - Entry path in FTP server
                    
                    <info>CURLINFO_APPCONNECT_TIME</info> - Time in seconds it took from the start until the
                    SSL/SSH connect/handshake to the remote host was completed
                    
                    <info>CURLINFO_CERTINFO</info> - TLS certificate chain
                    
                    <info>CURLINFO_CONDITION_UNMET</info> - Info on unmet time conditional
                    
                    <info>CURLINFO_RTSP_CLIENT_CSEQ</info> - Next RTSP client CSeq
                    
                    <info>CURLINFO_RTSP_CSEQ_RECV</info> - Recently received CSeq
                    
                    <info>CURLINFO_RTSP_SERVER_CSEQ</info> - Next RTSP server CSeq
                    
                    <info>CURLINFO_RTSP_SESSION_ID</info> - RTSP session ID
                    
                    <info>CURLINFO_CONTENT_LENGTH_DOWNLOAD_T</info> - The content-length of the download. This is
                    the value read from the <return>Content-Type:</return> field. -1 if the size isn't known
                    
                    <info>CURLINFO_CONTENT_LENGTH_UPLOAD_T</info> - The specified size of the upload. -1 if the
                    size isn't known
                    
                    <info>CURLINFO_HTTP_VERSION</info> - The version used in the last HTTP connection. The return
                    value will be one of the defined <info>CURL_HTTP_VERSION_*</info> constants or 0 if the
                    version can't be determined
                    
                    <info>CURLINFO_PROTOCOL</info> - The protocol used in the last HTTP connection. The returned
                    value will be exactly one of the <info>CURLPROTO_*</info> values
                    
                    <info>CURLINFO_PROXY_SSL_VERIFYRESULT</info> - The result of the certificate verification
                    that was requested (using the <info>CURLOPT_PROXY_SSL_VERIFYPEER</info> option). Only used
                    for HTTPS proxies
                    
                    <info>CURLINFO_SCHEME</info> - The URL scheme used for the most recent connection
                    
                    <info>CURLINFO_SIZE_DOWNLOAD_T</info> - Total number of bytes that were downloaded. The
                    number is only for the latest transfer and will be reset again for each new
                    transfer
                    
                    <info>CURLINFO_SIZE_UPLOAD_T</info> - Total number of bytes that were uploaded
                    
                    <info>CURLINFO_SPEED_DOWNLOAD_T</info> - The average download speed in bytes/second that curl
                    measured for the complete download
                    
                    <info>CURLINFO_SPEED_UPLOAD_T</info> - The average upload speed in bytes/second that curl
                    measured for the complete upload
                    
                    <info>CURLINFO_APPCONNECT_TIME_T</info> - Time, in microseconds, it took from the start until
                    the SSL/SSH connect/handshake to the remote host was completed
                    
                    <info>CURLINFO_CONNECT_TIME_T</info> - Total time taken, in microseconds, from the start
                    until the connection to the remote host (or proxy) was completed
                    
                    <info>CURLINFO_FILETIME_T</info> - Remote time of the retrieved document (as Unix timestamp),
                    an alternative to <info>CURLINFO_FILETIME</info> to allow systems with 32 bit long variables
                    to extract dates outside of the 32bit timestamp range
                    
                    <info>CURLINFO_NAMELOOKUP_TIME_T</info> - Time in microseconds from the start until the name
                    resolving was completed
                    
                    <info>CURLINFO_PRETRANSFER_TIME_T</info> - Time taken from the start until the file transfer
                    is just about to begin, in microseconds
                    
                    <info>CURLINFO_REDIRECT_TIME_T</info> - Total time, in microseconds, it took for all
                    redirection steps include name lookup, connect, pretransfer and transfer before
                    final transaction was started
                    
                    <info>CURLINFO_STARTTRANSFER_TIME_T</info> - Time, in microseconds, it took from the start
                    until the first byte is received
                    
                    <info>CURLINFO_TOTAL_TIME_T</info> - Total time in microseconds for the previous transfer,
                    including name resolving, TCP connect etc.

<comment>Return:</comment>
  <info>mixed</info>  If <strong>$option</strong> is given, returns its value. Otherwise, returns an associative array with the
         following elements  (which correspond to <strong>$option</strong>), or <info>false</info> on failure:  "url"
         "content_type"  "http_code"  "header_size"  "request_size"  "filetime"  "ssl_verify_result"
         "redirect_count"  "total_time"  "namelookup_time"  "connect_time"  "pretransfer_time"
         "size_upload"  "size_download"  "speed_download"  "speed_upload"  "download_content_length"
         "upload_content_length"  "starttransfer_time"  "redirect_time"  "certinfo"  "primary_ip"
         "primary_port"  "local_ip"  "local_port"  "redirect_url"  "request_header" (This is only
         set if the <info>CURLINFO_HEADER_OUT</info>  is set by a previous call to <strong>curl_setopt()</strong>)  Note that
         private data is not included in the associative array and must be retrieved individually
         with the <info>CURLINFO_PRIVATE</info> option.
         
         "url"
         
         "content_type"
         
         "http_code"
         
         "header_size"
         
         "request_size"
         
         "filetime"
         
         "ssl_verify_result"
         
         "redirect_count"
         
         "total_time"
         
         "namelookup_time"
         
         "connect_time"
         
         "pretransfer_time"
         
         "size_upload"
         
         "size_download"
         
         "speed_download"
         
         "speed_upload"
         
         "download_content_length"
         
         "upload_content_length"
         
         "starttransfer_time"
         
         "redirect_time"
         
         "certinfo"
         
         "primary_ip"
         
         "primary_port"
         
         "local_ip"
         
         "local_port"
         
         "redirect_url"
         
         "request_header" (This is only set if the <info>CURLINFO_HEADER_OUT</info>  is set by a previous call to
         <strong>curl_setopt()</strong>)


id: curl_init
type: function
doc:
<comment>Description:</comment>
  Initialize a cURL session
  
  Initializes a new session and return a cURL handle for use with the <strong>curl_setopt()</strong>, <strong>curl_exec()</strong>,
  and <strong>curl_close()</strong> functions.

<comment>Param:</comment>
  <info>stringnull</info>  <strong>$url</strong>  If provided, the <info>CURLOPT_URL</info> option will be set to its value. You can manually
                    set this using the  <strong>curl_setopt()</strong> function.
                    
                    The <return>file</return> protocol is disabled by cURL if open_basedir is set.

<comment>Return:</comment>
  <info>CurlHandlefalse</info>  Returns a cURL handle on success, <info>false</info> on errors.

<comment>See Also:</comment>
   * <strong>curl_close()</strong>
   * <strong>curl_multi_init()</strong>


id: curl_multi_add_handle
type: function
doc:
<comment>Description:</comment>
  Add a normal cURL handle to a cURL multi handle
  
  Adds the <strong>$handle</strong> handle to the multi handle  <strong>$multi_handle</strong>

<comment>Param:</comment>
  <info></info>  <strong>$mh</strong>  Un multi-handle cURL
         întors de <strong>curl_multi_init()</strong>.
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>int</info>  Returns 0 on success, or one of the <info>CURLM_XXX</info> errors code.

<comment>See Also:</comment>
   * <strong>curl_multi_remove_handle()</strong>
   * <strong>curl_multi_init()</strong>
   * <strong>curl_init()</strong>


id: curl_multi_close
type: function
doc:
<comment>Description:</comment>
  Close a set of cURL handles
  
  Closes a set of cURL handles.

<comment>Param:</comment>
  <info></info>  <strong>$mh</strong>  Un multi-handle cURL
         întors de <strong>curl_multi_init()</strong>.

<comment>Return:</comment>
  <info>void</info>  Nu este întoarsă nici o valoare.

<comment>See Also:</comment>
   * <strong>curl_multi_init()</strong>
   * <strong>curl_close()</strong>


id: curl_multi_errno
type: function
doc:
<comment>Description:</comment>
  Return the last multi curl error number
  
  Return an integer containing the last multi curl error number.

<comment>Param:</comment>
  <info></info>  <strong>$mh</strong>  Un multi-handle cURL
         întors de <strong>curl_multi_init()</strong>.

<comment>Return:</comment>
  <info>int</info>  Return an integer containing the last multi curl error number.

<comment>See Also:</comment>
   * <strong>curl_errno()</strong>


id: curl_multi_exec
type: function
doc:
<comment>Description:</comment>
  Run the sub-connections of the current cURL handle
  
  Processes each of the handles in the stack.  This method can be called whether or not a handle
  needs to read or write data.

<comment>Param:</comment>
  <info>   </info>  <strong>$mh           </strong>  Un multi-handle cURL
                       întors de <strong>curl_multi_init()</strong>.
  <info>int</info>  <strong>$still_running</strong>  A reference to a flag to tell whether the operations are still running.

<comment>Return:</comment>
  <info>int</info>  A cURL code defined in the cURL Predefined Constants.
       
       This only returns errors regarding the whole multi stack. There might still have  occurred
       problems on individual transfers even when this function returns  <info>CURLM_OK</info>.

<comment>See Also:</comment>
   * <strong>curl_multi_init()</strong>
   * <strong>curl_multi_select()</strong>
   * <strong>curl_exec()</strong>


id: curl_multi_getcontent
type: function
doc:
<comment>Description:</comment>
  Return the content of a cURL handle if CURLOPT_RETURNTRANSFER is set
  
  If <info>CURLOPT_RETURNTRANSFER</info> is an option that is set for a specific handle,  then this function will
  return the content of that cURL handle in the form of a string.

<comment>Param:</comment>
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>stringnull</info>  Return the content of a cURL handle if <info>CURLOPT_RETURNTRANSFER</info> is set.

<comment>See Also:</comment>
   * <strong>curl_multi_init()</strong>


id: curl_multi_info_read
type: function
doc:
<comment>Description:</comment>
  Get information about the current transfers
  
  Ask the multi handle if there are any messages or information from the individual transfers.
  Messages may include information such as an error code from the transfer or just the fact  that a
  transfer is completed.
  
  Repeated calls to this function will return a new result each time, until a <info>false</info> is returned  as
  a signal that there is no more to get at this point. The integer pointed to with  <strong>$queued_messages</strong>
  will contain the number of remaining messages after this  function was called.
  
  The data the returned resource points to will not survive calling  <strong>curl_multi_remove_handle()</strong>.

<comment>Param:</comment>
  <info>   </info>  <strong>$mh             </strong>  Un multi-handle cURL
                         întors de <strong>curl_multi_init()</strong>.
  <info>int</info>  <strong>$queued_messages</strong>  Number of messages that are still in the queue

<comment>Return:</comment>
  <info>arrayfalse</info>  On success, returns an associative array for the message, <info>false</info> on failure.
              
              Contents of the returned arrayKey:Value:<return>msg</return>The <info>CURLMSG_DONE</info> constant. Other return
              values are currently not available.<return>result</return>One of the <info>CURLE_*</info> constants. If everything
              is OK, the <info>CURLE_OK</info> will be the result.<return>handle</return>Resource of type curl indicates the
              handle which it concerns.

<comment>See Also:</comment>
   * <strong>curl_multi_init()</strong>


id: curl_multi_init
type: function
doc:
<comment>Description:</comment>
  Returns a new cURL multi handle
  
  Allows the processing of multiple cURL handles asynchronously.

<comment>Return:</comment>
  <info>CurlMultiHandle</info>  Returns a cURL multi handle on success, <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>curl_init()</strong>
   * <strong>curl_multi_close()</strong>


id: curl_multi_remove_handle
type: function
doc:
<comment>Description:</comment>
  Remove a multi handle from a set of cURL handles
  
  Removes a given <strong>$handle</strong> handle from the given <strong>$multi_handle</strong> handle. When the <strong>$handle</strong> handle has
  been removed, it is again perfectly  legal to run <strong>curl_exec()</strong> on this handle.  Removing the
  <strong>$handle</strong> handle while being  used, will effectively halt the transfer in progress involving that
  handle.

<comment>Param:</comment>
  <info></info>  <strong>$mh</strong>  Un multi-handle cURL
         întors de <strong>curl_multi_init()</strong>.
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>int</info>  Returns 0 on success, or one of the <info>CURLM_XXX</info> error codes.

<comment>See Also:</comment>
   * <strong>curl_init()</strong>
   * <strong>curl_multi_init()</strong>
   * <strong>curl_multi_add_handle()</strong>


id: curl_multi_select
type: function
doc:
<comment>Description:</comment>
  Wait for activity on any curl_multi connection
  
  Blocks until there is activity on any of the curl_multi connections.

<comment>Param:</comment>
  <info>     </info>  <strong>$mh     </strong>  Un multi-handle cURL
                   întors de <strong>curl_multi_init()</strong>.
  <info>float</info>  <strong>$timeout</strong>  Time, in seconds, to wait for a response.

<comment>Return:</comment>
  <info>int</info>  On success, returns the number of descriptors contained in  the descriptor sets. This may be
       0 if there was no activity on any of the descriptors. On failure, this function will return
       -1 on a select failure (from the underlying select system call).

<comment>See Also:</comment>
   * <strong>curl_multi_init()</strong>


id: curl_multi_setopt
type: function
doc:
<comment>Description:</comment>
  Set an option for the cURL multi handle
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>CurlMultiHandle</info>  <strong>$multi_handle</strong>  
  <info>int            </info>  <strong>$option      </strong>  One of the <info>CURLMOPT_*</info> constants.
  <info>mixed          </info>  <strong>$value       </strong>  The value to be set on <strong>$option</strong>.
                                  
                                  <strong>$value</strong> should be an <info>int</info> for the following values of the <strong>$option</strong>
                                  parameter: OptionSet <strong>$value</strong> to<info>CURLMOPT_PIPELINING</info> Pass 1 to enable
                                  or 0 to disable. Enabling pipelining on a multi handle will make
                                  it attempt to perform HTTP Pipelining as far as possible for
                                  transfers using this handle. This means that if you add a second
                                  request that can use an already existing connection, the second
                                  request will be "piped" on the same connection. As of cURL 7.43.0,
                                  the value is a bitmask, and you can also pass 2 to try to
                                  multiplex the new transfer over an existing HTTP/2 connection if
                                  possible. Passing 3 instructs cURL to ask for pipelining and
                                  multiplexing independently of each other. As of cURL 7.62.0,
                                  setting the pipelining bit has no effect. Instead of integer
                                  literals, you can also use the CURLPIPE_* constants if available.
                                  <info>CURLMOPT_MAXCONNECTS</info> Pass a number that will be used as the
                                  maximum amount of simultaneously open connections that libcurl may
                                  cache. By default the size will be enlarged to fit four times the
                                  number of handles added via <strong>curl_multi_add_handle()</strong>. When the
                                  cache is full, curl closes the oldest one in the cache to prevent
                                  the number of open connections from increasing.
                                  <info>CURLMOPT_CHUNK_LENGTH_PENALTY_SIZE</info> Pass a number that specifies
                                  the chunk length threshold for pipelining in bytes.
                                  <info>CURLMOPT_CONTENT_LENGTH_PENALTY_SIZE</info> Pass a number that specifies
                                  the size threshold for pipelining penalty in bytes.
                                  <info>CURLMOPT_MAX_HOST_CONNECTIONS</info> Pass a number that specifies the
                                  maximum number of connections to a single host.
                                  <info>CURLMOPT_MAX_PIPELINE_LENGTH</info> Pass a number that specifies the
                                  maximum number of requests in a pipeline.
                                  <info>CURLMOPT_MAX_TOTAL_CONNECTIONS</info> Pass a number that specifies the
                                  maximum number of simultaneously open connections.
                                  <info>CURLMOPT_PUSHFUNCTION</info> Pass a <info>callable</info> that will be registered to
                                  handle server pushes and should have the following signature:
                                  <info>int</info>pushfunction<info>resource</info><strong>$parent_ch</strong><info>resource</info><strong>$pushed_ch</strong><info>array</info><strong>$headers</strong>
                                  <strong>$parent_ch</strong> The parent cURL handle (the request the client made).
                                  <strong>$pushed_ch</strong> A new cURL handle for the pushed request. <strong>$headers</strong> The
                                  push promise headers.  The push function is supposed to return
                                  either <info>CURL_PUSH_OK</info> if it can handle the push, or <info>CURL_PUSH_DENY</info>
                                  to reject it.
                                  
                                  The parent cURL handle (the request the client made).
                                  
                                  A new cURL handle for the pushed request.
                                  
                                  The push promise headers.
  <info>resource       </info>  <strong>$parent_ch   </strong>  The parent cURL handle (the request the client made).
  <info>resource       </info>  <strong>$pushed_ch   </strong>  A new cURL handle for the pushed request.
  <info>array          </info>  <strong>$headers     </strong>  The push promise headers.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.


id: curl_multi_strerror
type: function
doc:
<comment>Description:</comment>
  Return string describing error code
  
  Returns a text error message describing the given CURLM error code.

<comment>Param:</comment>
  <info>int</info>  <strong>$error_code</strong>  One of the CURLM error codes constants.

<comment>Return:</comment>
  <info>stringnull</info>  Returns error string for valid error code, <info>null</info> otherwise.

<comment>See Also:</comment>
   * <strong>curl_strerror()</strong>
   * cURL error codes


id: curl_pause
type: function
doc:
<comment>Description:</comment>
  Pause and unpause a connection
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>   </info>  <strong>$ch   </strong>  Un handle cURL întors de
               <strong>curl_init()</strong>.
  <info>int</info>  <strong>$flags</strong>  One of <info>CURLPAUSE_*</info> constants.

<comment>Return:</comment>
  <info>int</info>  Returns an error code (<info>CURLE_OK</info> for no error).


id: curl_reset
type: function
doc:
<comment>Description:</comment>
  Reset all options of a libcurl session handle
  
  This function re-initializes all options set on the given cURL handle to the default values.

<comment>Param:</comment>
  <info></info>  <strong>$ch</strong>  Un handle cURL întors de
         <strong>curl_init()</strong>.

<comment>Return:</comment>
  <info>void</info>  Nu este întoarsă nici o valoare.

<comment>See Also:</comment>
   * <strong>curl_setopt()</strong>


id: curl_setopt
type: function
doc:
<comment>Description:</comment>
  Set an option for a cURL transfer
  
  Sets an option on the given cURL session handle.

<comment>Param:</comment>
  <info>     </info>  <strong>$ch    </strong>  Un handle cURL întors de
                  <strong>curl_init()</strong>.
  <info>int  </info>  <strong>$option</strong>  The <return>CURLOPT_XXX</return> option to set.
  <info>mixed</info>  <strong>$value </strong>  The value to be set on <strong>$option</strong>.
                  
                  <strong>$value</strong> should be a <info>bool</info> for the following values of the <strong>$option</strong> parameter:
                  OptionSet <strong>$value</strong> toNotes<info>CURLOPT_AUTOREFERER</info><info>true</info> to automatically set the <return>Referer:</return>
                  field in requests where it follows a <return>Location:</return> redirect.
                  <info>CURLOPT_BINARYTRANSFER</info><info>true</info> to return the raw output when <info>CURLOPT_RETURNTRANSFER</info> is
                  used.  From PHP 5.1.3, this option has no effect: the raw output will always be
                  returned when <info>CURLOPT_RETURNTRANSFER</info> is used. <info>CURLOPT_COOKIESESSION</info><info>true</info> to mark
                  this as a new cookie "session". It will force libcurl to ignore all cookies it is
                  about to load that are "session cookies" from the previous session. By default,
                  libcurl always stores and loads all cookies, independent if they are session
                  cookies or not. Session cookies are cookies without expiry date and they are meant
                  to be alive and existing for this "session" only.  <info>CURLOPT_CERTINFO</info><info>true</info> to output
                  SSL certification information to <return>STDERR</return> on secure transfers.  Added in cURL
                  7.19.1.  Available since PHP 5.3.2.  Requires <info>CURLOPT_VERBOSE</info> to be on to have an
                  effect. <info>CURLOPT_CONNECT_ONLY</info><info>true</info> tells the library to perform all the required
                  proxy authentication  and connection setup, but no data transfer. This option is
                  implemented for  HTTP, SMTP and POP3.  Added in 7.15.2. Available since PHP 5.5.0.
                  <info>CURLOPT_CRLF</info><info>true</info> to convert Unix newlines to CRLF newlines on transfers.
                  <info>CURLOPT_DISALLOW_USERNAME_IN_URL</info><info>true</info> to not allow URLs that include a username.
                  Usernames are allowed by default (0).  Added in cURL 7.61.0. Available since PHP
                  7.3.0. <info>CURLOPT_DNS_SHUFFLE_ADDRESSES</info><info>true</info> to shuffle the order of all returned
                  addresses so that they will be used  in a random order, when a name is resolved
                  and more than one IP address is returned. This may cause IPv4 to be used before
                  IPv6 or vice versa.  Added in cURL 7.60.0. Available since PHP 7.3.0.
                  <info>CURLOPT_HAPROXYPROTOCOL</info><info>true</info> to send an HAProxy PROXY protocol v1 header at the
                  start of the connection. The default action is not to send this header.  Added in
                  cURL 7.60.0. Available since PHP 7.3.0. <info>CURLOPT_SSH_COMPRESSION</info><info>true</info> to enable
                  built-in SSH compression. This is a request, not an order;  the server may or may
                  not do it.  Added in cURL 7.56.0. Available since PHP 7.3.0.
                  <info>CURLOPT_DNS_USE_GLOBAL_CACHE</info><info>true</info> to use a global DNS cache. This option is not
                  thread-safe. It is conditionally enabled by default if PHP is built for
                  non-threaded use (CLI, FCGI, Apache2-Prefork, etc.).  <info>CURLOPT_FAILONERROR</info><info>true</info> to
                  fail verbosely if the HTTP code returned is greater than or equal to 400. The
                  default behavior is to return the page normally, ignoring the code.
                  <info>CURLOPT_SSL_FALSESTART</info><info>true</info> to enable TLS false start.  Added in cURL 7.42.0.
                  Available since PHP 7.0.7. <info>CURLOPT_FILETIME</info><info>true</info> to attempt to retrieve the
                  modification date of the remote document. This value can be retrieved using the
                  <info>CURLINFO_FILETIME</info> option with <strong>curl_getinfo()</strong>.  <info>CURLOPT_FOLLOWLOCATION</info><info>true</info> to
                  follow any <return>"Location: "</return> header that the server sends as part of the HTTP header
                  (note this is recursive, PHP will follow as many <return>"Location: "</return> headers that it is
                  sent, unless <info>CURLOPT_MAXREDIRS</info> is set).  <info>CURLOPT_FORBID_REUSE</info><info>true</info> to force the
                  connection to explicitly close when it has finished processing, and not be pooled
                  for reuse.  <info>CURLOPT_FRESH_CONNECT</info><info>true</info> to force the use of a new connection instead
                  of a cached one.  <info>CURLOPT_FTP_USE_EPRT</info><info>true</info> to use EPRT (and LPRT) when doing
                  active FTP downloads. Use <info>false</info> to disable EPRT and LPRT and use PORT only.
                  <info>CURLOPT_FTP_USE_EPSV</info><info>true</info> to first try an EPSV command for FTP transfers before
                  reverting back to PASV. Set to <info>false</info> to disable EPSV.
                  <info>CURLOPT_FTP_CREATE_MISSING_DIRS</info><info>true</info> to create missing directories when an FTP
                  operation encounters a path that currently doesn't exist.  <info>CURLOPT_FTPAPPEND</info><info>true</info>
                  to append to the remote file instead of overwriting it.  <info>CURLOPT_TCP_NODELAY</info><info>true</info>
                  to disable TCP's Nagle algorithm, which tries to minimize the number of small
                  packets on the network.  Available since PHP 5.2.1 for versions compiled with
                  libcurl 7.11.2 or greater. <info>CURLOPT_FTPASCII</info> An alias of <info>CURLOPT_TRANSFERTEXT</info>. Use
                  that instead.  <info>CURLOPT_FTPLISTONLY</info><info>true</info> to only list the names of an FTP directory.
                  <info>CURLOPT_HEADER</info><info>true</info> to include the header in the output.  <info>CURLINFO_HEADER_OUT</info><info>true</info>
                  to track the handle's request string.  Available since PHP 5.1.3. The <info>CURLINFO_</info>
                  prefix is intentional. <info>CURLOPT_HTTP09_ALLOWED </info> Whether to allow HTTP/0.9
                  responses. Defaults to <info>false</info> as of libcurl 7.66.0; formerly it defaulted to <info>true</info>.
                  Available since PHP 7.3.15 and 7.4.3, respectively, if built against libcurl &gt;=
                  7.64.0  <info>CURLOPT_HTTPGET</info><info>true</info> to reset the HTTP request method to GET. Since GET is
                  the default, this is only necessary if the request method has been changed.
                  <info>CURLOPT_HTTPPROXYTUNNEL</info><info>true</info> to tunnel through a given HTTP proxy.
                  <info>CURLOPT_HTTP_CONTENT_DECODING</info><info>false</info> to get the raw HTTP response body.  Available
                  as of PHP 5.5.0 if built against libcurl &gt;= 7.16.2.
                  <info>CURLOPT_KEEP_SENDING_ON_ERROR</info><info>true</info> to keep sending the request body if the HTTP
                  code returned is  equal to or larger than 300. The default action would be to stop
                  sending and close the stream or connection. Suitable for manual NTLM
                  authentication. Most applications do not need this option.  Available as of PHP
                  7.3.0 if built against libcurl &gt;= 7.51.0. <info>CURLOPT_MUTE</info><info>true</info> to be completely
                  silent with regards to the cURL functions.  Removed in cURL 7.15.5 (You can use
                  CURLOPT_RETURNTRANSFER instead) <info>CURLOPT_NETRC</info><info>true</info> to scan the ~/.netrc file to
                  find a username and password for the remote site that a connection is being
                  established with.  <info>CURLOPT_NOBODY</info><info>true</info> to exclude the body from the output. Request
                  method is then set to HEAD. Changing this to <info>false</info> does not change it to GET.
                  <info>CURLOPT_NOPROGRESS</info><info>true</info> to disable the progress meter for cURL transfers.  PHP
                  automatically sets this option to <info>true</info>, this should only be changed for debugging
                  purposes.   <info>CURLOPT_NOSIGNAL</info><info>true</info> to ignore any cURL function that causes a signal
                  to be sent to the PHP process. This is turned on by default in multi-threaded
                  SAPIs so timeout options can still be used.  Added in cURL 7.10.
                  <info>CURLOPT_PATH_AS_IS</info><info>true</info> to not handle dot dot sequences.  Added in cURL 7.42.0.
                  Available since PHP 7.0.7. <info>CURLOPT_PIPEWAIT</info><info>true</info> to wait for
                  pipelining/multiplexing.  Added in cURL 7.43.0. Available since PHP 7.0.7.
                  <info>CURLOPT_POST</info><info>true</info> to do a regular HTTP POST. This POST is the normal
                  <return>application/x-www-form-urlencoded</return> kind, most commonly used by HTML forms.
                  <info>CURLOPT_PUT</info><info>true</info> to HTTP PUT a file. The file to PUT must be set with
                  <info>CURLOPT_INFILE</info> and <info>CURLOPT_INFILESIZE</info>.  <info>CURLOPT_RETURNTRANSFER</info><info>true</info> to return the
                  transfer as a string of the return value of <strong>curl_exec()</strong> instead of outputting it
                  directly.  <info>CURLOPT_SASL_IR</info><info>true</info> to enable sending the initial response in the first
                  packet.  Added in cURL 7.31.10. Available since PHP 7.0.7.
                  <info>CURLOPT_SSL_ENABLE_ALPN</info><info>false</info> to disable ALPN in the SSL handshake (if the SSL
                  backend libcurl is built to use supports it), which can be used to negotiate
                  http2.  Added in cURL 7.36.0. Available since PHP 7.0.7.
                  <info>CURLOPT_SSL_ENABLE_NPN</info><info>false</info> to disable NPN in the SSL handshake (if the SSL
                  backend libcurl is built to use supports it), which can be used to negotiate
                  http2.  Added in cURL 7.36.0. Available since PHP 7.0.7.
                  <info>CURLOPT_SSL_VERIFYPEER</info><info>false</info> to stop cURL from verifying the peer's certificate.
                  Alternate certificates to verify against can be specified with the <info>CURLOPT_CAINFO</info>
                  option or a certificate directory can be specified with the <info>CURLOPT_CAPATH</info> option.
                  <info>true</info> by default as of cURL 7.10. Default bundle installed as of cURL 7.10.
                  <info>CURLOPT_SSL_VERIFYSTATUS</info><info>true</info> to verify the certificate's status.  Added in cURL
                  7.41.0. Available since PHP 7.0.7. <info>CURLOPT_PROXY_SSL_VERIFYPEER</info><info>false</info> to stop cURL
                  from verifying the peer's certificate. Alternate certificates to verify against
                  can be specified with the <info>CURLOPT_CAINFO</info> option or a certificate directory can be
                  specified with the <info>CURLOPT_CAPATH</info> option. When set to false, the peer certificate
                  verification succeeds regardless. <info>true</info> by default. Available since PHP 7.3.0 and
                  libcurl &gt;= cURL 7.52.0. <info>CURLOPT_SUPPRESS_CONNECT_HEADERS</info><info>true</info> to suppress proxy
                  CONNECT response headers from the user callback functions  <info>CURLOPT_HEADERFUNCTION</info>
                  and <info>CURLOPT_WRITEFUNCTION</info>, when <info>CURLOPT_HTTPPROXYTUNNEL</info> is used and a CONNECT
                  request is made.  Added in cURL 7.54.0. Available since PHP 7.3.0.
                  <info>CURLOPT_TCP_FASTOPEN</info><info>true</info> to enable TCP Fast Open.  Added in cURL 7.49.0. Available
                  since PHP 7.0.7. <info>CURLOPT_TFTP_NO_OPTIONS</info><info>true</info> to not send TFTP options requests.
                  Added in cURL 7.48.0. Available since PHP 7.0.7. <info>CURLOPT_TRANSFERTEXT</info><info>true</info> to use
                  ASCII mode for FTP transfers. For LDAP, it retrieves data in plain text instead of
                  HTML. On Windows systems, it will not set <return>STDOUT</return> to binary mode.
                  <info>CURLOPT_UNRESTRICTED_AUTH</info><info>true</info> to keep sending the username and password when
                  following locations (using <info>CURLOPT_FOLLOWLOCATION</info>), even when the hostname has
                  changed.  <info>CURLOPT_UPLOAD</info><info>true</info> to prepare for an upload.  <info>CURLOPT_VERBOSE</info><info>true</info> to
                  output verbose information. Writes output to <return>STDERR</return>, or the file specified using
                  <info>CURLOPT_STDERR</info>.
                  
                  <info>true</info> to disable the progress meter for cURL transfers.  PHP automatically sets
                  this option to <info>true</info>, this should only be changed for debugging purposes.
                  
                  PHP automatically sets this option to <info>true</info>, this should only be changed for
                  debugging purposes.
                  
                  <strong>$value</strong> should be an <info>int</info> for the following values of the <strong>$option</strong> parameter:
                  OptionSet <strong>$value</strong> toNotes<info>CURLOPT_BUFFERSIZE</info> The size of the buffer to use for each
                  read. There is no guarantee this request will be fulfilled, however.  Added in
                  cURL 7.10. <info>CURLOPT_CLOSEPOLICY</info> One of the <info>CURLCLOSEPOLICY_*</info> values.  This option
                  is deprecated, as it was never implemented in cURL and never had any effect.
                  Removed in PHP 5.6.0. <info>CURLOPT_CONNECTTIMEOUT</info> The number of seconds to wait while
                  trying to connect. Use 0 to wait indefinitely.  <info>CURLOPT_CONNECTTIMEOUT_MS</info> The
                  number of milliseconds to wait while trying to connect. Use 0 to wait
                  indefinitely.  If libcurl is built to use the standard system name resolver, that
                  portion of the connect will still use full-second resolution for timeouts with a
                  minimum timeout allowed of one second.  Added in cURL 7.16.2. Available since PHP
                  5.2.3. <info>CURLOPT_DNS_CACHE_TIMEOUT</info> The number of seconds to keep DNS entries in
                  memory. This option is set to 120 (2 minutes) by default.
                  <info>CURLOPT_EXPECT_100_TIMEOUT_MS</info> The timeout for Expect: 100-continue responses in
                  milliseconds. Defaults to 1000 milliseconds.  Added in cURL 7.36.0. Available
                  since PHP 7.0.7. <info>CURLOPT_HAPPY_EYEBALLS_TIMEOUT_MS</info> Head start for ipv6 for the
                  happy eyeballs algorithm. Happy eyeballs attempts to connect to both IPv4 and IPv6
                  addresses for dual-stack hosts,  preferring IPv6 first for timeout milliseconds.
                  Defaults to CURL_HET_DEFAULT, which is currently 200 milliseconds.  Added in cURL
                  7.59.0. Available since PHP 7.3.0. <info>CURLOPT_FTPSSLAUTH</info> The FTP authentication
                  method (when is activated): <return>CURLFTPAUTH_SSL</return> (try SSL first), <return>CURLFTPAUTH_TLS</return> (try
                  TLS first), or <return>CURLFTPAUTH_DEFAULT</return> (let cURL decide).  Added in cURL 7.12.2.
                  <info>CURLOPT_HEADEROPT</info> How to deal with headers. One of the following constants:
                  <info>CURLHEADER_UNIFIED</info>: the headers specified in <info>CURLOPT_HTTPHEADER</info> will be used in
                  requests both to servers and proxies. With this option enabled,
                  <info>CURLOPT_PROXYHEADER</info> will not have any effect.  <info>CURLHEADER_SEPARATE</info>: makes
                  <info>CURLOPT_HTTPHEADER</info> headers only get sent to a server and not to a proxy. Proxy
                  headers must be set with <info>CURLOPT_PROXYHEADER</info> to get used. Note that if a
                  non-CONNECT request is sent to a proxy, libcurl will send both server headers and
                  proxy headers. When doing CONNECT, libcurl will send <info>CURLOPT_PROXYHEADER</info> headers
                  only to the proxy and then <info>CURLOPT_HTTPHEADER</info> headers only to the server.
                  Defaults to <info>CURLHEADER_SEPARATE</info> as of cURL 7.42.1, and <info>CURLHEADER_UNIFIED</info> before.
                  Added in cURL 7.37.0. Available since PHP 7.0.7.
                  <info>CURLOPT_HTTP_VERSION</info><info>CURL_HTTP_VERSION_NONE</info> (default, lets CURL decide which
                  version to use), <info>CURL_HTTP_VERSION_1_0</info> (forces HTTP/1.0), <info>CURL_HTTP_VERSION_1_1</info>
                  (forces HTTP/1.1), <info>CURL_HTTP_VERSION_2_0</info> (attempts HTTP 2), <info>CURL_HTTP_VERSION_2 </info>
                  (alias of <info>CURL_HTTP_VERSION_2_0</info>), <info>CURL_HTTP_VERSION_2TLS</info> (attempts HTTP 2 over TLS
                  (HTTPS) only) or <info>CURL_HTTP_VERSION_2_PRIOR_KNOWLEDGE</info> (issues non-TLS HTTP requests
                  using HTTP/2 without HTTP/1.1 Upgrade).  <info>CURLOPT_HTTPAUTH</info> The HTTP authentication
                  method(s) to use. The options are: <info>CURLAUTH_BASIC</info>, <info>CURLAUTH_DIGEST</info>,
                  <info>CURLAUTH_GSSNEGOTIATE</info>, <info>CURLAUTH_NTLM</info>, <info>CURLAUTH_ANY</info>, and <info>CURLAUTH_ANYSAFE</info>.  The
                  bitwise <return>|</return> (or) operator can be used to combine more than one method. If this is
                  done, cURL will poll the server to see what methods it supports and pick the best
                  one. <info>CURLAUTH_ANY</info> is an alias for <return>CURLAUTH_BASIC | CURLAUTH_DIGEST |
                  CURLAUTH_GSSNEGOTIATE | CURLAUTH_NTLM</return>. <info>CURLAUTH_ANYSAFE</info> is an alias for
                  <return>CURLAUTH_DIGEST | CURLAUTH_GSSNEGOTIATE | CURLAUTH_NTLM</return>.  <info>CURLOPT_INFILESIZE</info> The
                  expected size, in bytes, of the file when uploading a file to a remote site. Note
                  that using this option will not stop libcurl from sending more data, as exactly
                  what is sent depends on <info>CURLOPT_READFUNCTION</info>.  <info>CURLOPT_LOW_SPEED_LIMIT</info> The
                  transfer speed, in bytes per second, that the transfer should be below during the
                  count of <info>CURLOPT_LOW_SPEED_TIME</info> seconds before PHP considers the transfer too slow
                  and aborts.  <info>CURLOPT_LOW_SPEED_TIME</info> The number of seconds the transfer speed
                  should be below <info>CURLOPT_LOW_SPEED_LIMIT</info> before PHP considers the transfer too slow
                  and aborts.  <info>CURLOPT_MAXCONNECTS</info> The maximum amount of persistent connections that
                  are allowed. When the limit is reached, <info>CURLOPT_CLOSEPOLICY</info> is used to determine
                  which connection to close.  <info>CURLOPT_MAXREDIRS</info> The maximum amount of HTTP
                  redirections to follow. Use this option alongside <info>CURLOPT_FOLLOWLOCATION</info>.
                  <info>CURLOPT_PORT</info> An alternative port number to connect to.  <info>CURLOPT_POSTREDIR</info> A
                  bitmask of 1 (301 Moved Permanently), 2 (302 Found) and 4 (303 See Other) if the
                  HTTP POST method should be maintained when <info>CURLOPT_FOLLOWLOCATION</info> is set and a
                  specific type of redirect occurs.  Added in cURL 7.19.1. Available since PHP
                  5.3.2. <info>CURLOPT_PROTOCOLS</info> Bitmask of <info>CURLPROTO_*</info> values. If used, this bitmask
                  limits what protocols libcurl may use in the transfer. This allows you to have a
                  libcurl built to support a wide range of protocols but still limit specific
                  transfers to only be allowed to use a subset of them. By default libcurl will
                  accept all protocols it supports.  See also <info>CURLOPT_REDIR_PROTOCOLS</info>.  Valid
                  protocol options are:  <info>CURLPROTO_HTTP</info>, <info>CURLPROTO_HTTPS</info>, <info>CURLPROTO_FTP</info>,
                  <info>CURLPROTO_FTPS</info>, <info>CURLPROTO_SCP</info>, <info>CURLPROTO_SFTP</info>, <info>CURLPROTO_TELNET</info>, <info>CURLPROTO_LDAP</info>,
                  <info>CURLPROTO_LDAPS</info>, <info>CURLPROTO_DICT</info>, <info>CURLPROTO_FILE</info>, <info>CURLPROTO_TFTP</info>, <info>CURLPROTO_ALL</info>
                  Added in cURL 7.19.4. <info>CURLOPT_PROXYAUTH</info> The HTTP authentication method(s) to use
                  for the proxy connection. Use the same bitmasks as described in <info>CURLOPT_HTTPAUTH</info>.
                  For proxy authentication, only <info>CURLAUTH_BASIC</info> and <info>CURLAUTH_NTLM</info> are currently
                  supported.  Added in cURL 7.10.7. <info>CURLOPT_PROXYPORT</info> The port number of the proxy
                  to connect to. This port number can also be set in <info>CURLOPT_PROXY</info>.
                  <info>CURLOPT_PROXYTYPE</info> Either <info>CURLPROXY_HTTP</info> (default), <info>CURLPROXY_SOCKS4</info>,
                  <info>CURLPROXY_SOCKS5</info>, <info>CURLPROXY_SOCKS4A</info> or <info>CURLPROXY_SOCKS5_HOSTNAME</info>.  Added in cURL
                  7.10. <info>CURLOPT_REDIR_PROTOCOLS</info> Bitmask of <info>CURLPROTO_*</info> values. If used, this bitmask
                  limits what protocols libcurl may use in a transfer that it follows to in a
                  redirect when <info>CURLOPT_FOLLOWLOCATION</info> is enabled. This allows you to limit specific
                  transfers to only be allowed to use a subset of protocols in redirections. By
                  default libcurl will allow all protocols except for FILE and SCP. This is a
                  difference compared to pre-7.19.4 versions which unconditionally would follow to
                  all protocols supported.  See also <info>CURLOPT_PROTOCOLS</info> for protocol constant values.
                  Added in cURL 7.19.4. <info>CURLOPT_RESUME_FROM</info> The offset, in bytes, to resume a
                  transfer from.  <info>CURLOPT_SOCKS5_AUTH</info> The SOCKS5 authentication method(s) to use.
                  The options are: <info>CURLAUTH_BASIC</info>, <info>CURLAUTH_GSSAPI</info>, <info>CURLAUTH_NONE</info>.  The bitwise <return>|</return>
                  (or) operator can be used to combine more than one method. If this is done, cURL
                  will poll the server to see what methods it supports and pick the best one.
                  <info>CURLAUTH_BASIC</info> allows username/password authentication. <info>CURLAUTH_GSSAPI</info> allows
                  GSS-API authentication. <info>CURLAUTH_NONE</info> allows no authentication.  Defaults to
                  <return>CURLAUTH_BASIC|CURLAUTH_GSSAPI</return>. Set the actual username and password with the
                  <info>CURLOPT_PROXYUSERPWD</info> option.  Available as of 7.3.0 and curl &gt;= 7.55.0.
                  <info>CURLOPT_SSL_OPTIONS</info> Set SSL behavior options, which is a bitmask of any of the
                  following constants: <info>CURLSSLOPT_ALLOW_BEAST</info>: do not attempt to use any workarounds
                  for a security flaw in the SSL3 and TLS1.0 protocols.  <info>CURLSSLOPT_NO_REVOKE</info>:
                  disable certificate revocation checks for those SSL backends where such behavior
                  is present.   Added in cURL 7.25.0. Available since PHP 7.0.7.
                  <info>CURLOPT_SSL_VERIFYHOST</info><return>1</return> to check the existence of a common name in the SSL peer
                  certificate. <return>2</return> to check the existence of a common name and also verify that it
                  matches the hostname provided. <return>0</return> to not check the names. In production
                  environments the value of this option should be kept at <return>2</return> (default value).
                  Support for value <return>1</return> removed in cURL 7.28.1. <info>CURLOPT_SSLVERSION</info> One of
                  <info>CURL_SSLVERSION_DEFAULT</info> (0), <info>CURL_SSLVERSION_TLSv1</info> (1), <info>CURL_SSLVERSION_SSLv2</info> (2),
                  <info>CURL_SSLVERSION_SSLv3</info> (3), <info>CURL_SSLVERSION_TLSv1_0</info> (4), <info>CURL_SSLVERSION_TLSv1_1</info>
                  (5) or <info>CURL_SSLVERSION_TLSv1_2</info> (6). The maximum TLS version can be set by using
                  one of the <info>CURL_SSLVERSION_MAX_*</info> constants. It is also possible to OR one of the
                  <info>CURL_SSLVERSION_*</info> constants with one of the <info>CURL_SSLVERSION_MAX_*</info> constants.
                  <info>CURL_SSLVERSION_MAX_DEFAULT</info> (the maximum version supported by the library),
                  <info>CURL_SSLVERSION_MAX_TLSv1_0</info>, <info>CURL_SSLVERSION_MAX_TLSv1_1</info>,
                  <info>CURL_SSLVERSION_MAX_TLSv1_2</info>, or <info>CURL_SSLVERSION_MAX_TLSv1_3</info>.  Your best bet is to
                  not set this and let it use the default. Setting it to 2 or 3 is very dangerous
                  given the known vulnerabilities in SSLv2 and SSLv3.   <info>CURLOPT_PROXY_SSL_OPTIONS</info>
                  Set proxy SSL behavior options, which is a bitmask of any of the following
                  constants: <info>CURLSSLOPT_ALLOW_BEAST</info>: do not attempt to use any workarounds for a
                  security flaw in the SSL3 and TLS1.0 protocols.  <info>CURLSSLOPT_NO_REVOKE</info>: disable
                  certificate revocation checks for those SSL backends where such behavior is
                  present. (curl &gt;= 7.44.0)  <info>CURLSSLOPT_NO_PARTIALCHAIN</info>: do not accept "partial"
                  certificate chains, which it otherwise does by default. (curl &gt;= 7.68.0)
                  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0.
                  <info>CURLOPT_PROXY_SSL_VERIFYHOST</info> Set to <return>2</return> to verify in the HTTPS proxy's certificate
                  name fields against the proxy name.  When set to <return>0</return> the connection succeeds
                  regardless of the names used in the certificate.  Use that ability with caution!
                  <return>1</return> treated as a debug option in curl 7.28.0 and earlier.  From curl 7.28.1 to
                  7.65.3 <info>CURLE_BAD_FUNCTION_ARGUMENT</info> is returned. From curl 7.66.0 onwards <return>1</return> and <return>2</return>
                  is treated as the same value. In production environments the value of this option
                  should be kept at <return>2</return> (default value).  Available since PHP 7.3.0 and libcurl &gt;=
                  cURL 7.52.0. <info>CURLOPT_PROXY_SSLVERSION</info> One of <info>CURL_SSLVERSION_DEFAULT</info>,
                  <info>CURL_SSLVERSION_TLSv1</info>, <info>CURL_SSLVERSION_TLSv1_0</info>, <info>CURL_SSLVERSION_TLSv1_1</info>,
                  <info>CURL_SSLVERSION_TLSv1_2</info>, <info>CURL_SSLVERSION_TLSv1_3</info>, <info>CURL_SSLVERSION_MAX_DEFAULT</info>,
                  <info>CURL_SSLVERSION_MAX_TLSv1_0</info>, <info>CURL_SSLVERSION_MAX_TLSv1_1</info>,
                  <info>CURL_SSLVERSION_MAX_TLSv1_2</info>, <info>CURL_SSLVERSION_MAX_TLSv1_3</info> or <info>CURL_SSLVERSION_SSLv3</info>.
                  Your best bet is to not set this and let it use the default
                  <info>CURL_SSLVERSION_DEFAULT</info> which will attempt to figure out the remote SSL protocol
                  version.   Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0.
                  <info>CURLOPT_STREAM_WEIGHT</info> Set the numerical stream weight (a number between 1 and
                  256).  Added in cURL 7.46.0. Available since PHP 7.0.7. <info>CURLOPT_TCP_KEEPALIVE</info> If
                  set to <return>1</return>, TCP keepalive probes will be sent. The delay and frequency of these
                  probes can be controlled by the <info>CURLOPT_TCP_KEEPIDLE</info> and <info>CURLOPT_TCP_KEEPINTVL</info>
                  options, provided the operating system supports them. If set to <return>0</return> (default)
                  keepalive probes are disabled.  Added in cURL 7.25.0. Available since PHP 5.5.0.
                  <info>CURLOPT_TCP_KEEPIDLE</info> Sets the delay, in seconds, that the operating system will
                  wait while the connection is idle before sending keepalive probes, if
                  <info>CURLOPT_TCP_KEEPALIVE</info> is enabled. Not all operating systems support this option.
                  The default is <return>60</return>.  Added in cURL 7.25.0. Available since PHP 5.5.0.
                  <info>CURLOPT_TCP_KEEPINTVL</info> Sets the interval, in seconds, that the operating system
                  will wait between sending keepalive probes, if <info>CURLOPT_TCP_KEEPALIVE</info> is enabled.
                  Not all operating systems support this option. The default is <return>60</return>.  Added in cURL
                  7.25.0. Available since PHP 5.5.0. <info>CURLOPT_TIMECONDITION</info> How <info>CURLOPT_TIMEVALUE</info> is
                  treated. Use <info>CURL_TIMECOND_IFMODSINCE</info> to return the page only if it has been
                  modified since the time specified in <info>CURLOPT_TIMEVALUE</info>. If it hasn't been
                  modified, a <return>"304 Not Modified"</return> header will be returned assuming <info>CURLOPT_HEADER</info> is
                  <info>true</info>. Use <info>CURL_TIMECOND_IFUNMODSINCE</info> for the reverse effect.
                  <info>CURL_TIMECOND_IFMODSINCE</info> is the default.  <info>CURLOPT_TIMEOUT</info> The maximum number of
                  seconds to allow cURL functions to execute.  <info>CURLOPT_TIMEOUT_MS</info> The maximum number
                  of milliseconds to allow cURL functions to execute.  If libcurl is built to use
                  the standard system name resolver, that portion of the connect will still use
                  full-second resolution for timeouts with a minimum timeout allowed of one second.
                  Added in cURL 7.16.2. Available since PHP 5.2.3. <info>CURLOPT_TIMEVALUE</info> The time in
                  seconds since January 1st, 1970. The time will be used by <info>CURLOPT_TIMECONDITION</info>.
                  By default, <info>CURL_TIMECOND_IFMODSINCE</info> is used.  <info>CURLOPT_TIMEVALUE_LARGE</info> The time in
                  seconds since January 1st, 1970. The time will be used by <info>CURLOPT_TIMECONDITION</info>.
                  Defaults to zero. The difference between this option and <info>CURLOPT_TIMEVALUE</info> is the
                  type of the argument. On systems where 'long' is only 32 bit wide,  this option
                  has to be used to set dates beyond the year 2038.  Added in cURL 7.59.0. Available
                  since PHP 7.3.0. <info>CURLOPT_MAX_RECV_SPEED_LARGE</info> If a download exceeds this speed
                  (counted in bytes per second) on cumulative average during the transfer, the
                  transfer will pause to keep the average rate less than or equal to the parameter
                  value. Defaults to unlimited speed.  Added in cURL 7.15.5. Available since PHP
                  5.4.0. <info>CURLOPT_MAX_SEND_SPEED_LARGE</info> If an upload exceeds this speed (counted in
                  bytes per second) on cumulative average during the transfer, the transfer will
                  pause to keep the average rate less than or equal to the parameter value. Defaults
                  to unlimited speed.  Added in cURL 7.15.5. Available since PHP 5.4.0.
                  <info>CURLOPT_SSH_AUTH_TYPES</info> A bitmask consisting of one or more of
                  <info>CURLSSH_AUTH_PUBLICKEY</info>,  <info>CURLSSH_AUTH_PASSWORD</info>,  <info>CURLSSH_AUTH_HOST</info>,
                  <info>CURLSSH_AUTH_KEYBOARD</info>. Set to  <info>CURLSSH_AUTH_ANY</info> to let libcurl pick one.  Added in
                  cURL 7.16.1.  <info>CURLOPT_IPRESOLVE</info> Allows an application to select what kind of IP
                  addresses to use when resolving host names. This is only interesting when using
                  host names that resolve addresses using more than one version of IP, possible
                  values are <info>CURL_IPRESOLVE_WHATEVER</info>,  <info>CURL_IPRESOLVE_V4</info>,  <info>CURL_IPRESOLVE_V6</info>, by
                  default <info>CURL_IPRESOLVE_WHATEVER</info>.  Added in cURL 7.10.8. <info>CURLOPT_FTP_FILEMETHOD</info>
                  Tell curl which method to use to reach a file on a FTP(S) server. Possible values
                  are <info>CURLFTPMETHOD_MULTICWD</info>,  <info>CURLFTPMETHOD_NOCWD</info> and   <info>CURLFTPMETHOD_SINGLECWD</info>.
                  Added in cURL 7.15.1. Available since PHP 5.3.0.
                  
                  This option is deprecated, as it was never implemented in cURL and never had any
                  effect.
                  
                  <info>CURLHEADER_UNIFIED</info>: the headers specified in <info>CURLOPT_HTTPHEADER</info> will be used in
                  requests both to servers and proxies. With this option enabled,
                  <info>CURLOPT_PROXYHEADER</info> will not have any effect.
                  
                  <info>CURLHEADER_SEPARATE</info>: makes <info>CURLOPT_HTTPHEADER</info> headers only get sent to a server
                  and not to a proxy. Proxy headers must be set with <info>CURLOPT_PROXYHEADER</info> to get
                  used. Note that if a non-CONNECT request is sent to a proxy, libcurl will send
                  both server headers and proxy headers. When doing CONNECT, libcurl will send
                  <info>CURLOPT_PROXYHEADER</info> headers only to the proxy and then <info>CURLOPT_HTTPHEADER</info> headers
                  only to the server.
                  
                  Defaults to <info>CURLHEADER_SEPARATE</info> as of cURL 7.42.1, and <info>CURLHEADER_UNIFIED</info> before.
                  
                  The HTTP authentication method(s) to use. The options are: <info>CURLAUTH_BASIC</info>,
                  <info>CURLAUTH_DIGEST</info>, <info>CURLAUTH_GSSNEGOTIATE</info>, <info>CURLAUTH_NTLM</info>, <info>CURLAUTH_ANY</info>, and
                  <info>CURLAUTH_ANYSAFE</info>.
                  
                  The bitwise <return>|</return> (or) operator can be used to combine more than one method. If this
                  is done, cURL will poll the server to see what methods it supports and pick the
                  best one.
                  
                  <info>CURLAUTH_ANY</info> is an alias for <return>CURLAUTH_BASIC | CURLAUTH_DIGEST |
                  CURLAUTH_GSSNEGOTIATE | CURLAUTH_NTLM</return>.
                  
                  <info>CURLAUTH_ANYSAFE</info> is an alias for <return>CURLAUTH_DIGEST | CURLAUTH_GSSNEGOTIATE |
                  CURLAUTH_NTLM</return>.
                  
                  Bitmask of <info>CURLPROTO_*</info> values. If used, this bitmask  limits what protocols
                  libcurl may use in the transfer. This allows you to have a libcurl built to
                  support a wide range of protocols but still limit specific transfers to only be
                  allowed to use a subset of them. By default libcurl will accept all protocols it
                  supports.  See also <info>CURLOPT_REDIR_PROTOCOLS</info>.
                  
                  Valid protocol options are:  <info>CURLPROTO_HTTP</info>, <info>CURLPROTO_HTTPS</info>, <info>CURLPROTO_FTP</info>,
                  <info>CURLPROTO_FTPS</info>, <info>CURLPROTO_SCP</info>, <info>CURLPROTO_SFTP</info>, <info>CURLPROTO_TELNET</info>, <info>CURLPROTO_LDAP</info>,
                  <info>CURLPROTO_LDAPS</info>, <info>CURLPROTO_DICT</info>, <info>CURLPROTO_FILE</info>, <info>CURLPROTO_TFTP</info>, <info>CURLPROTO_ALL</info>
                  
                  The SOCKS5 authentication method(s) to use. The options are: <info>CURLAUTH_BASIC</info>,
                  <info>CURLAUTH_GSSAPI</info>, <info>CURLAUTH_NONE</info>.
                  
                  The bitwise <return>|</return> (or) operator can be used to combine more than one method. If this
                  is done, cURL will poll the server to see what methods it supports and pick the
                  best one.
                  
                  <info>CURLAUTH_BASIC</info> allows username/password authentication.
                  
                  <info>CURLAUTH_GSSAPI</info> allows GSS-API authentication.
                  
                  <info>CURLAUTH_NONE</info> allows no authentication.
                  
                  Defaults to <return>CURLAUTH_BASIC|CURLAUTH_GSSAPI</return>. Set the actual username and password
                  with the <info>CURLOPT_PROXYUSERPWD</info> option.
                  
                  <info>CURLSSLOPT_ALLOW_BEAST</info>: do not attempt to use any workarounds for a security flaw
                  in the SSL3 and TLS1.0 protocols.
                  
                  <info>CURLSSLOPT_NO_REVOKE</info>: disable certificate revocation checks for those SSL backends
                  where such behavior is present.
                  
                  Your best bet is to not set this and let it use the default. Setting it to 2 or 3
                  is very dangerous given the known vulnerabilities in SSLv2 and SSLv3.
                  
                  <info>CURLSSLOPT_ALLOW_BEAST</info>: do not attempt to use any workarounds for a security flaw
                  in the SSL3 and TLS1.0 protocols.
                  
                  <info>CURLSSLOPT_NO_REVOKE</info>: disable certificate revocation checks for those SSL backends
                  where such behavior is present. (curl &gt;= 7.44.0)
                  
                  <info>CURLSSLOPT_NO_PARTIALCHAIN</info>: do not accept "partial"  certificate chains, which it
                  otherwise does by default. (curl &gt;= 7.68.0)
                  
                  Your best bet is to not set this and let it use the default
                  <info>CURL_SSLVERSION_DEFAULT</info> which will attempt to figure out the remote SSL protocol
                  version.
                  
                  <strong>$value</strong> should be a <info>string</info> for the following values of the <strong>$option</strong> parameter:
                  OptionSet <strong>$value</strong> toNotes<info>CURLOPT_ABSTRACT_UNIX_SOCKET</info> Enables the use of an
                  abstract Unix domain socket instead of  establishing a TCP connection to a host
                  and sets the path to the given <info>string</info>. This option shares the same semantics as
                  <info>CURLOPT_UNIX_SOCKET_PATH</info>. These two options share the same storage and therefore
                  only one of them can be set per handle.   Available since PHP 7.3.0 and cURL
                  7.53.0 <info>CURLOPT_CAINFO</info> The name of a file holding one or more certificates to
                  verify the peer with. This only makes sense when used in combination with
                  <info>CURLOPT_SSL_VERIFYPEER</info>.  Might require an absolute path. <info>CURLOPT_CAPATH</info> A
                  directory that holds multiple CA certificates. Use this option alongside
                  <info>CURLOPT_SSL_VERIFYPEER</info>.  <info>CURLOPT_COOKIE</info> The contents of the <return>"Cookie: "</return> header to
                  be used in the HTTP request. Note that multiple cookies are separated with a
                  semicolon followed by a space (e.g., "<return>fruit=apple; colour=red</return>")
                  <info>CURLOPT_COOKIEFILE</info> The name of the file containing the cookie data. The cookie
                  file can be in Netscape format, or just plain HTTP-style headers dumped into a
                  file. If the name is an empty string, no cookies are loaded, but cookie handling
                  is still enabled.  <info>CURLOPT_COOKIEJAR</info> The name of a file to save all internal
                  cookies to when the handle is closed,  e.g. after a call to curl_close.
                  <info>CURLOPT_COOKIELIST</info> A cookie string (i.e. a single line in Netscape/Mozilla format,
                  or a regular HTTP-style Set-Cookie header) adds that single cookie to the internal
                  cookie store. <return>"ALL"</return> erases all cookies held in memory. <return>"SESS"</return> erases all session
                  cookies held in memory. <return>"FLUSH"</return> writes all known cookies to the file specified by
                  <info>CURLOPT_COOKIEJAR</info>. <return>"RELOAD"</return> loads all cookies from the files specified by
                  <info>CURLOPT_COOKIEFILE</info>.  Available since PHP 5.5.0 and cURL 7.14.1.
                  <info>CURLOPT_CUSTOMREQUEST</info> A custom request method to use instead of <return>"GET"</return> or <return>"HEAD"</return>
                  when doing a HTTP request. This is useful for doing <return>"DELETE"</return> or other, more
                  obscure HTTP requests. Valid values are things like <return>"GET"</return>, <return>"POST"</return>, <return>"CONNECT"</return> and
                  so on; i.e. Do not enter a whole HTTP request line here. For instance, entering
                  <return>"GET /index.html HTTP/1.0\r\n\r\n"</return> would be incorrect.  Don't do this without
                  making sure the server supports the custom request method first.
                  <info>CURLOPT_DEFAULT_PROTOCOL</info> The default protocol to use if the URL is missing a
                  scheme name.  Added in cURL 7.45.0. Available since PHP 7.0.7.
                  <info>CURLOPT_DNS_INTERFACE</info> Set the name of the network interface that the DNS resolver
                  should bind to. This must be an interface name (not an address).  Added in cURL
                  7.33.0. Available since PHP 7.0.7. <info>CURLOPT_DNS_LOCAL_IP4</info> Set the local IPv4
                  address that the resolver should bind to. The argument should contain a single
                  numerical IPv4 address as a string.  Added in cURL 7.33.0. Available since PHP
                  7.0.7. <info>CURLOPT_DNS_LOCAL_IP6</info> Set the local IPv6 address that the resolver should
                  bind to. The argument should contain a single numerical IPv6 address as a string.
                  Added in cURL 7.33.0. Available since PHP 7.0.7. <info>CURLOPT_EGDSOCKET</info> Like
                  <info>CURLOPT_RANDOM_FILE</info>, except a filename to an Entropy Gathering Daemon socket.
                  <info>CURLOPT_ENCODING</info> The contents of the <return>"Accept-Encoding: "</return> header. This enables
                  decoding of the response. Supported encodings are <return>"identity"</return>, <return>"deflate"</return>, and
                  <return>"gzip"</return>. If an empty string, <return>""</return>, is set, a header containing all supported encoding
                  types is sent.  Added in cURL 7.10. <info>CURLOPT_FTPPORT</info> The value which will be used
                  to get the IP address to use for the FTP "PORT" instruction. The "PORT"
                  instruction tells the remote server to connect to our specified IP address.  The
                  string may be a plain IP address, a hostname, a network interface name (under
                  Unix), or just a plain '-' to use the systems default IP address.
                  <info>CURLOPT_INTERFACE</info> The name of the outgoing network interface to use. This can be
                  an interface name, an IP address or a host name.  <info>CURLOPT_KEYPASSWD</info> The password
                  required to use the <info>CURLOPT_SSLKEY</info>  or <info>CURLOPT_SSH_PRIVATE_KEYFILE</info> private key.
                  Added in cURL 7.16.1.  <info>CURLOPT_KRB4LEVEL</info> The KRB4 (Kerberos 4) security level. Any
                  of the following values (in order from least to most powerful) are valid: <return>"clear"</return>,
                  <return>"safe"</return>, <return>"confidential"</return>, <return>"private".</return>. If the string does not match one of these,
                  <return>"private"</return> is used. Setting this option to <info>null</info> will disable KRB4 security.
                  Currently KRB4 security only works with FTP transactions.  <info>CURLOPT_LOGIN_OPTIONS</info>
                  Can be used to set protocol specific login options, such as the preferred
                  authentication mechanism via "AUTH=NTLM" or "AUTH=*", and should be used in
                  conjunction with the <info>CURLOPT_USERNAME</info> option.  Added in cURL 7.34.0. Available
                  since PHP 7.0.7. <info>CURLOPT_PINNEDPUBLICKEY</info> Set the pinned public key. The string can
                  be the file name of your pinned public key. The file format expected is "PEM" or
                  "DER". The string can also be any number of base64 encoded sha256 hashes preceded
                  by "sha256//" and separated by ";".  Added in cURL 7.39.0. Available since PHP
                  7.0.7. <info>CURLOPT_POSTFIELDS</info> The full data to post in a HTTP "POST" operation. This
                  parameter can either be passed as a urlencoded string like
                  '<return>para1=val1&para2=val2&...</return>'  or as an array with the field name as key and field
                  data as value. If <strong>$value</strong> is an array, the <return>Content-Type</return> header will be set to
                  <return>multipart/form-data</return>.  Files can be sent using <class>CURLFile</class>, in which case <strong>$value</strong> must
                  be an array.  <info>CURLOPT_PRIVATE</info> Any data that should be associated with this cURL
                  handle. This data can subsequently be retrieved with the <info>CURLINFO_PRIVATE</info> option
                  of <strong>curl_getinfo()</strong>. cURL does nothing with this data. When using a cURL multi
                  handle, this private data is typically a unique key to identify a standard cURL
                  handle.  Added in cURL 7.10.3.  <info>CURLOPT_PRE_PROXY</info> Set a <info>string</info> holding the host
                  name or dotted numerical  IP address to be used as the preproxy that curl connects
                  to before  it connects to the HTTP(S) proxy specified in the  <info>CURLOPT_PROXY</info> option
                  for the upcoming request. The preproxy can only be a SOCKS proxy and it should be
                  prefixed with <return>[scheme]://</return> to specify which kind of socks is used. A numerical IPv6
                  address must be written within [brackets]. Setting the preproxy to an empty string
                  explicitly disables the use of a preproxy.  To specify port number in this string,
                  append <return>:[port]</return> to the end of the host name. The proxy's port number may optionally
                  be  specified with the separate option <info>CURLOPT_PROXYPORT</info>.  Defaults to using port
                  1080 for proxies if a port is not specified.  Available since PHP 7.3.0 and
                  libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXY</info> The HTTP proxy to tunnel requests
                  through.  <info>CURLOPT_PROXY_SERVICE_NAME</info> The proxy authentication service name.  Added
                  in cURL 7.34.0. Available since PHP 7.0.7. <info>CURLOPT_PROXY_CAINFO</info> The path to proxy
                  Certificate Authority (CA) bundle. Set the path as a  <info>string</info> naming a file holding
                  one or more certificates to  verify the HTTPS proxy with. This option is for
                  connecting to an HTTPS proxy, not an HTTPS server. Defaults set to the system path
                  where libcurl's cacert bundle is assumed  to be stored.  Available since PHP 7.3.0
                  and libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXY_CAPATH</info> The directory holding multiple
                  CA certificates to verify the HTTPS proxy with.  Available since PHP 7.3.0 and
                  libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXY_CRLFILE</info> Set the file name with the
                  concatenation of CRL (Certificate Revocation List)  in PEM format to use in the
                  certificate validation that occurs during  the SSL exchange.  Available since PHP
                  7.3.0 and libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXY_KEYPASSWD</info> Set the string be
                  used as the password required to use the  <info>CURLOPT_PROXY_SSLKEY</info> private key. You
                  never needed a  passphrase to load a certificate but you need one to load your
                  private key. This option is for connecting to an HTTPS proxy, not an HTTPS server.
                  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0.
                  <info>CURLOPT_PROXY_PINNEDPUBLICKEY</info> Set the pinned public key for HTTPS proxy. The
                  string can be the file name  of your pinned public key. The file format expected
                  is "PEM" or "DER".  The string can also be any number of base64 encoded sha256
                  hashes preceded by  "sha256//" and separated by ";"  Available since PHP 7.3.0 and
                  libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXY_SSLCERT</info> The file name of your client
                  certificate used to connect to the HTTPS proxy.  The default format is "P12" on
                  Secure Transport and "PEM" on other engines,  and can be changed with
                  <info>CURLOPT_PROXY_SSLCERTTYPE</info>. With NSS or Secure Transport, this can also be the
                  nickname of the certificate  you wish to authenticate with as it is named in the
                  security database.  If you want to use a file from the current directory, please
                  precede it with  "./" prefix, in order to avoid confusion with a nickname.
                  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXY_SSLCERTTYPE</info>
                  The format of your client certificate used when connecting to an HTTPS proxy.
                  Supported formats are "PEM" and "DER", except with Secure Transport.  OpenSSL
                  (versions 0.9.3 and later) and Secure Transport  (on iOS 5 or later, or OS X 10.7
                  or later) also support "P12" for  PKCS#12-encoded files. Defaults to "PEM".
                  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0.
                  <info>CURLOPT_PROXY_SSL_CIPHER_LIST</info> The list of ciphers to use for the connection to the
                  HTTPS proxy.  The list must be syntactically correct, it consists of one or more
                  cipher  strings separated by colons. Commas or spaces are also acceptable
                  separators  but colons are normally used, !, - and + can be used as operators.
                  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0.
                  <info>CURLOPT_PROXY_TLS13_CIPHERS</info> The list of cipher suites to use for the TLS 1.3
                  connection to a proxy. The list must be syntactically correct, it consists of one
                  or more  cipher suite strings separated by colons. This option is currently used
                  only when curl is built to use OpenSSL 1.1.1 or later.  If you are using a
                  different SSL backend you can try setting  TLS 1.3 cipher suites by using the
                  <info>CURLOPT_PROXY_SSL_CIPHER_LIST</info> option.  Available since PHP 7.3.0 and libcurl &gt;=
                  cURL 7.61.0. Available when built with OpenSSL &gt;= 1.1.1. <info>CURLOPT_PROXY_SSLKEY</info>
                  The file name of your private key used for connecting to the HTTPS proxy.  The
                  default format is "PEM" and can be changed with  <info>CURLOPT_PROXY_SSLKEYTYPE</info>.  (iOS
                  and Mac OS X only) This option is ignored if curl was built against Secure
                  Transport.  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0. Available if
                  built TLS enabled. <info>CURLOPT_PROXY_SSLKEYTYPE</info> The format of your private key.
                  Supported formats are "PEM", "DER" and "ENG".  Available since PHP 7.3.0 and
                  libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXY_TLSAUTH_PASSWORD</info> The password to use for
                  the TLS authentication method specified with the  <info>CURLOPT_PROXY_TLSAUTH_TYPE</info>
                  option. Requires that the  <info>CURLOPT_PROXY_TLSAUTH_USERNAME</info> option to also be set.
                  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0.
                  <info>CURLOPT_PROXY_TLSAUTH_TYPE</info> The method of the TLS authentication used for the HTTPS
                  connection. Supported method is "SRP".  Secure Remote Password (SRP)
                  authentication for TLS provides mutual authentication  if both sides have a shared
                  secret. To use TLS-SRP, you must also set the  <info>CURLOPT_PROXY_TLSAUTH_USERNAME</info> and
                  <info>CURLOPT_PROXY_TLSAUTH_PASSWORD</info> options.   Available since PHP 7.3.0 and libcurl
                  &gt;= cURL 7.52.0. <info>CURLOPT_PROXY_TLSAUTH_USERNAME</info> Tusername to use for the HTTPS
                  proxy TLS authentication method specified with the  <info>CURLOPT_PROXY_TLSAUTH_TYPE</info>
                  option. Requires that the <info>CURLOPT_PROXY_TLSAUTH_PASSWORD</info> option to also be set.
                  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.52.0. <info>CURLOPT_PROXYUSERPWD</info> A
                  username and password formatted as <return>"[username]:[password]"</return> to use for the
                  connection to the proxy.  <info>CURLOPT_RANDOM_FILE</info> A filename to be used to seed the
                  random number generator for SSL.  <info>CURLOPT_RANGE</info> Range(s) of data to retrieve in
                  the format <return>"X-Y"</return> where X or Y are optional. HTTP transfers also support several
                  intervals, separated with commas in the format <return>"X-Y,N-M"</return>.  <info>CURLOPT_REFERER</info> The
                  contents of the <return>"Referer: "</return> header to be used in a HTTP request.
                  <info>CURLOPT_SERVICE_NAME</info> The authentication service name.  Added in cURL 7.43.0.
                  Available since PHP 7.0.7. <info>CURLOPT_SSH_HOST_PUBLIC_KEY_MD5</info> A string containing 32
                  hexadecimal digits. The string should be the  MD5 checksum of the remote host's
                  public key, and libcurl will reject  the connection to the host unless the md5sums
                  match.  This option is only for SCP and SFTP transfers.  Added in cURL 7.17.1.
                  <info>CURLOPT_SSH_PUBLIC_KEYFILE</info> The file name for your public key. If not used, libcurl
                  defaults to  $HOME/.ssh/id_dsa.pub if the HOME environment variable is set,  and
                  just "id_dsa.pub" in the current directory if HOME is not set.  Added in cURL
                  7.16.1.  <info>CURLOPT_SSH_PRIVATE_KEYFILE</info> The file name for your private key. If not
                  used, libcurl defaults to  $HOME/.ssh/id_dsa if the HOME environment variable is
                  set,  and just "id_dsa" in the current directory if HOME is not set.  If the file
                  is password-protected, set the password with  <info>CURLOPT_KEYPASSWD</info>.  Added in cURL
                  7.16.1.  <info>CURLOPT_SSL_CIPHER_LIST</info> A list of ciphers to use for SSL. For example,
                  <return>RC4-SHA</return> and <return>TLSv1</return> are valid cipher lists.  <info>CURLOPT_SSLCERT</info> The name of a file
                  containing a PEM formatted certificate.  <info>CURLOPT_SSLCERTPASSWD</info> The password
                  required to use the <info>CURLOPT_SSLCERT</info> certificate.  <info>CURLOPT_SSLCERTTYPE</info> The format
                  of the certificate. Supported formats are <return>"PEM"</return> (default), <return>"DER"</return>, and <return>"ENG"</return>. As of
                  OpenSSL 0.9.3, <return>"P12"</return> (for PKCS#12-encoded files) is also supported.  Added in cURL
                  7.9.3. <info>CURLOPT_SSLENGINE</info> The identifier for the crypto engine of the private SSL
                  key specified in <info>CURLOPT_SSLKEY</info>.  <info>CURLOPT_SSLENGINE_DEFAULT</info> The identifier for the
                  crypto engine used for asymmetric crypto operations.  <info>CURLOPT_SSLKEY</info> The name of a
                  file containing a private SSL key.  <info>CURLOPT_SSLKEYPASSWD</info> The secret password
                  needed to use the private SSL key specified in <info>CURLOPT_SSLKEY</info>.  Since this option
                  contains a sensitive password, remember to keep the PHP script it is contained
                  within safe.   <info>CURLOPT_SSLKEYTYPE</info> The key type of the private SSL key specified in
                  <info>CURLOPT_SSLKEY</info>. Supported key types are <return>"PEM"</return> (default), <return>"DER"</return>, and <return>"ENG"</return>.
                  <info>CURLOPT_TLS13_CIPHERS</info> The list of cipher suites to use for the TLS 1.3 connection.
                  The list must be  syntactically correct, it consists of one or more cipher suite
                  strings separated by colons.  This option is currently used only when curl is
                  built to use OpenSSL 1.1.1 or later.  If you are using a different SSL backend you
                  can try setting  TLS 1.3 cipher suites by using the <info>CURLOPT_SSL_CIPHER_LIST</info>
                  option.  Available since PHP 7.3.0 and libcurl &gt;= cURL 7.61.0. Available when
                  built with OpenSSL &gt;= 1.1.1. <info>CURLOPT_UNIX_SOCKET_PATH</info> Enables the use of Unix
                  domain sockets as connection endpoint and sets the path to the given <info>string</info>.
                  Added in cURL 7.40.0. Available since PHP 7.0.7. <info>CURLOPT_URL</info> The URL to fetch.
                  This can also be set when initializing a session with <strong>curl_init()</strong>.
                  <info>CURLOPT_USERAGENT</info> The contents of the <return>"User-Agent: "</return> header to be used in a HTTP
                  request.  <info>CURLOPT_USERNAME</info> The user name to use in authentication.  Added in cURL
                  7.19.1. Available since PHP 5.5.0. <info>CURLOPT_USERPWD</info> A username and password
                  formatted as <return>"[username]:[password]"</return> to use for the connection.
                  <info>CURLOPT_XOAUTH2_BEARER</info> Specifies the OAuth 2.0 access token.  Added in cURL
                  7.33.0. Available since PHP 7.0.7.
                  
                  A custom request method to use instead of <return>"GET"</return> or <return>"HEAD"</return> when doing a HTTP
                  request. This is useful for doing <return>"DELETE"</return> or other, more obscure HTTP requests.
                  Valid values are things like <return>"GET"</return>, <return>"POST"</return>, <return>"CONNECT"</return> and so on; i.e. Do not enter
                  a whole HTTP request line here. For instance, entering <return>"GET /index.html
                  HTTP/1.0\r\n\r\n"</return> would be incorrect.  Don't do this without making sure the
                  server supports the custom request method first.
                  
                  Don't do this without making sure the server supports the custom request method
                  first.
                  
                  The default protocol to use if the URL is missing a scheme name.
                  
                  Set the name of the network interface that the DNS resolver should bind to. This
                  must be an interface name (not an address).
                  
                  Set the local IPv4 address that the resolver should bind to. The argument should
                  contain a single numerical IPv4 address as a string.
                  
                  Set the local IPv6 address that the resolver should bind to. The argument should
                  contain a single numerical IPv6 address as a string.
                  
                  The full data to post in a HTTP "POST" operation. This parameter can either be
                  passed as a urlencoded string like '<return>para1=val1&para2=val2&...</return>'  or as an array
                  with the field name as key and field data as value. If <strong>$value</strong> is an array, the
                  <return>Content-Type</return> header will be set to <return>multipart/form-data</return>.
                  
                  Files can be sent using <class>CURLFile</class>, in which case <strong>$value</strong> must be an array.
                  
                  Secure Remote Password (SRP) authentication for TLS provides mutual authentication
                  if both sides have a shared secret. To use TLS-SRP, you must also set the
                  <info>CURLOPT_PROXY_TLSAUTH_USERNAME</info> and  <info>CURLOPT_PROXY_TLSAUTH_PASSWORD</info> options.
                  
                  The secret password needed to use the private SSL key specified in <info>CURLOPT_SSLKEY</info>.
                  Since this option contains a sensitive password, remember to keep the PHP script
                  it is contained within safe.
                  
                  Since this option contains a sensitive password, remember to keep the PHP script
                  it is contained within safe.
                  
                  <strong>$value</strong> should be an array for the following values of the <strong>$option</strong> parameter:
                  OptionSet <strong>$value</strong> toNotes<info>CURLOPT_CONNECT_TO</info> Connect to a specific host and port
                  instead of the URL's host and port. Accepts an array of strings with the format
                  <return>HOST:PORT:CONNECT-TO-HOST:CONNECT-TO-PORT</return>.  Added in cURL 7.49.0. Available since
                  PHP 7.0.7. <info>CURLOPT_HTTP200ALIASES</info> An array of HTTP 200 responses that will be
                  treated as valid responses and not as errors.  Added in cURL 7.10.3.
                  <info>CURLOPT_HTTPHEADER</info> An array of HTTP header fields to set, in the format
                  array('Content-type: text/plain', 'Content-length: 100')   <info>CURLOPT_POSTQUOTE</info> An
                  array of FTP commands to execute on the server after the FTP request has been
                  performed.  <info>CURLOPT_PROXYHEADER</info> An array of custom HTTP headers to pass to
                  proxies.  Added in cURL 7.37.0. Available since PHP 7.0.7. <info>CURLOPT_QUOTE</info> An array
                  of FTP commands to execute on the server prior to the FTP request.
                  <info>CURLOPT_RESOLVE</info> Provide a custom address for a specific host and port pair. An
                  array of hostname, port, and IP address strings, each element separated by a
                  colon. In the format:  array("example.com:80:127.0.0.1")   Added in cURL 7.21.3.
                  Available since PHP 5.5.0.
                  
                  <strong>$value</strong> should be a stream resource (using <strong>fopen()</strong>, for example) for the following
                  values of the <strong>$option</strong> parameter: OptionSet <strong>$value</strong> to<info>CURLOPT_FILE</info> The file that the
                  transfer should be written to. The default is <return>STDOUT</return> (the browser window).
                  <info>CURLOPT_INFILE</info> The file that the transfer should be read from when uploading.
                  <info>CURLOPT_STDERR</info> An alternative location to output errors to instead of <return>STDERR</return>.
                  <info>CURLOPT_WRITEHEADER</info> The file that the header part of the transfer is written to.
                  
                  <strong>$value</strong> should be the name of a valid function or a Closure  for the following
                  values of the <strong>$option</strong> parameter: OptionSet <strong>$value</strong> to<info>CURLOPT_HEADERFUNCTION</info> A
                  callback accepting two parameters. The first is the cURL resource, the second is a
                  string with the header data to be written. The header data must be written by this
                  callback. Return the number of  bytes written. <info>CURLOPT_PASSWDFUNCTION</info> A callback
                  accepting three parameters.  The first is the cURL resource, the second is a
                  string containing a password prompt, and the third is the maximum password length.
                  Return the string containing the password. <info>CURLOPT_PROGRESSFUNCTION</info> A callback
                  accepting five parameters. The first is the cURL resource, the second is the total
                  number of bytes expected to be downloaded in this transfer, the third is the
                  number of bytes downloaded so far, the fourth is the total number of bytes
                  expected to be uploaded in this transfer, and the fifth is the number of bytes
                  uploaded so far.  The callback is only called when the <info>CURLOPT_NOPROGRESS</info> option
                  is set to <info>false</info>.  Return a non-zero value to abort the transfer. In which case,
                  the transfer will set a <info>CURLE_ABORTED_BY_CALLBACK</info> error. <info>CURLOPT_READFUNCTION</info> A
                  callback accepting three parameters.  The first is the cURL resource, the second
                  is a stream resource provided to cURL through the option <info>CURLOPT_INFILE</info>, and the
                  third is the maximum amount of data to be read. The callback must return a string
                  with a length equal or smaller than the amount of data requested, typically by
                  reading it from the passed stream resource. It should return an empty string to
                  signal <return>EOF</return>. <info>CURLOPT_WRITEFUNCTION</info> A callback accepting two parameters.  The first
                  is the cURL resource, and the second is a string with the data to be written. The
                  data must be saved by this callback. It must return the exact number of bytes
                  written  or the transfer will be aborted with an error.
                  
                  A callback accepting five parameters. The first is the cURL resource, the second
                  is the total number of bytes expected to be downloaded in this transfer, the third
                  is the number of bytes downloaded so far, the fourth is the total number of bytes
                  expected to be uploaded in this transfer, and the fifth is the number of bytes
                  uploaded so far.
                  
                  The callback is only called when the <info>CURLOPT_NOPROGRESS</info> option is set to <info>false</info>.
                  
                  Return a non-zero value to abort the transfer. In which case, the transfer will
                  set a <info>CURLE_ABORTED_BY_CALLBACK</info> error.
                  
                  Other values: OptionSet <strong>$value</strong> to<info>CURLOPT_SHARE</info> A result of <strong>curl_share_init()</strong>.
                  Makes the cURL handle to use the data from the shared handle.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>curl_setopt_array()</strong>


id: curl_setopt_array
type: function
doc:
<comment>Description:</comment>
  Set multiple options for a cURL transfer
  
  Sets multiple options for a cURL session. This function is useful for setting a large number of
  cURL options without repetitively calling <strong>curl_setopt()</strong>.

<comment>Param:</comment>
  <info>     </info>  <strong>$ch     </strong>  Un handle cURL întors de
                   <strong>curl_init()</strong>.
  <info>array</info>  <strong>$options</strong>  An <info>array</info> specifying which options to set and their values. The keys should be
                   valid <strong>curl_setopt()</strong> constants or their integer equivalents.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if all options were successfully set. If an option could not be successfully
        set, <info>false</info> is immediately returned, ignoring any future options in the <strong>$options</strong> array.

<comment>See Also:</comment>
   * <strong>curl_setopt()</strong>


id: curl_share_close
type: function
doc:
<comment>Description:</comment>
  Close a cURL share handle
  
  Closes a cURL share handle and frees all resources.

<comment>Param:</comment>
  <info>CurlShareHandle</info>  <strong>$share_handle</strong>  A cURL share handle returned by
                                  <strong>curl_share_init()</strong>.

<comment>Return:</comment>
  <info>void</info>  Nu este întoarsă nici o valoare.

<comment>See Also:</comment>
   * <strong>curl_share_init()</strong>


id: curl_share_errno
type: function
doc:
<comment>Description:</comment>
  Return the last share curl error number
  
  Return an integer containing the last share curl error number.

<comment>Param:</comment>
  <info>CurlShareHandle</info>  <strong>$share_handle</strong>  A cURL share handle returned by
                                  <strong>curl_share_init()</strong>.

<comment>Return:</comment>
  <info>int</info>  Returns an integer containing the last share curl error number, sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>curl_errno()</strong>


id: curl_share_init
type: function
doc:
<comment>Description:</comment>
  Initialize a cURL share handle
  
  Allows to share data between cURL handles.

<comment>Return:</comment>
  <info>CurlShareHandle</info>  Returns a cURL share handle.

<comment>See Also:</comment>
   * <strong>curl_share_setopt()</strong>
   * <strong>curl_share_close()</strong>


id: curl_share_setopt
type: function
doc:
<comment>Description:</comment>
  Set an option for a cURL share handle
  
  Sets an option on the given cURL share handle.

<comment>Param:</comment>
  <info>CurlShareHandle</info>  <strong>$share_handle</strong>  A cURL share handle returned by
                                  <strong>curl_share_init()</strong>.
  <info>int            </info>  <strong>$option      </strong>  OptionDescription<info>CURLSHOPT_SHARE</info> Specifies a type of data that
                                  should be shared. <info>CURLSHOPT_UNSHARE</info> Specifies a type of data that
                                  will be no longer shared.
  <info>mixed          </info>  <strong>$value       </strong>  ValueDescription<info>CURL_LOCK_DATA_COOKIE</info> Shares cookie data.
                                  <info>CURL_LOCK_DATA_DNS</info> Shares DNS cache. Note that when you use cURL
                                  multi handles, all handles added to the same multi handle will
                                  share DNS cache by default. <info>CURL_LOCK_DATA_SSL_SESSION</info> Shares SSL
                                  session IDs, reducing the time spent on the SSL handshake when
                                  reconnecting to the same server. Note that SSL session IDs are
                                  reused within the same handle by default.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.


id: curl_share_strerror
type: function
doc:
<comment>Description:</comment>
  Return string describing the given error code
  
  Returns a text error message describing the given error code.

<comment>Param:</comment>
  <info>int</info>  <strong>$error_code</strong>  One of the cURL error codes constants.

<comment>Return:</comment>
  <info>stringnull</info>  Returns error description or <info>null</info> for invalid error code.

<comment>See Also:</comment>
   * <strong>curl_share_errno()</strong>
   * <strong>curl_strerror()</strong>


id: curl_strerror
type: function
doc:
<comment>Description:</comment>
  Return string describing the given error code
  
  Returns a text error message describing the given error code.

<comment>Param:</comment>
  <info>int</info>  <strong>$error_code</strong>  One of the cURL error codes constants.

<comment>Return:</comment>
  <info>stringnull</info>  Returns error description or <info>null</info> for invalid error code.

<comment>See Also:</comment>
   * <strong>curl_errno()</strong>
   * <strong>curl_error()</strong>
   * Curl error codes


id: curl_unescape
type: function
doc:
<comment>Description:</comment>
  Decodes the given URL encoded string
  
  This function decodes the given URL encoded string.

<comment>Param:</comment>
  <info>      </info>  <strong>$ch    </strong>  Un handle cURL întors de
                   <strong>curl_init()</strong>.
  <info>string</info>  <strong>$string</strong>  The URL encoded string to be decoded.

<comment>Return:</comment>
  <info>stringfalse</info>  Returns decoded string  sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>curl_escape()</strong>
   * <strong>urlencode()</strong>
   * <strong>urldecode()</strong>
   * <strong>rawurlencode()</strong>
   * <strong>rawurldecode()</strong>


id: curl_version
type: function
doc:
<comment>Description:</comment>
  Gets cURL version information
  
  Returns information about the cURL version.

<comment>Param:</comment>
  <info></info>  <strong>$age</strong>  

<comment>Return:</comment>
  <info>arrayfalse</info>  Returns an associative array with the following elements:  KeyValue
              descriptionversion_numbercURL 24 bit version numberversioncURL version number, as a
              stringssl_version_numberOpenSSL 24 bit version numberssl_versionOpenSSL version
              number, as a stringlibz_versionzlib version number, as a stringhostInformation about
              the host where cURL was builtagefeaturesA bitmask of the <return>CURL_VERSION_XXX</return>
              constantsprotocolsAn array of protocols names supported by cURL


id: current
type: function
doc:
<comment>Description:</comment>
  Return the current element in an array
  
  Every array has an internal pointer to its "current" element, which is initialized to the first
  element inserted into the array.

<comment>Param:</comment>
  <info>arrayobject</info>  <strong>$array</strong>  The array.

<comment>Return:</comment>
  <info>mixed</info>  The <strong>current()</strong> function simply returns the value of the array element that's currently being
         pointed to by the internal pointer.  It does not move the pointer in any way.  If the
         internal pointer points beyond the end of the elements list or the array is  empty,
         <strong>current()</strong> returns <info>false</info>.
         
         Această funcție poate întoarce valoarea Boolean <info>false</info>, dar poate de
         asemenea întoarce o valoare non-Boolean care evaluează în <info>false</info>. Vă rugăm să
         citiți secțiunea despre tipul Boolean
         pentru informații suplimentare. Utilizați
         operatorul === pentru a
         verifica valoarea întoarsă de această funcție.

<comment>See Also:</comment>
   * <strong>end()</strong>
   * <strong>key()</strong>
   * <strong>each()</strong>
   * <strong>prev()</strong>
   * <strong>reset()</strong>
   * <strong>next()</strong>


id: date
type: function
doc:
<comment>Description:</comment>
  Formatează o oră/dată
  
  Întoarce un string formatat în conformitate cu string-ul de formatare dat, utilizând <strong>$timestamp</strong>-ul
  întreg dat, sau data și ora curentă dacă nu este furnizat nici un timestamp. Cu alte cuvinte,
  <strong>$timestamp</strong> este opțional și implicit are valoarea întoarsă de <strong>time()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$format   </strong>  Format acceptat de <strong>DateTimeInterface::format()</strong>.
  <info>int   </info>  <strong>$timestamp</strong>  Parametrul opțional <strong>$timestamp</strong>
                      este un <info>integer</info> și este un moment de timp Unix și are valoarea
                      implicită a orei locale, dacă parametrul <strong>$timestamp</strong> nu
                      este indicat. Cu alte cuvinte, valoarea implicită este cea a funcției
                      <strong>time()</strong>.

<comment>Return:</comment>
  <info>string</info>  Întoarce un string cu dată formatat. Dacă este utilizată o valoare non-numerică pentru
          <strong>$timestamp</strong>, este întors <info>false</info> și este emisă o eroare de nivel <info>E_WARNING</info>.

<comment>See Also:</comment>
   * <strong>gmdate()</strong>
   * <strong>idate()</strong>
   * <strong>getdate()</strong>
   * <strong>getlastmod()</strong>
   * <strong>mktime()</strong>
   * <strong>strftime()</strong>
   * <strong>time()</strong>
   * <strong>DateTimeImmutable::__construct()</strong>
   * Constante DateTime predefinite


id: date_add
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::add
  
  Această funcție este pseudonim pentru:  DateTime::add


id: date_create
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::__construct
  
  Această funcție este pseudonim pentru:  DateTime::__construct


id: date_create_from_format
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::createFromFormat
  
  Această funcție este pseudonim pentru:  DateTime::createFromFormat


id: date_create_immutable
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTimeImmutable::__construct
  
  Această funcție este pseudonim pentru:  DateTimeImmutable::__construct


id: date_create_immutable_from_format
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTimeImmutable::createFromFormat
  
  Această funcție este pseudonim pentru:  DateTimeImmutable::createFromFormat


id: date_date_set
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::setDate
  
  Această funcție este pseudonim pentru:  DateTime::setDate


id: date_default_timezone_get
type: function
doc:
<comment>Description:</comment>
  Gets the default timezone used by all date/time functions in a script
    
  
  In order of preference, this function returns the default timezone by:  Reading the timezone set
  using the <strong>date_default_timezone_set()</strong> function (if any)  Prior to PHP 5.4.0 only: Reading the TZ
  environment variable (if non empty)  Reading the value of the date.timezone ini option (if set)
  Prior to PHP 5.4.0 only: Querying the host operating system (if supported and allowed by the OS).
  This uses an algorithm that has to guess the timezone. This is by no means going to work correctly
  for  every situation. A warning is shown when this stage is reached. Do not rely on it to be
  guessed correctly, and set date.timezone to the correct timezone instead.
  
  Reading the timezone set using the <strong>date_default_timezone_set()</strong> function (if any)
  
  Prior to PHP 5.4.0 only: Reading the TZ environment variable (if non empty)
  
  Reading the value of the date.timezone ini option (if set)
  
  Prior to PHP 5.4.0 only: Querying the host operating system (if supported and allowed by the OS).
  This uses an algorithm that has to guess the timezone. This is by no means going to work correctly
  for  every situation. A warning is shown when this stage is reached. Do not rely on it to be
  guessed correctly, and set date.timezone to the correct timezone instead.
  
  If none of the above succeed, date_default_timezone_get will return a default timezone of <return>UTC</return>.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info>.

<comment>See Also:</comment>
   * <strong>date_default_timezone_set()</strong>
   * 


id: date_default_timezone_set
type: function
doc:
<comment>Description:</comment>
  Sets the default timezone used by all date/time functions in a script
    
  
  <strong>date_default_timezone_set()</strong> sets the default timezone used by all date/time functions.
  
  Since PHP 5.1.0 (when the date/time functions were rewritten), every call to a date/time function
  will generate a <info>E_NOTICE</info> if the timezone isn't valid, and/or a <info>E_WARNING</info> message if using the
  system settings or the TZ environment variable.
  
  Instead of using this function to set the default timezone in your script, you can also use the
  INI setting date.timezone to set the default timezone.

<comment>Param:</comment>
  <info>string</info>  <strong>$timezoneId</strong>  The timezone identifier, like <return>UTC</return>, <return>Africa/Lagos</return>, <return>Asia/Hong_Kong</return>, or
                       <return>Europe/Lisbon</return>. The list of valid identifiers is available in the .

<comment>Return:</comment>
  <info>bool</info>  This function returns <info>false</info> if the <strong>$timezoneId</strong> isn't valid, or <info>true</info> otherwise.

<comment>See Also:</comment>
   * <strong>date_default_timezone_get()</strong>
   * 


id: date_diff
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::diff
  
  Această funcție este pseudonim pentru:  DateTime::diff


id: date_format
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::format
  
  Această funcție este pseudonim pentru:  DateTime::format


id: date_get_last_errors
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::getLastErrors
  
  Această funcție este pseudonim pentru:  DateTime::getLastErrors


id: date_interval_create_from_date_string
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateInterval::createFromDateString
  
  Această funcție este pseudonim pentru:  DateInterval::createFromDateString


id: date_interval_format
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateInterval::format
  
  Această funcție este pseudonim pentru:  DateInterval::format


id: date_isodate_set
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::setISODate
  
  Această funcție este pseudonim pentru:  DateTime::setISODate


id: date_modify
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::modify
  
  Această funcție este pseudonim pentru:  DateTime::modify


id: date_offset_get
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::getOffset
  
  Această funcție este pseudonim pentru:  DateTime::getOffset


id: date_parse
type: function
doc:
<comment>Description:</comment>
  Returns associative array with detailed info about given date/time

<comment>Param:</comment>
  <info>string</info>  <strong>$datetime</strong>  Date/time in format accepted by <strong>DateTimeImmutable::__construct()</strong>.

<comment>Return:</comment>
  <info>array</info>  Returns <info>array</info> with information about the parsed date/time on success sau <info>false</info> în cazul
         eșecului.

<comment>See Also:</comment>
   * <strong>checkdate()</strong>
   * <strong>getdate()</strong>


id: date_parse_from_format
type: function
doc:
<comment>Description:</comment>
  Get info about given date formatted according to the specified format
  
  Returns associative array with detailed info about given date/time.

<comment>Param:</comment>
  <info>string</info>  <strong>$format  </strong>  Format accepted by <strong>DateTime::createFromFormat()</strong>.
  <info>string</info>  <strong>$datetime</strong>  String representing the date/time.

<comment>Return:</comment>
  <info>array</info>  Returns associative array with detailed info about given date/time.

<comment>See Also:</comment>
   * <strong>DateTime::createFromFormat()</strong>
   * <strong>checkdate()</strong>


id: date_sub
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::sub
  
  Această funcție este pseudonim pentru:  DateTime::sub


id: date_sun_info
type: function
doc:
<comment>Description:</comment>
  Returns an array with information about sunset/sunrise and twilight begin/end

<comment>Param:</comment>
  <info>int  </info>  <strong>$timestamp</strong>  Unix timestamp.
  <info>float</info>  <strong>$latitude </strong>  Latitude in degrees.
  <info>float</info>  <strong>$longitude</strong>  Longitude in degrees.

<comment>Return:</comment>
  <info>array</info>  Returns array on success sau <info>false</info> în cazul eșecului. The structure of the array is
         detailed in the following list:
         
         <return>sunrise</return> The timestamp of the sunrise (zenith angle = 90°35'). <return>sunset</return> The timestamp of the
         sunset (zenith angle = 90°35'). <return>transit</return> The timestamp when the sun is at its zenith, i.e.
         has reached its topmost point. <return>civil_twilight_begin</return> The start of the civil dawn (zenith
         angle = 96°). It ends at <return>sunrise</return>. <return>civil_twilight_end</return> The end of the civil dusk (zenith
         angle = 96°). It starts at <return>sunset</return>. <return>nautical_twilight_begin</return> The start of the nautical dawn
         (zenith angle = 102°). It ends at <return>civil_twilight_begin</return>. <return>nautical_twilight_end</return> The end of
         the nautical dusk (zenith angle = 102°). It starts at <return>civil_twilight_end</return>.
         <return>astronomical_twilight_begin</return> The start of the astronomical dawn (zenith angle = 108°). It
         ends at <return>nautical_twilight_begin</return>. <return>astronomical_twilight_end</return> The end of the astronomical dusk
         (zenith angle = 108°). It starts at <return>nautical_twilight_end</return>.
         
         The timestamp of the sunrise (zenith angle = 90°35').
         
         The timestamp of the sunset (zenith angle = 90°35').
         
         The timestamp when the sun is at its zenith, i.e. has reached its topmost point.
         
         The start of the civil dawn (zenith angle = 96°). It ends at <return>sunrise</return>.
         
         The end of the civil dusk (zenith angle = 96°). It starts at <return>sunset</return>.
         
         The start of the nautical dawn (zenith angle = 102°). It ends at <return>civil_twilight_begin</return>.
         
         The end of the nautical dusk (zenith angle = 102°). It starts at <return>civil_twilight_end</return>.
         
         The start of the astronomical dawn (zenith angle = 108°). It ends at
         <return>nautical_twilight_begin</return>.
         
         The end of the astronomical dusk (zenith angle = 108°). It starts at <return>nautical_twilight_end</return>.
         
         The values of the array elements are either UNIX timestamps, <info>false</info> if the sun is below the
         respective zenith for the whole day, or <info>true</info> if the sun is above the respective zenith for
         the whole day.

<comment>See Also:</comment>
   * <strong>date_sunrise()</strong>
   * <strong>date_sunset()</strong>


id: date_sunrise
type: function
doc:
<comment>Description:</comment>
  Returns time of sunrise for a given day and location
  
  <strong>date_sunrise()</strong> returns the sunrise time for a given day (specified as a <strong>$timestamp</strong>) and location.

<comment>Param:</comment>
  <info>int      </info>  <strong>$timestamp   </strong>  The <strong>$timestamp</strong> of the day from which the sunrise time is taken.
  <info>int      </info>  <strong>$returnFormat</strong>  <strong>$returnFormat</strong>
                            constantsconstantdescriptionexampleSUNFUNCS_RET_STRINGreturns the result
                            as <info>string</info>16:46SUNFUNCS_RET_DOUBLEreturns the result as
                            <info>float</info>16.78243132SUNFUNCS_RET_TIMESTAMPreturns the result as <info>int</info>
                            (timestamp)1095034606
  <info>floatnull</info>  <strong>$latitude    </strong>  Defaults to North, pass in a negative value for South. See also:
                            date.default_latitude
  <info>floatnull</info>  <strong>$longitude   </strong>  Defaults to East, pass in a negative value for West. See also:
                            date.default_longitude
  <info>floatnull</info>  <strong>$zenith      </strong>  <strong>$zenith</strong> is the angle between the center of the sun and a line
                            perpendicular to earth's surface. It defaults to date.sunrise_zenith
                            Common <strong>$zenith</strong> anglesAngleDescription90°50'Sunrise: the point where the
                            sun becomes visible.96°Civil twilight: conventionally used to signify
                            the start of dawn.102°Nautical twilight: the point at which the horizon
                            starts being visible at sea.108°Astronomical twilight: the point at
                            which the sun starts being the source of any illumination.
  <info>floatnull</info>  <strong>$utcOffset   </strong>  Specified in hours. The <strong>$utcOffset</strong> is ignored, if <strong>$returnFormat</strong> is
                            <info>SUNFUNCS_RET_TIMESTAMP</info>.

<comment>Return:</comment>
  <info>stringintfloatfalse</info>  Returns the sunrise time in a specified <strong>$returnFormat</strong> on success sau <info>false</info> în
                       cazul eșecului. One potential reason for failure is that the sun does not
                       rise at all, which happens inside the polar circles for part of the year.

<comment>See Also:</comment>
   * <strong>date_sunset()</strong>
   * <strong>date_sun_info()</strong>


id: date_sunset
type: function
doc:
<comment>Description:</comment>
  Returns time of sunset for a given day and location
    
  
  <strong>date_sunset()</strong> returns the sunset time for a given day (specified as a <strong>$timestamp</strong>) and location.

<comment>Param:</comment>
  <info>int      </info>  <strong>$timestamp   </strong>  The <strong>$timestamp</strong> of the day from which the sunset time is taken.
  <info>int      </info>  <strong>$returnFormat</strong>  <strong>$returnFormat</strong>
                            constantsconstantdescriptionexampleSUNFUNCS_RET_STRINGreturns the result
                            as <info>string</info>16:46SUNFUNCS_RET_DOUBLEreturns the result as
                            <info>float</info>16.78243132SUNFUNCS_RET_TIMESTAMPreturns the result as <info>int</info>
                            (timestamp)1095034606
  <info>floatnull</info>  <strong>$latitude    </strong>  Defaults to North, pass in a negative value for South. See also:
                            date.default_latitude
  <info>floatnull</info>  <strong>$longitude   </strong>  Defaults to East, pass in a negative value for West. See also:
                            date.default_longitude
  <info>floatnull</info>  <strong>$zenith      </strong>  <strong>$zenith</strong> is the angle between the center of the sun and a line
                            perpendicular to earth's surface. It defaults to date.sunset_zenith
                            Common <strong>$zenith</strong> anglesAngleDescription90°50'Sunset: the point where the
                            sun becomes invisible.96°Civil twilight: conventionally used to signify
                            the end of dusk.102°Nautical twilight: the point at which the horizon
                            ends being visible at sea.108°Astronomical twilight: the point at which
                            the sun ends being the source of any illumination.
  <info>floatnull</info>  <strong>$utcOffset   </strong>  Specified in hours. The <strong>$utcOffset</strong> is ignored, if <strong>$returnFormat</strong> is
                            <info>SUNFUNCS_RET_TIMESTAMP</info>.

<comment>Return:</comment>
  <info>stringintfloatfalse</info>  Returns the sunset time in a specified <strong>$returnFormat</strong> on success sau <info>false</info> în
                       cazul eșecului. One potential reason for failure is that the sun does not set
                       at all, which happens inside the polar circles for part of the year.

<comment>See Also:</comment>
   * <strong>date_sunrise()</strong>
   * <strong>date_sun_info()</strong>


id: date_time_set
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::setTime
  
  Această funcție este pseudonim pentru:  DateTime::setTime


id: date_timestamp_get
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::getTimestamp
  
  Această funcție este pseudonim pentru:  DateTime::getTimestamp


id: date_timestamp_set
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::setTimestamp
  
  Această funcție este pseudonim pentru:  DateTime::setTimestamp


id: date_timezone_get
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::getTimezone
  
  Această funcție este pseudonim pentru:  DateTime::getTimezone


id: date_timezone_set
type: function
doc:
<comment>Description:</comment>
  Pseudonim pentru DateTime::setTimezone
  
  Această funcție este pseudonim pentru:  DateTime::setTimezone


id: db2_autocommit
type: function
doc:
<comment>Description:</comment>
  Returns or sets the AUTOCOMMIT state for a database connection
    
  
  Sets or gets the AUTOCOMMIT behavior of the specified connection resource.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  A valid database connection resource variable as returned from
                         <strong>db2_connect()</strong> or <strong>db2_pconnect()</strong>.
  <info>bool    </info>  <strong>$value     </strong>  One of the following constants:  <return>DB2_AUTOCOMMIT_OFF</return> Turns AUTOCOMMIT off.
                         <return>DB2_AUTOCOMMIT_ON</return> Turns AUTOCOMMIT on.
                         
                         Turns AUTOCOMMIT off.
                         
                         Turns AUTOCOMMIT on.

<comment>Return:</comment>
  <info>mixed</info>  When <strong>db2_autocommit()</strong> receives only the <strong>$connection</strong> parameter, it returns the current state
         of AUTOCOMMIT for the requested connection as an integer value. A value of
         <info>DB2_AUTOCOMMIT_OFF</info> indicates that AUTOCOMMIT is off, while a value of <info>DB2_AUTOCOMMIT_ON</info>
         indicates that AUTOCOMMIT is on.
         
         When <strong>db2_autocommit()</strong> receives both the <strong>$connection</strong> parameter and <strong>$autocommit</strong> parameter, it
         attempts to set the AUTOCOMMIT state of the requested connection to the corresponding
         state. Întoarce valoarea <info>true</info> în cazul
         succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_connect()</strong>
   * <strong>db2_pconnect()</strong>


id: db2_bind_param
type: function
doc:
<comment>Description:</comment>
  Binds a PHP variable to an SQL statement parameter
    
  
  Binds a PHP variable to an SQL statement parameter in a statement resource returned by
  <strong>db2_prepare()</strong>. This function gives you more control over the parameter type, data type, precision,
  and scale for the parameter than simply passing the variable as part of the optional input array
  to <strong>db2_execute()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt            </strong>  A prepared statement returned from <strong>db2_prepare()</strong>.
  <info>int     </info>  <strong>$parameter_number</strong>  Specifies the 1-indexed position of the parameter in the prepared
                               statement.
  <info>string  </info>  <strong>$variable_name   </strong>  A string specifying the name of the PHP variable to bind to the
                               parameter specified by <strong>$parameter_number</strong>.
  <info>int     </info>  <strong>$parameter_type  </strong>  A constant specifying whether the PHP variable should be bound to the
                               SQL parameter as an input parameter (<return>DB2_PARAM_IN</return>), an output
                               parameter (<return>DB2_PARAM_OUT</return>), or as a parameter that accepts input and
                               returns output (<return>DB2_PARAM_INOUT</return>). To avoid memory overhead, you can
                               also specify <return>DB2_PARAM_FILE</return> to bind the PHP variable to the name of a
                               file that contains large object (BLOB, CLOB, or DBCLOB) data.
  <info>int     </info>  <strong>$data_type       </strong>  A constant specifying the SQL data type that the PHP variable should
                               be bound as: one of <return>DB2_BINARY</return>, <return>DB2_CHAR</return>, <return>DB2_DOUBLE</return>, or <return>DB2_LONG</return> .
  <info>int     </info>  <strong>$precision       </strong>  Specifies the precision with which the variable should be bound to
                               the database. This parameter can also be used for retrieving XML
                               output values  from stored procedures. A non-negative value specifies
                               the maximum size of  the XML data that will be retrieved from the
                               database. If this parameter  is not used, a default of 1MB will be
                               assumed for retrieving the XML  output value from the stored
                               procedure.
  <info>int     </info>  <strong>$scale           </strong>  Specifies the scale with which the variable should be bound to the
                               database.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_execute()</strong>
   * <strong>db2_prepare()</strong>


id: db2_client_info
type: function
doc:
<comment>Description:</comment>
  Returns an object with properties that describe the DB2 database client
  
  This function returns an object with read-only properties that return information about the DB2
  database client. The following table lists the DB2 client properties: DB2 client
  propertiesProperty nameReturn typeDescriptionAPPL_CODEPAGEintThe application code
  page.CONN_CODEPAGEintThe code page for the current connection.DATA_SOURCE_NAMEstringThe data
  source name (DSN) used to create the current connection to the database.DRIVER_NAMEstringThe name
  of the library that implements the DB2 Call Level Interface (CLI)
  specification.DRIVER_ODBC_VERstringThe version of ODBC that the DB2 client supports. This returns
  a string "MM.mm" where MM is the major version and mm is the minor version. The DB2 client always
  returns "03.51". DRIVER_VERstringThe version of the client, in the form of a string "MM.mm.uuuu"
  where MM is the major version,  mm is the minor version, and uuuu is the update. For example,
  "08.02.0001" represents major version 8, minor version 2, update 1. ODBC_SQL_CONFORMANCEstringThe
  level of ODBC SQL grammar supported by the client: MINIMUM Supports the minimum ODBC SQL grammar.
  CORE Supports the core ODBC SQL grammar. EXTENDED Supports extended ODBC SQL grammar.
  ODBC_VERstringThe version of ODBC that the ODBC driver manager supports. This returns a string
  "MM.mm.rrrr" where MM is the major version, mm is the minor version, and rrrr is the release. The
  DB2 client always returns "03.01.0000".
  
  The level of ODBC SQL grammar supported by the client: MINIMUM Supports the minimum ODBC SQL
  grammar. CORE Supports the core ODBC SQL grammar. EXTENDED Supports extended ODBC SQL grammar.
  
  Supports the minimum ODBC SQL grammar.
  
  Supports the core ODBC SQL grammar.
  
  Supports extended ODBC SQL grammar.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  Specifies an active DB2 client connection.

<comment>Return:</comment>
  <info>object</info>  Returns an object on a successful call. Returns <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>db2_server_info()</strong>


id: db2_close
type: function
doc:
<comment>Description:</comment>
  Closes a database connection
    
  
  This function closes a DB2 client connection created with <strong>db2_connect()</strong> and returns the
  corresponding resources to the database server.
  
  If you attempt to close a persistent DB2 client connection created with <strong>db2_pconnect()</strong>, the close
  request is ignored and the persistent DB2 client connection remains available for the next caller.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  Specifies an active DB2 client connection.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_connect()</strong>
   * <strong>db2_pclose()</strong>
   * <strong>db2_pconnect()</strong>


id: db2_column_privileges
type: function
doc:
<comment>Description:</comment>
  Returns a result set listing the columns and associated privileges for a table
    
  
  Returns a result set listing the columns and associated privileges for a table.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection </strong>  A valid connection to an IBM DB2, Cloudscape, or Apache Derby database.
  <info>string  </info>  <strong>$qualifier  </strong>  A qualifier for DB2 databases running on OS/390 or z/OS servers. For other
                          databases, pass <info>null</info> or an empty string.
  <info>string  </info>  <strong>$schema     </strong>  The schema which contains the tables. To match all schemas, pass <info>null</info> or
                          an empty string.
  <info>string  </info>  <strong>$table-name </strong>  The name of the table or view. To match all tables in the database, pass
                          <info>null</info> or an empty string.
  <info>string  </info>  <strong>$column-name</strong>  The name of the column. To match all columns in the table, pass <info>null</info> or an
                          empty string.

<comment>Return:</comment>
  <info>resource</info>  Returns a statement resource with a result set containing rows describing the column
            privileges for columns matching the specified parameters. The rows are composed of the
            following columns: Column nameDescriptionTABLE_CATName of the catalog. The value is NULL
            if this table does not have catalogs.TABLE_SCHEMName of the schema.TABLE_NAMEName of the
            table or view.COLUMN_NAMEName of the column.GRANTORAuthorization ID of the user who
            granted the privilege.GRANTEEAuthorization ID of the user to whom the privilege was
            granted.PRIVILEGEThe privilege for the column.IS_GRANTABLEWhether the GRANTEE is
            permitted to grant this privilege to other users.

<comment>See Also:</comment>
   * <strong>db2_columns()</strong>
   * <strong>db2_foreign_keys()</strong>
   * <strong>db2_primary_keys()</strong>
   * <strong>db2_procedure_columns()</strong>
   * <strong>db2_procedures()</strong>
   * <strong>db2_special_columns()</strong>
   * <strong>db2_statistics()</strong>
   * <strong>db2_table_privileges()</strong>
   * <strong>db2_tables()</strong>


id: db2_columns
type: function
doc:
<comment>Description:</comment>
  Returns a result set listing the columns and associated metadata for a table
    
  
  Returns a result set listing the columns and associated metadata for a table.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection </strong>  A valid connection to an IBM DB2, Cloudscape, or Apache Derby database.
  <info>string  </info>  <strong>$qualifier  </strong>  A qualifier for DB2 databases running on OS/390 or z/OS servers. For other
                          databases, pass <info>null</info> or an empty string.
  <info>string  </info>  <strong>$schema     </strong>  The schema which contains the tables. To match all schemas, pass <return>'%'</return>.
  <info>string  </info>  <strong>$table-name </strong>  The name of the table or view. To match all tables in the database, pass
                          <info>null</info> or an empty string.
  <info>string  </info>  <strong>$column-name</strong>  The name of the column. To match all columns in the table, pass <info>null</info> or an
                          empty string.

<comment>Return:</comment>
  <info>resource</info>  Returns a statement resource with a result set containing rows describing the columns
            matching the specified parameters. The rows are composed of the following columns:
            Column nameDescriptionTABLE_CATName of the catalog. The value is NULL if this table does
            not have catalogs.TABLE_SCHEMName of the schema.TABLE_NAMEName of the table or
            view.COLUMN_NAMEName of the column.DATA_TYPEThe SQL data type for the column represented
            as an integer value.TYPE_NAMEA string representing the data type for the
            column.COLUMN_SIZEAn integer value representing the size of the column.BUFFER_LENGTH
            Maximum number of bytes necessary to store data from this column. DECIMAL_DIGITS The
            scale of the column, or <info>null</info> where scale is not applicable. NUM_PREC_RADIX An integer
            value of either <return>10</return> (representing an exact numeric data type), <return>2</return> (representing an
            approximate numeric data type), or <info>null</info> (representing a data type for which radix is not
            applicable). NULLABLEAn integer value representing whether the column is nullable or
            not.REMARKSDescription of the column.COLUMN_DEFDefault value for the
            column.SQL_DATA_TYPEAn integer value representing the size of the
            column.SQL_DATETIME_SUB Returns an integer value representing a datetime subtype code,
            or <info>null</info> for SQL data types to which this does not apply. CHAR_OCTET_LENGTH Maximum
            length in octets for a character data type column, which matches COLUMN_SIZE for
            single-byte character set data, or <info>null</info> for non-character data types.
            ORDINAL_POSITIONThe 1-indexed position of the column in the table.IS_NULLABLE A string
            value where 'YES' means that the column is nullable and 'NO' means that the column is
            not nullable.

<comment>See Also:</comment>
   * <strong>db2_column_privileges()</strong>
   * <strong>db2_foreign_keys()</strong>
   * <strong>db2_primary_keys()</strong>
   * <strong>db2_procedure_columns()</strong>
   * <strong>db2_procedures()</strong>
   * <strong>db2_special_columns()</strong>
   * <strong>db2_statistics()</strong>
   * <strong>db2_table_privileges()</strong>
   * <strong>db2_tables()</strong>


id: db2_commit
type: function
doc:
<comment>Description:</comment>
  Commits a transaction
    
  
  Commits an in-progress transaction on the specified connection resource and begins a new
  transaction. PHP applications normally default to AUTOCOMMIT mode, so <strong>db2_commit()</strong> is not
  necessary unless AUTOCOMMIT has been turned off for the connection resource.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  A valid database connection resource variable as returned from
                         <strong>db2_connect()</strong> or <strong>db2_pconnect()</strong>.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_autocommit()</strong>
   * <strong>db2_rollback()</strong>


id: db2_conn_error
type: function
doc:
<comment>Description:</comment>
  Returns a string containing the SQLSTATE returned by the last connection attempt
    
  
  <strong>db2_conn_error()</strong> returns an SQLSTATE value representing the reason the last attempt to connect to
  a database failed. As <strong>db2_connect()</strong> returns <info>false</info> in the event of a failed connection attempt, you
  do not pass any parameters to <strong>db2_conn_error()</strong> to retrieve the SQLSTATE value.
  
  If, however, the connection was successful but becomes invalid over time, you can pass the
  <strong>$connection</strong> parameter to retrieve the SQLSTATE value for a specific connection.
  
  To learn what the SQLSTATE value means, you can issue the following command at a DB2 Command Line
  Processor prompt: db2 '? <strong>$sqlstate-value</strong>'. You can also call <strong>db2_conn_errormsg()</strong> to retrieve an
  explicit error message and the associated SQLCODE value.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  A connection resource associated with a connection that initially
                         succeeded, but which over time became invalid.

<comment>Return:</comment>
  <info>string</info>  Returns the SQLSTATE value resulting from a failed connection attempt. Returns an empty
          string if there is no error associated with the last connection attempt.

<comment>See Also:</comment>
   * <strong>db2_conn_errormsg()</strong>
   * <strong>db2_connect()</strong>
   * <strong>db2_stmt_error()</strong>
   * <strong>db2_stmt_errormsg()</strong>


id: db2_conn_errormsg
type: function
doc:
<comment>Description:</comment>
  Returns the last connection error message and SQLCODE value
    
  
  <strong>db2_conn_errormsg()</strong> returns an error message and SQLCODE value representing the reason the last
  database connection attempt failed. As <strong>db2_connect()</strong> returns <info>false</info> in the event of a failed
  connection attempt, do not pass any parameters to <strong>db2_conn_errormsg()</strong> to retrieve the associated
  error message and SQLCODE value.
  
  If, however, the connection was successful but becomes invalid over time, you can pass the
  <strong>$connection</strong> parameter to retrieve the associated error message and SQLCODE value for a specific
  connection.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  A connection resource associated with a connection that initially
                         succeeded, but which over time became invalid.

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the error message and SQLCODE value resulting from a failed
          connection attempt. If there is no error associated with the last connection attempt,
          <strong>db2_conn_errormsg()</strong> returns an empty string.

<comment>See Also:</comment>
   * <strong>db2_conn_error()</strong>
   * <strong>db2_connect()</strong>
   * <strong>db2_stmt_error()</strong>
   * <strong>db2_stmt_errormsg()</strong>


id: db2_connect
type: function
doc:
<comment>Description:</comment>
  Returns a connection to a database
    
  
  Creates a new connection to an IBM DB2 Universal Database, IBM Cloudscape, or Apache Derby
  database.

<comment>Param:</comment>
  <info>string</info>  <strong>$database         </strong>  For a cataloged connection to a database, <strong>$database</strong> represents the
                              database alias in the DB2 client catalog.
                              
                              For an uncataloged connection to a database,  <strong>$database</strong> represents a
                              complete connection string in the following format:
                              DATABASE=<strong>$database</strong>;HOSTNAME=<strong>$hostname</strong>;PORT=<strong>$port</strong>;PROTOCOL=TCPIP;UID=<strong>$username</strong>;PWD=<strong>$password</strong>;
                              where the parameters represent the following values: <strong>$database</strong> The
                              name of the database. <strong>$hostname</strong> The hostname or IP address of the
                              database server. <strong>$port</strong> The TCP/IP port on which the database is
                              listening for requests. <strong>$username</strong> The username with which you are
                              connecting to the database. <strong>$password</strong> The password with which you are
                              connecting to the database.
                              
                              The name of the database.
                              
                              The hostname or IP address of the database server.
                              
                              The TCP/IP port on which the database is listening for requests.
                              
                              The username with which you are connecting to the database.
                              
                              The password with which you are connecting to the database.
  <info>string</info>  <strong>$database         </strong>  The name of the database.
  <info>      </info>  <strong>$hostname         </strong>  The hostname or IP address of the database server.
  <info>      </info>  <strong>$port             </strong>  The TCP/IP port on which the database is listening for requests.
  <info>string</info>  <strong>$username         </strong>  The username with which you are connecting to the database.
  <info>string</info>  <strong>$password         </strong>  The password with which you are connecting to the database.
  <info>string</info>  <strong>$username         </strong>  The username with which you are connecting to the database.
                              
                              For uncataloged connections, you must pass a <info>null</info> value or empty
                              string.
  <info>string</info>  <strong>$password         </strong>  The password with which you are connecting to the database.
                              
                              For uncataloged connections, you must pass a <info>null</info> value or empty
                              string.
  <info>array </info>  <strong>$options          </strong>  An associative array of connection options that affect the behavior of
                              the connection, where valid array keys include: <strong>$autocommit</strong> Passing
                              the <return>DB2_AUTOCOMMIT_ON</return> value turns autocommit on for this connection
                              handle.  Passing the <return>DB2_AUTOCOMMIT_OFF</return> value turns autocommit off for
                              this connection handle. <strong>$DB2_ATTR_CASE</strong> Passing the <return>DB2_CASE_NATURAL</return>
                              value specifies that column names are returned in natural case.
                              Passing the <return>DB2_CASE_LOWER</return> value specifies that column names are
                              returned in lower case.  Passing the <return>DB2_CASE_UPPER</return> value specifies
                              that column names are returned in upper case. <strong>$CURSOR</strong> Passing the
                              <return>DB2_FORWARD_ONLY</return> value specifies a forward-only cursor for a statement
                              resource. This is the default cursor type and is supported on all
                              database servers.  Passing the <return>DB2_SCROLLABLE</return> value specifies a
                              scrollable cursor for a statement resource. This mode enables random
                              access to rows in a result set, but currently is supported only by IBM
                              DB2 Universal Database.
                              
                              Passing the <return>DB2_AUTOCOMMIT_ON</return> value turns autocommit on for this
                              connection handle.
                              
                              Passing the <return>DB2_AUTOCOMMIT_OFF</return> value turns autocommit off for this
                              connection handle.
                              
                              Passing the <return>DB2_CASE_NATURAL</return> value specifies that column names are
                              returned in natural case.
                              
                              Passing the <return>DB2_CASE_LOWER</return> value specifies that column names are
                              returned in lower case.
                              
                              Passing the <return>DB2_CASE_UPPER</return> value specifies that column names are
                              returned in upper case.
                              
                              Passing the <return>DB2_FORWARD_ONLY</return> value specifies a forward-only cursor for
                              a statement resource. This is the default cursor type and is supported
                              on all database servers.
                              
                              Passing the <return>DB2_SCROLLABLE</return> value specifies a scrollable cursor for a
                              statement resource. This mode enables random access to rows in a
                              result set, but currently is supported only by IBM DB2 Universal
                              Database.
                              
                              The following new option is available in ibm_db2 version 1.7.0 and
                              later.  <strong>$trustedcontext</strong> Passing the DB2_TRUSTED_CONTEXT_ENABLE value
                              turns trusted context  on for this connection handle. This parameter
                              cannot be set using  <strong>db2_set_option()</strong>.  This key works only if the
                              database is cataloged (even if the  database is local), or if you
                              specify the full DSN when you create   the connection.  To catalog the
                              database, use following commands: db2 catalog tcpip node loopback
                              remote \<SERVERNAME&gt; server \<SERVICENAME&gt;
                              db2 catalog database \<LOCALDBNAME&gt; as \<REMOTEDBNAME&gt; at node loopback
                              db2 "update dbm cfg using svcename \<SERVICENAME&gt;"
                              db2set DB2COMM=TCPIP
                              
                              Passing the DB2_TRUSTED_CONTEXT_ENABLE value turns trusted context  on
                              for this connection handle. This parameter cannot be set using
                              <strong>db2_set_option()</strong>.
                              
                              This key works only if the database is cataloged (even if the
                              database is local), or if you specify the full DSN when you create
                              the connection.
                              
                              To catalog the database, use following commands:
                              
                              db2 catalog tcpip node loopback remote \<SERVERNAME&gt; server \<SERVICENAME&gt;
                              db2 catalog database \<LOCALDBNAME&gt; as \<REMOTEDBNAME&gt; at node loopback
                              db2 "update dbm cfg using svcename \<SERVICENAME&gt;"
                              db2set DB2COMM=TCPIP
                              
                              The following new i5/OS options are available in ibm_db2 version 1.5.1
                              and later.  <strong>$i5_lib</strong> A character value that indicates the default
                              library that will be  used for resolving unqualified file references.
                              This is not valid  if the connection is using system naming mode.
                              <strong>$i5_naming</strong><return>DB2_I5_NAMING_ON</return> value turns on DB2 UDB CLI iSeries  system
                              naming mode. Files are qualified using the slash (/) delimiter.
                              Unqualified files are resolved using the library list for the job.
                              <return>DB2_I5_NAMING_OFF</return> value turns off DB2 UDB CLI default  naming mode,
                              which is SQL naming. Files are qualified using the period (.)
                              delimiter. Unqualified files are resolved using either the default
                              library  or the current user ID. <strong>$i5_commit</strong> The <strong>$i5_commit</strong> attribute
                              should be set before the  <strong>db2_connect()</strong>. If the value is changed after
                              the  connection has been established, and the connection is to a
                              remote data  source, the change does not take effect until the next
                              successful  <strong>db2_connect()</strong> for the connection handle.  The php.ini
                              setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or <return>DB2_I5_TXN_NO_COMMIT</return> is the
                              default, but may be  overridden with the <strong>$i5_commit</strong> option.
                              <return>DB2_I5_TXN_NO_COMMIT</return> - Commitment control is not used.
                              <return>DB2_I5_TXN_READ_UNCOMMITTED</return> - Dirty reads, nonrepeatable  reads, and
                              phantoms are possible. <return>DB2_I5_TXN_READ_COMMITTED</return> - Dirty reads are not
                              possible.  Nonrepeatable reads, and phantoms are possible.
                              <return>DB2_I5_TXN_REPEATABLE_READ</return> - Dirty reads and nonrepeatable  reads are
                              not possible. Phantoms are possible. <return>DB2_I5_TXN_SERIALIZABLE</return> -
                              Transactions are serializable.  Dirty reads, non-repeatable reads, and
                              phantoms are not possible <strong>$i5_query_optimize</strong><return>DB2_FIRST_IO</return> All queries
                              are optimized with the goal of  returning the first page of output as
                              fast as possible. This goal works well  when the output is controlled
                              by a user who is most likely to cancel the query  after viewing the
                              first page of output data. Queries coded with an  OPTIMIZE FOR nnn
                              ROWS clause honor the goal specified by the clause. <return>DB2_ALL_IO</return> All
                              queries are optimized with the goal of running  the entire query to
                              completion in the shortest amount of elapsed time. This is a  good
                              option when the output of a query is being written to a file or
                              report, or  the interface is queuing the output data. Queries coded
                              with an OPTIMIZE FOR nnn  ROWS clause honor the goal specified by the
                              clause. This is the default. <strong>$i5_dbcs_alloc</strong><return>DB2_I5_DBCS_ALLOC_ON</return> value
                              turns on DB2 6X allocation scheme  for DBCS translation column size
                              growth. <return>DB2_I5_DBCS_ALLOC_OFF</return> value turns off DB2 6X allocation scheme
                              for DBCS translation column size growth.   Note: php.ini setting
                              <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or  <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default,
                              but may be overridden  with the <strong>$i5_dbcs_alloc</strong> option.
                              <strong>$i5_date_fmt</strong><return>DB2_I5_FMT_ISO</return> - The International Organization for
                              Standardization  (ISO) date format yyyy-mm-dd is used. This is the
                              default. <return>DB2_I5_FMT_USA</return> - The United States date format mm/dd/yyyy is
                              used. <return>DB2_I5_FMT_EUR</return> - The European date format dd.mm.yyyy is used.
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard date format
                              yyyy-mm-dd is used.  <return>DB2_I5_FMT_MDY</return> - The date format mm/dd/yyyy is
                              used.  <return>DB2_I5_FMT_DMY</return> - The date format dd/mm/yyyy is used.
                              <return>DB2_I5_FMT_YMD</return> - The date format yy/mm/dd is used. <return>DB2_I5_FMT_JUL</return> -
                              The Julian date format yy/ddd is used. <return>DB2_I5_FMT_JOB</return> - The job
                              default is used. <strong>$i5_date_sep</strong><return>DB2_I5_SEP_SLASH</return> - A slash ( / ) is used
                              as the date separator.  This is the default. <return>DB2_I5_SEP_DASH</return> - A dash
                              ( - ) is used as the date separator. <return>DB2_I5_SEP_PERIOD</return> - A period ( .
                              ) is used as the date  separator. <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is
                              used as the date separator. <return>DB2_I5_SEP_BLANK</return> - A blank is used as the
                              date separator. <return>DB2_I5_SEP_JOB</return> - The job default is used
                              <strong>$i5_time_fmt</strong><return>DB2_I5_FMT_ISO</return> - The International Organization for
                              Standardization (ISO) time format hh.mm.ss is used. This is the
                              default. <return>DB2_I5_FMT_USA</return> - The United States time format  hh:mmxx is
                              used, where xx is AM or PM. <return>DB2_I5_FMT_EUR</return> - The European time format
                              hh.mm.ss  is used. <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard
                              time format hh:mm:ss is used. <return>DB2_I5_FMT_HMS</return> - The hh:mm:ss format is
                              used. <strong>$i5_time_sep</strong><return>DB2_I5_SEP_COLON</return> - A colon ( : ) is used as the time
                              separator. This is the default. <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is
                              used as the time  separator. <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used
                              as the time  separator. <return>DB2_I5_SEP_BLANK</return> - A blank is used as the time
                              separator. <return>DB2_I5_SEP_JOB</return> - The job default is used.
                              <strong>$i5_decimal_sep</strong><return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as  the
                              decimal separator. This is the default. <return>DB2_I5_SEP_COMMA</return> - A comma ( ,
                              ) is used as the  decimal separator. <return>DB2_I5_SEP_JOB</return> - The job default
                              is used.
                              
                              A character value that indicates the default library that will be
                              used for resolving unqualified file references. This is not valid  if
                              the connection is using system naming mode.
                              
                              <return>DB2_I5_NAMING_ON</return> value turns on DB2 UDB CLI iSeries  system naming
                              mode. Files are qualified using the slash (/) delimiter.  Unqualified
                              files are resolved using the library list for the job.
                              
                              <return>DB2_I5_NAMING_OFF</return> value turns off DB2 UDB CLI default  naming mode,
                              which is SQL naming. Files are qualified using the period (.)
                              delimiter. Unqualified files are resolved using either the default
                              library  or the current user ID.
                              
                              The <strong>$i5_commit</strong> attribute should be set before the  <strong>db2_connect()</strong>. If
                              the value is changed after the  connection has been established, and
                              the connection is to a remote data  source, the change does not take
                              effect until the next successful  <strong>db2_connect()</strong> for the connection
                              handle.  The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              <return>DB2_I5_TXN_NO_COMMIT</return> - Commitment control is not used.
                              
                              <return>DB2_I5_TXN_READ_UNCOMMITTED</return> - Dirty reads, nonrepeatable  reads, and
                              phantoms are possible.
                              
                              <return>DB2_I5_TXN_READ_COMMITTED</return> - Dirty reads are not possible.
                              Nonrepeatable reads, and phantoms are possible.
                              
                              <return>DB2_I5_TXN_REPEATABLE_READ</return> - Dirty reads and nonrepeatable  reads are
                              not possible. Phantoms are possible.
                              
                              <return>DB2_I5_TXN_SERIALIZABLE</return> - Transactions are serializable.  Dirty reads,
                              non-repeatable reads, and phantoms are not possible
                              
                              <return>DB2_FIRST_IO</return> All queries are optimized with the goal of  returning the
                              first page of output as fast as possible. This goal works well  when
                              the output is controlled by a user who is most likely to cancel the
                              query  after viewing the first page of output data. Queries coded with
                              an  OPTIMIZE FOR nnn ROWS clause honor the goal specified by the
                              clause.
                              
                              <return>DB2_ALL_IO</return> All queries are optimized with the goal of running  the
                              entire query to completion in the shortest amount of elapsed time.
                              This is a  good option when the output of a query is being written to
                              a file or report, or  the interface is queuing the output data.
                              Queries coded with an OPTIMIZE FOR nnn  ROWS clause honor the goal
                              specified by the clause. This is the default.
                              
                              <return>DB2_I5_DBCS_ALLOC_ON</return> value turns on DB2 6X allocation scheme  for DBCS
                              translation column size growth.
                              
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> value turns off DB2 6X allocation scheme  for
                              DBCS translation column size growth.
                              
                              Note: php.ini setting <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default, but may be overridden  with the
                              <strong>$i5_dbcs_alloc</strong> option.
                              
                              <return>DB2_I5_FMT_ISO</return> - The International Organization for Standardization
                              (ISO) date format yyyy-mm-dd is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European date format dd.mm.yyyy is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard date format
                              yyyy-mm-dd is used.
                              
                              <return>DB2_I5_FMT_MDY</return> - The date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_DMY</return> - The date format dd/mm/yyyy is used.
                              
                              <return>DB2_I5_FMT_YMD</return> - The date format yy/mm/dd is used.
                              
                              <return>DB2_I5_FMT_JUL</return> - The Julian date format yy/ddd is used.
                              
                              <return>DB2_I5_FMT_JOB</return> - The job default is used.
                              
                              <return>DB2_I5_SEP_SLASH</return> - A slash ( / ) is used as the date separator.  This
                              is the default.
                              
                              <return>DB2_I5_SEP_DASH</return> - A dash ( - ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the date  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the date separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used
                              
                              <return>DB2_I5_FMT_ISO</return> - The International Organization for  Standardization
                              (ISO) time format hh.mm.ss is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States time format  hh:mmxx is used, where
                              xx is AM or PM.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European time format hh.mm.ss  is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard  time format
                              hh:mm:ss is used.
                              
                              <return>DB2_I5_FMT_HMS</return> - The hh:mm:ss format is used.
                              
                              <return>DB2_I5_SEP_COLON</return> - A colon ( : ) is used as the time  separator. This
                              is the default.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the time separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as  the decimal separator.
                              This is the default.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the  decimal separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
                              
                              The following new i5/OS option is available in ibm_db2 version 1.8.0
                              and later.   <strong>$i5_libl</strong> A character value that indicates the library
                              list that will be used for  resolving unqualified file references.
                              Specify the library list  elements separated by blanks
                              'i5_libl'=&gt;"MYLIB YOURLIB ANYLIB".  <strong>$i5_libl</strong> calls
                              qsys2/qcmdexc('cmd',cmdlen), which is only  available in i5/OS V5R4
                              and later.
                              
                              A character value that indicates the library list that will be used
                              for  resolving unqualified file references. Specify the library list
                              elements separated by blanks 'i5_libl'=&gt;"MYLIB YOURLIB ANYLIB".
                              
                              <strong>$i5_libl</strong> calls qsys2/qcmdexc('cmd',cmdlen), which is only  available
                              in i5/OS V5R4 and later.
  <info>      </info>  <strong>$autocommit       </strong>  Passing the <return>DB2_AUTOCOMMIT_ON</return> value turns autocommit on for this
                              connection handle.
                              
                              Passing the <return>DB2_AUTOCOMMIT_OFF</return> value turns autocommit off for this
                              connection handle.
  <info>      </info>  <strong>$DB2_ATTR_CASE    </strong>  Passing the <return>DB2_CASE_NATURAL</return> value specifies that column names are
                              returned in natural case.
                              
                              Passing the <return>DB2_CASE_LOWER</return> value specifies that column names are
                              returned in lower case.
                              
                              Passing the <return>DB2_CASE_UPPER</return> value specifies that column names are
                              returned in upper case.
  <info>      </info>  <strong>$CURSOR           </strong>  Passing the <return>DB2_FORWARD_ONLY</return> value specifies a forward-only cursor for
                              a statement resource. This is the default cursor type and is supported
                              on all database servers.
                              
                              Passing the <return>DB2_SCROLLABLE</return> value specifies a scrollable cursor for a
                              statement resource. This mode enables random access to rows in a
                              result set, but currently is supported only by IBM DB2 Universal
                              Database.
  <info>      </info>  <strong>$trustedcontext   </strong>  Passing the DB2_TRUSTED_CONTEXT_ENABLE value turns trusted context  on
                              for this connection handle. This parameter cannot be set using
                              <strong>db2_set_option()</strong>.
                              
                              This key works only if the database is cataloged (even if the
                              database is local), or if you specify the full DSN when you create
                              the connection.
                              
                              To catalog the database, use following commands:
                              
                              db2 catalog tcpip node loopback remote \<SERVERNAME&gt; server \<SERVICENAME&gt;
                              db2 catalog database \<LOCALDBNAME&gt; as \<REMOTEDBNAME&gt; at node loopback
                              db2 "update dbm cfg using svcename \<SERVICENAME&gt;"
                              db2set DB2COMM=TCPIP
  <info>      </info>  <strong>$i5_lib           </strong>  A character value that indicates the default library that will be
                              used for resolving unqualified file references. This is not valid  if
                              the connection is using system naming mode.
  <info>      </info>  <strong>$i5_naming        </strong>  <return>DB2_I5_NAMING_ON</return> value turns on DB2 UDB CLI iSeries  system naming
                              mode. Files are qualified using the slash (/) delimiter.  Unqualified
                              files are resolved using the library list for the job.
                              
                              <return>DB2_I5_NAMING_OFF</return> value turns off DB2 UDB CLI default  naming mode,
                              which is SQL naming. Files are qualified using the period (.)
                              delimiter. Unqualified files are resolved using either the default
                              library  or the current user ID.
  <info>      </info>  <strong>$i5_commit        </strong>  The <strong>$i5_commit</strong> attribute should be set before the  <strong>db2_connect()</strong>. If
                              the value is changed after the  connection has been established, and
                              the connection is to a remote data  source, the change does not take
                              effect until the next successful  <strong>db2_connect()</strong> for the connection
                              handle.  The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              <return>DB2_I5_TXN_NO_COMMIT</return> - Commitment control is not used.
                              
                              <return>DB2_I5_TXN_READ_UNCOMMITTED</return> - Dirty reads, nonrepeatable  reads, and
                              phantoms are possible.
                              
                              <return>DB2_I5_TXN_READ_COMMITTED</return> - Dirty reads are not possible.
                              Nonrepeatable reads, and phantoms are possible.
                              
                              <return>DB2_I5_TXN_REPEATABLE_READ</return> - Dirty reads and nonrepeatable  reads are
                              not possible. Phantoms are possible.
                              
                              <return>DB2_I5_TXN_SERIALIZABLE</return> - Transactions are serializable.  Dirty reads,
                              non-repeatable reads, and phantoms are not possible
  <info>      </info>  <strong>$i5_query_optimize</strong>  <return>DB2_FIRST_IO</return> All queries are optimized with the goal of  returning the
                              first page of output as fast as possible. This goal works well  when
                              the output is controlled by a user who is most likely to cancel the
                              query  after viewing the first page of output data. Queries coded with
                              an  OPTIMIZE FOR nnn ROWS clause honor the goal specified by the
                              clause.
                              
                              <return>DB2_ALL_IO</return> All queries are optimized with the goal of running  the
                              entire query to completion in the shortest amount of elapsed time.
                              This is a  good option when the output of a query is being written to
                              a file or report, or  the interface is queuing the output data.
                              Queries coded with an OPTIMIZE FOR nnn  ROWS clause honor the goal
                              specified by the clause. This is the default.
  <info>      </info>  <strong>$i5_dbcs_alloc    </strong>  <return>DB2_I5_DBCS_ALLOC_ON</return> value turns on DB2 6X allocation scheme  for DBCS
                              translation column size growth.
                              
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> value turns off DB2 6X allocation scheme  for
                              DBCS translation column size growth.
                              
                              Note: php.ini setting <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default, but may be overridden  with the
                              <strong>$i5_dbcs_alloc</strong> option.
  <info>      </info>  <strong>$i5_date_fmt      </strong>  <return>DB2_I5_FMT_ISO</return> - The International Organization for Standardization
                              (ISO) date format yyyy-mm-dd is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European date format dd.mm.yyyy is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard date format
                              yyyy-mm-dd is used.
                              
                              <return>DB2_I5_FMT_MDY</return> - The date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_DMY</return> - The date format dd/mm/yyyy is used.
                              
                              <return>DB2_I5_FMT_YMD</return> - The date format yy/mm/dd is used.
                              
                              <return>DB2_I5_FMT_JUL</return> - The Julian date format yy/ddd is used.
                              
                              <return>DB2_I5_FMT_JOB</return> - The job default is used.
  <info>      </info>  <strong>$i5_date_sep      </strong>  <return>DB2_I5_SEP_SLASH</return> - A slash ( / ) is used as the date separator.  This
                              is the default.
                              
                              <return>DB2_I5_SEP_DASH</return> - A dash ( - ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the date  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the date separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used
  <info>      </info>  <strong>$i5_time_fmt      </strong>  <return>DB2_I5_FMT_ISO</return> - The International Organization for  Standardization
                              (ISO) time format hh.mm.ss is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States time format  hh:mmxx is used, where
                              xx is AM or PM.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European time format hh.mm.ss  is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard  time format
                              hh:mm:ss is used.
                              
                              <return>DB2_I5_FMT_HMS</return> - The hh:mm:ss format is used.
  <info>      </info>  <strong>$i5_time_sep      </strong>  <return>DB2_I5_SEP_COLON</return> - A colon ( : ) is used as the time  separator. This
                              is the default.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the time separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
  <info>      </info>  <strong>$i5_decimal_sep   </strong>  <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as  the decimal separator.
                              This is the default.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the  decimal separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
  <info>      </info>  <strong>$i5_libl          </strong>  A character value that indicates the library list that will be used
                              for  resolving unqualified file references. Specify the library list
                              elements separated by blanks 'i5_libl'=&gt;"MYLIB YOURLIB ANYLIB".
                              
                              <strong>$i5_libl</strong> calls qsys2/qcmdexc('cmd',cmdlen), which is only  available
                              in i5/OS V5R4 and later.

<comment>Return:</comment>
  <info>resource</info>  Returns a connection handle resource if the connection attempt is successful. If the
            connection attempt fails, <strong>db2_connect()</strong> returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_close()</strong>
   * <strong>db2_pconnect()</strong>


id: db2_cursor_type
type: function
doc:
<comment>Description:</comment>
  Returns the cursor type used by a statement resource
    
  
  Returns the cursor type used by a statement resource. Use this to determine if you are working
  with a forward-only cursor or scrollable cursor.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt</strong>  A valid statement resource.

<comment>Return:</comment>
  <info>int</info>  Returns either <return>DB2_FORWARD_ONLY</return> if the statement resource uses a forward-only cursor or
       <return>DB2_SCROLLABLE</return> if the statement resource uses a scrollable cursor.

<comment>See Also:</comment>
   * <strong>db2_prepare()</strong>


id: db2_escape_string
type: function
doc:
<comment>Description:</comment>
  Used to escape certain characters
    
  
  Prepends backslashes to special characters in the string argument.

<comment>Param:</comment>
  <info>string</info>  <strong>$string_literal</strong>  The string that contains special characters that need to be modified.
                           Characters that are prepended with a backslash are <return>\x00</return>,  <return>\n</return>, <return>\r</return>, <return>\</return>,  <return>'</return>,
                           <return>"</return> and <return>\x1a</return>.

<comment>Return:</comment>
  <info>string</info>  Returns <strong>$string_literal</strong> with the special characters  noted above prepended with
          backslashes.

<comment>See Also:</comment>
   * <strong>db2_prepare()</strong>


id: db2_exec
type: function
doc:
<comment>Description:</comment>
  Executes an SQL statement directly
    
  
  Executes an SQL statement directly.
  
  If you plan to interpolate PHP variables into the SQL statement, understand that this is one of
  the more common security exposures. Consider calling <strong>db2_prepare()</strong> to prepare an SQL statement
  with parameter markers for input values. Then you can call <strong>db2_execute()</strong> to pass in the input
  values and avoid SQL injection attacks.
  
  If you plan to repeatedly issue the same SQL statement with different parameters, consider calling
  <strong>db2_prepare()</strong> and <strong>db2_execute()</strong> to enable the database server to reuse its access plan and
  increase the efficiency of your database access.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  A valid database connection resource variable as returned from
                         <strong>db2_connect()</strong> or <strong>db2_pconnect()</strong>.
  <info>string  </info>  <strong>$statement </strong>  An SQL statement. The statement cannot contain any parameter markers.
  <info>array   </info>  <strong>$options   </strong>  An associative array containing statement options. You can use this
                         parameter to request a scrollable cursor on database servers that support
                         this functionality.
                         
                         For a description of valid statement options, see  <strong>db2_set_option()</strong>.

<comment>Return:</comment>
  <info>resource</info>  Returns a statement resource if the SQL statement was issued successfully, or <info>false</info> if
            the database failed to execute the SQL statement.

<comment>See Also:</comment>
   * <strong>db2_execute()</strong>
   * <strong>db2_prepare()</strong>


id: db2_execute
type: function
doc:
<comment>Description:</comment>
  Executes a prepared SQL statement
    
  
  <strong>db2_execute()</strong> executes an SQL statement that was prepared by <strong>db2_prepare()</strong>.
  
  If the SQL statement returns a result set, for example, a SELECT statement or a CALL to a stored
  procedure that returns one or more result sets, you can retrieve a row as an array from the <return>stmt</return>
  resource using <strong>db2_fetch_assoc()</strong>, <strong>db2_fetch_both()</strong>, or <strong>db2_fetch_array()</strong>. Alternatively, you can
  use <strong>db2_fetch_row()</strong> to move the result set pointer to the next row and fetch a column at a time
  from that row with <strong>db2_result()</strong>.
  
  Refer to <strong>db2_prepare()</strong> for a brief discussion of the advantages of using <strong>db2_prepare()</strong> and
  <strong>db2_execute()</strong> rather than <strong>db2_exec()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt      </strong>  A prepared statement returned from <strong>db2_prepare()</strong>.
  <info>array   </info>  <strong>$parameters</strong>  An array of input parameters matching any parameter markers contained in
                         the prepared statement.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_exec()</strong>
   * <strong>db2_fetch_array()</strong>
   * <strong>db2_fetch_assoc()</strong>
   * <strong>db2_fetch_both()</strong>
   * <strong>db2_fetch_row()</strong>
   * <strong>db2_prepare()</strong>
   * <strong>db2_result()</strong>


id: db2_fetch_array
type: function
doc:
<comment>Description:</comment>
  Returns an array, indexed by column position, representing a row in a result set
    
  
  Returns an array, indexed by column position, representing a row in a result set. The columns are
  0-indexed.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt      </strong>  A valid <return>stmt</return> resource containing a result set.
  <info>int     </info>  <strong>$row_number</strong>  Requests a specific 1-indexed row from the result set. Passing this
                         parameter results in a PHP warning if the result set uses a forward-only
                         cursor.

<comment>Return:</comment>
  <info>array</info>  Returns a 0-indexed array with column values indexed by the column position representing
         the next or requested row in the result set. Returns <info>false</info> if there are no rows left in the
         result set, or if the row requested by <strong>$row_number</strong> does not exist in the result set.

<comment>See Also:</comment>
   * <strong>db2_fetch_assoc()</strong>
   * <strong>db2_fetch_both()</strong>
   * <strong>db2_fetch_object()</strong>
   * <strong>db2_fetch_row()</strong>
   * <strong>db2_result()</strong>


id: db2_fetch_assoc
type: function
doc:
<comment>Description:</comment>
  Returns an array, indexed by column name, representing a row in a result set
    
  
  Returns an array, indexed by column name, representing a row in a result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt      </strong>  A valid <return>stmt</return> resource containing a result set.
  <info>int     </info>  <strong>$row_number</strong>  Requests a specific 1-indexed row from the result set. Passing this
                         parameter results in a PHP warning if the result set uses a forward-only
                         cursor.

<comment>Return:</comment>
  <info>array</info>  Returns an associative array with column values indexed by the column name representing the
         next or requested row in the result set. Returns <info>false</info> if there are no rows left in the
         result set, or if the row requested by <strong>$row_number</strong> does not exist in the result set.

<comment>See Also:</comment>
   * <strong>db2_fetch_array()</strong>
   * <strong>db2_fetch_both()</strong>
   * <strong>db2_fetch_object()</strong>
   * <strong>db2_fetch_row()</strong>
   * <strong>db2_result()</strong>


id: db2_fetch_both
type: function
doc:
<comment>Description:</comment>
  Returns an array, indexed by both column name and position, representing a row in a result set
    
  
  Returns an array, indexed by both column name and position, representing a row in a result set.
  Note that the row returned by <strong>db2_fetch_both()</strong> requires more memory than the single-indexed arrays
  returned by <strong>db2_fetch_assoc()</strong> or <strong>db2_fetch_array()</strong>.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt      </strong>  A valid <return>stmt</return> resource containing a result set.
  <info>int     </info>  <strong>$row_number</strong>  Requests a specific 1-indexed row from the result set. Passing this
                         parameter results in a PHP warning if the result set uses a forward-only
                         cursor.

<comment>Return:</comment>
  <info>array</info>  Returns an associative array with column values indexed by both the column name and
         0-indexed column number. The array represents the next or requested row in the result set.
         Returns <info>false</info> if there are no rows left in the result set, or if the row requested by
         <strong>$row_number</strong> does not exist in the result set.

<comment>See Also:</comment>
   * <strong>db2_fetch_array()</strong>
   * <strong>db2_fetch_assoc()</strong>
   * <strong>db2_fetch_object()</strong>
   * <strong>db2_fetch_row()</strong>
   * <strong>db2_result()</strong>


id: db2_fetch_object
type: function
doc:
<comment>Description:</comment>
  Returns an object with properties representing columns in the fetched row
    
  
  Returns an object in which each property represents a column returned in the row fetched from a
  result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt      </strong>  A valid <return>stmt</return> resource containing a result set.
  <info>int     </info>  <strong>$row_number</strong>  Requests a specific 1-indexed row from the result set. Passing this
                         parameter results in a PHP warning if the result set uses a forward-only
                         cursor.

<comment>Return:</comment>
  <info>object</info>  Returns an object representing a single row in the result set. The properties of the
          object map to the names of the columns in the result set.
          
          The IBM DB2, Cloudscape, and Apache Derby database servers typically fold column names to
          upper-case, so the object properties will reflect that case.
          
          If your SELECT statement calls a scalar function to modify the value of a column, the
          database servers return the column number as the name of the column in the result set. If
          you prefer a more descriptive column name and object property, you can use the AS clause
          to assign a name to the column in the result set.
          
          Returns <info>false</info> if no row was retrieved.

<comment>See Also:</comment>
   * <strong>db2_fetch_array()</strong>
   * <strong>db2_fetch_assoc()</strong>
   * <strong>db2_fetch_both()</strong>
   * <strong>db2_fetch_row()</strong>
   * <strong>db2_result()</strong>


id: db2_fetch_row
type: function
doc:
<comment>Description:</comment>
  Sets the result set pointer to the next row or requested row
    
  
  Use <strong>db2_fetch_row()</strong> to iterate through a result set, or to point to a specific row in a result set
  if you requested a scrollable cursor.
  
  To retrieve individual fields from the result set, call the <strong>db2_result()</strong> function.
  
  Rather than calling <strong>db2_fetch_row()</strong> and <strong>db2_result()</strong>, most applications will call one of
  <strong>db2_fetch_assoc()</strong>, <strong>db2_fetch_both()</strong>, or <strong>db2_fetch_array()</strong> to advance the result set pointer and
  return a complete row as an array.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt      </strong>  A valid <return>stmt</return> resource.
  <info>int     </info>  <strong>$row_number</strong>  With scrollable cursors, you can request a specific row number in the
                         result set. Row numbering is 1-indexed.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the requested row exists in the result set. Returns <info>false</info> if the requested
        row does not exist in the result set.

<comment>See Also:</comment>
   * <strong>db2_fetch_array()</strong>
   * <strong>db2_fetch_assoc()</strong>
   * <strong>db2_fetch_both()</strong>
   * <strong>db2_fetch_object()</strong>
   * <strong>db2_result()</strong>


id: db2_field_display_size
type: function
doc:
<comment>Description:</comment>
  Returns the maximum number of bytes required to display a column
    
  
  Returns the maximum number of bytes required to display a column in a result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  Specifies a statement resource containing a result set.
  <info>mixed   </info>  <strong>$column</strong>  Specifies the column in the result set. This can either be an integer
                     representing the 0-indexed position of the column, or a string containing the
                     name of the column.

<comment>Return:</comment>
  <info>int</info>  Returns an integer value with the maximum number of bytes required to display the specified
       column. If the column does not exist in the result set, <strong>db2_field_display_size()</strong> returns
       <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_field_name()</strong>
   * <strong>db2_field_num()</strong>
   * <strong>db2_field_precision()</strong>
   * <strong>db2_field_scale()</strong>
   * <strong>db2_field_type()</strong>
   * <strong>db2_field_width()</strong>


id: db2_field_name
type: function
doc:
<comment>Description:</comment>
  Returns the name of the column in the result set
    
  
  Returns the name of the specified column in the result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  Specifies a statement resource containing a result set.
  <info>mixed   </info>  <strong>$column</strong>  Specifies the column in the result set. This can either be an integer
                     representing the 0-indexed position of the column, or a string containing the
                     name of the column.

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the name of the specified column. If the specified column does
          not exist in the result set, <strong>db2_field_name()</strong> returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_field_display_size()</strong>
   * <strong>db2_field_num()</strong>
   * <strong>db2_field_precision()</strong>
   * <strong>db2_field_scale()</strong>
   * <strong>db2_field_type()</strong>
   * <strong>db2_field_width()</strong>


id: db2_field_num
type: function
doc:
<comment>Description:</comment>
  Returns the position of the named column in a result set
    
  
  Returns the position of the named column in a result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  Specifies a statement resource containing a result set.
  <info>mixed   </info>  <strong>$column</strong>  Specifies the column in the result set. This can either be an integer
                     representing the 0-indexed position of the column, or a string containing the
                     name of the column.

<comment>Return:</comment>
  <info>int</info>  Returns an integer containing the 0-indexed position of the named column in the result set.
       If the specified column does not exist in the result set, <strong>db2_field_num()</strong> returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_field_display_size()</strong>
   * <strong>db2_field_name()</strong>
   * <strong>db2_field_precision()</strong>
   * <strong>db2_field_scale()</strong>
   * <strong>db2_field_type()</strong>
   * <strong>db2_field_width()</strong>


id: db2_field_precision
type: function
doc:
<comment>Description:</comment>
  Returns the precision of the indicated column in a result set
    
  
  Returns the precision of the indicated column in a result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  Specifies a statement resource containing a result set.
  <info>mixed   </info>  <strong>$column</strong>  Specifies the column in the result set. This can either be an integer
                     representing the 0-indexed position of the column, or a string containing the
                     name of the column.

<comment>Return:</comment>
  <info>int</info>  Returns an integer containing the precision of the specified column. If the specified column
       does not exist in the result set, <strong>db2_field_precision()</strong> returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_field_display_size()</strong>
   * <strong>db2_field_name()</strong>
   * <strong>db2_field_num()</strong>
   * <strong>db2_field_scale()</strong>
   * <strong>db2_field_type()</strong>
   * <strong>db2_field_width()</strong>


id: db2_field_scale
type: function
doc:
<comment>Description:</comment>
  Returns the scale of the indicated column in a result set
    
  
  Returns the scale of the indicated column in a result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  Specifies a statement resource containing a result set.
  <info>mixed   </info>  <strong>$column</strong>  Specifies the column in the result set. This can either be an integer
                     representing the 0-indexed position of the column, or a string containing the
                     name of the column.

<comment>Return:</comment>
  <info>int</info>  Returns an integer containing the scale of the specified column. If the specified column does
       not exist in the result set, <strong>db2_field_scale()</strong> returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_field_display_size()</strong>
   * <strong>db2_field_name()</strong>
   * <strong>db2_field_num()</strong>
   * <strong>db2_field_precision()</strong>
   * <strong>db2_field_type()</strong>
   * <strong>db2_field_width()</strong>


id: db2_field_type
type: function
doc:
<comment>Description:</comment>
  Returns the data type of the indicated column in a result set
    
  
  Returns the data type of the indicated column in a result set.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  Specifies a statement resource containing a result set.
  <info>mixed   </info>  <strong>$column</strong>  Specifies the column in the result set. This can either be an integer
                     representing the 0-indexed position of the column, or a string containing the
                     name of the column.

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the defined data type of the specified column. If the
          specified column does not exist in the result set, <strong>db2_field_type()</strong> returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_field_display_size()</strong>
   * <strong>db2_field_name()</strong>
   * <strong>db2_field_num()</strong>
   * <strong>db2_field_precision()</strong>
   * <strong>db2_field_scale()</strong>
   * <strong>db2_field_width()</strong>


id: db2_field_width
type: function
doc:
<comment>Description:</comment>
  Returns the width of the current value of the indicated column in a result set
    
  
  Returns the width of the current value of the indicated column in a result set. This is the
  maximum width of the column for a fixed-length data type, or the actual width of the column for a
  variable-length data type.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  Specifies a statement resource containing a result set.
  <info>mixed   </info>  <strong>$column</strong>  Specifies the column in the result set. This can either be an integer
                     representing the 0-indexed position of the column, or a string containing the
                     name of the column.

<comment>Return:</comment>
  <info>int</info>  Returns an integer containing the width of the specified character or binary data type column
       in a result set. If the specified column does not exist in the result set, <strong>db2_field_width()</strong>
       returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_field_display_size()</strong>
   * <strong>db2_field_name()</strong>
   * <strong>db2_field_num()</strong>
   * <strong>db2_field_precision()</strong>
   * <strong>db2_field_scale()</strong>
   * <strong>db2_field_type()</strong>


id: db2_foreign_keys
type: function
doc:
<comment>Description:</comment>
  Returns a result set listing the foreign keys for a table
    
  
  Returns a result set listing the foreign keys for a table.

<comment>Param:</comment>
  <info>resource</info>  <strong>$connection</strong>  A valid connection to an IBM DB2, Cloudscape, or Apache Derby database.
  <info>string  </info>  <strong>$qualifier </strong>  A qualifier for DB2 databases running on OS/390 or z/OS servers. For other
                         databases, pass <info>null</info> or an empty string.
  <info>string  </info>  <strong>$schema    </strong>  The schema which contains the tables. If <strong>$schema</strong> is <info>null</info>,
                         <strong>db2_foreign_keys()</strong> matches the schema for the current connection.
  <info>string  </info>  <strong>$table-name</strong>  The name of the table.

<comment>Return:</comment>
  <info>resource</info>  Returns a statement resource with a result set containing rows describing the foreign
            keys for the specified table. The result set is composed of the following columns:
            Column nameDescriptionPKTABLE_CAT Name of the catalog for the table containing the
            primary key. The value is NULL if this table does not have catalogs. PKTABLE_SCHEM Name
            of the schema for the table containing the primary key. PKTABLE_NAMEName of the table
            containing the primary key.PKCOLUMN_NAMEName of the column containing the primary
            key.FKTABLE_CAT Name of the catalog for the table containing the foreign key. The value
            is NULL if this table does not have catalogs. FKTABLE_SCHEM Name of the schema for the
            table containing the foreign key. FKTABLE_NAMEName of the table containing the foreign
            key.FKCOLUMN_NAMEName of the column containing the foreign key.KEY_SEQ1-indexed position
            of the column in the key.UPDATE_RULE Integer value representing the action applied to
            the foreign key when the SQL operation is UPDATE. DELETE_RULE Integer value representing
            the action applied to the foreign key when the SQL operation is DELETE. FK_NAMEThe name
            of the foreign key.PK_NAMEThe name of the primary key.DEFERRABILITY An integer value
            representing whether the foreign key deferrability is SQL_INITIALLY_DEFERRED,
            SQL_INITIALLY_IMMEDIATE, or SQL_NOT_DEFERRABLE.

<comment>See Also:</comment>
   * <strong>db2_column_privileges()</strong>
   * <strong>db2_columns()</strong>
   * <strong>db2_primary_keys()</strong>
   * <strong>db2_procedure_columns()</strong>
   * <strong>db2_procedures()</strong>
   * <strong>db2_special_columns()</strong>
   * <strong>db2_statistics()</strong>
   * <strong>db2_table_privileges()</strong>
   * <strong>db2_tables()</strong>


id: db2_free_result
type: function
doc:
<comment>Description:</comment>
  Frees resources associated with a result set
    
  
  Frees the system and database resources that are associated with a result set. These resources are
  freed implicitly when a script finishes, but you can call <strong>db2_free_result()</strong> to explicitly free the
  result set resources before the end of the script.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt</strong>  A valid statement resource.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_free_stmt()</strong>


id: db2_free_stmt
type: function
doc:
<comment>Description:</comment>
  Frees resources associated with the indicated statement resource
    
  
  Frees the system and database resources that are associated with a statement resource. These
  resources are freed implicitly when a script finishes, but you can call <strong>db2_free_stmt()</strong> to
  explicitly free the statement resources before the end of the script.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt</strong>  A valid statement resource.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_free_result()</strong>


id: db2_get_option
type: function
doc:
<comment>Description:</comment>
  Retrieves an option value for a statement resource or a connection resource
  
  Retrieves the value of a specified option value for a statement resource  or a connection
  resource.

<comment>Param:</comment>
  <info>resource</info>  <strong>$resource  </strong>  A valid statement resource as returned from <strong>db2_prepare()</strong> or a valid
                         connection resource as returned from <strong>db2_connect()</strong> or <strong>db2_pconnect()</strong>.
  <info>string  </info>  <strong>$option    </strong>  A valid statement or connection options. The following new options are
                         available  as of ibm_db2 version 1.6.0. They provide useful tracking
                         information  that can be set during execution with <strong>db2_get_option()</strong>.  Prior
                         versions of ibm_db2 do not support these new options.  When the value in
                         each option is being set, some servers might not handle  the entire length
                         provided and might truncate the value.  To ensure that the data specified
                         in each option is converted correctly  when transmitted to a host system,
                         use only the characters A through Z,  0 through 9, and the underscore (_)
                         or period (.).  <strong>$userid</strong><return>SQL_ATTR_INFO_USERID</return> - A pointer to a
                         null-terminated  character string used to identify the client user ID sent
                         to the host  database server when using DB2 Connect.  DB2 for z/OS and
                         OS/390 servers support up to a length of 16 characters.  This user-id is
                         not to be confused with the authentication user-id, it is for
                         identification purposes only and is not used for any authorization.
                         <strong>$acctstr</strong><return>SQL_ATTR_INFO_ACCTSTR</return> - A pointer to a null-terminated  character
                         string used to identify the client accounting string sent to the  host
                         database server when using DB2 Connect.  DB2 for z/OS and OS/390 servers
                         support up to a length of 200 characters.  <strong>$applname</strong><return>SQL_ATTR_INFO_APPLNAME</return>
                         - A pointer to a null-terminated  character string used to identify the
                         client application name sent to the  host database server when using DB2
                         Connect.  DB2 for z/OS and OS/390 servers support up to a length of 32
                         characters.  <strong>$wrkstnname</strong><return>SQL_ATTR_INFO_WRKSTNNAME</return> - A pointer to a
                         null-terminated  character string used to identify the client workstation
                         name sent to the  host database server when using DB2 Connect.  DB2 for
                         z/OS and OS/390 servers support up to a length of 18 characters.
                         
                         Prior versions of ibm_db2 do not support these new options.
                         
                         When the value in each option is being set, some servers might not handle
                         the entire length provided and might truncate the value.
                         
                         To ensure that the data specified in each option is converted correctly
                         when transmitted to a host system, use only the characters A through Z,  0
                         through 9, and the underscore (_) or period (.).
                         
                         <return>SQL_ATTR_INFO_USERID</return> - A pointer to a null-terminated  character string
                         used to identify the client user ID sent to the host  database server when
                         using DB2 Connect.  DB2 for z/OS and OS/390 servers support up to a length
                         of 16 characters.  This user-id is not to be confused with the
                         authentication user-id, it is for  identification purposes only and is not
                         used for any authorization.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 16 characters.
                         This user-id is not to be confused with the authentication user-id, it is
                         for  identification purposes only and is not used for any authorization.
                         
                         <return>SQL_ATTR_INFO_ACCTSTR</return> - A pointer to a null-terminated  character string
                         used to identify the client accounting string sent to the  host database
                         server when using DB2 Connect.  DB2 for z/OS and OS/390 servers support up
                         to a length of 200 characters.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 200 characters.
                         
                         <return>SQL_ATTR_INFO_APPLNAME</return> - A pointer to a null-terminated  character string
                         used to identify the client application name sent to the  host database
                         server when using DB2 Connect.  DB2 for z/OS and OS/390 servers support up
                         to a length of 32 characters.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 32 characters.
                         
                         <return>SQL_ATTR_INFO_WRKSTNNAME</return> - A pointer to a null-terminated  character string
                         used to identify the client workstation name sent to the  host database
                         server when using DB2 Connect.  DB2 for z/OS and OS/390 servers support up
                         to a length of 18 characters.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 18 characters.
  <info>        </info>  <strong>$userid    </strong>  <return>SQL_ATTR_INFO_USERID</return> - A pointer to a null-terminated  character string
                         used to identify the client user ID sent to the host  database server when
                         using DB2 Connect.  DB2 for z/OS and OS/390 servers support up to a length
                         of 16 characters.  This user-id is not to be confused with the
                         authentication user-id, it is for  identification purposes only and is not
                         used for any authorization.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 16 characters.
                         This user-id is not to be confused with the authentication user-id, it is
                         for  identification purposes only and is not used for any authorization.
  <info>        </info>  <strong>$acctstr   </strong>  <return>SQL_ATTR_INFO_ACCTSTR</return> - A pointer to a null-terminated  character string
                         used to identify the client accounting string sent to the  host database
                         server when using DB2 Connect.  DB2 for z/OS and OS/390 servers support up
                         to a length of 200 characters.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 200 characters.
  <info>        </info>  <strong>$applname  </strong>  <return>SQL_ATTR_INFO_APPLNAME</return> - A pointer to a null-terminated  character string
                         used to identify the client application name sent to the  host database
                         server when using DB2 Connect.  DB2 for z/OS and OS/390 servers support up
                         to a length of 32 characters.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 32 characters.
  <info>        </info>  <strong>$wrkstnname</strong>  <return>SQL_ATTR_INFO_WRKSTNNAME</return> - A pointer to a null-terminated  character string
                         used to identify the client workstation name sent to the  host database
                         server when using DB2 Connect.  DB2 for z/OS and OS/390 servers support up
                         to a length of 18 characters.
                         
                         DB2 for z/OS and OS/390 servers support up to a length of 18 characters.

<comment>Return:</comment>
  <info>stringfalse</info>  Returns the current setting of the connection attribute provided on success  sau
               <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_connect()</strong>
   * <strong>db2_cursor_type()</strong>
   * <strong>db2_exec()</strong>
   * <strong>db2_set_option()</strong>
   * <strong>db2_pconnect()</strong>
   * <strong>db2_prepare()</strong>


id: db2_last_insert_id
type: function
doc:
<comment>Description:</comment>
  Returns the auto generated ID of the last insert query that successfully 
    executed on this connection
  
  Returns the auto generated ID of the last insert query that successfully  executed on this
  connection.
  
  The result of this function is not affected by any of the following:  A single row INSERT
  statement with a VALUES clause for a table without an identity column.  A multiple row INSERT
  statement with a VALUES clause.  An INSERT statement with a fullselect.  A ROLLBACK TO SAVEPOINT
  statement.
  
  A single row INSERT statement with a VALUES clause for a table without an identity column.
  
  A multiple row INSERT statement with a VALUES clause.
  
  An INSERT statement with a fullselect.
  
  A ROLLBACK TO SAVEPOINT statement.

<comment>Param:</comment>
  <info>resource</info>  <strong>$resource</strong>  A valid connection resource as returned from <strong>db2_connect()</strong>  or
                       <strong>db2_pconnect()</strong>. The value of this parameter cannot be a  statement resource
                       or result set resource.

<comment>Return:</comment>
  <info>string</info>  Returns the auto generated ID of last insert query that successfully  executed on this
          connection.


id: db2_lob_read
type: function
doc:
<comment>Description:</comment>
  Gets a user defined size of LOB files with each invocation
    
  
  Use <strong>db2_lob_read()</strong> to iterate through a specified column of  a result set and retrieve a user
  defined size of LOB data.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt  </strong>  A valid <return>stmt</return> resource containing LOB data.
  <info>int     </info>  <strong>$colnum</strong>  A valid column number in the result set of the <return>stmt</return> resource.
  <info>int     </info>  <strong>$length</strong>  The size of the LOB data to be retrieved from the <return>stmt</return> resource.

<comment>Return:</comment>
  <info>string</info>  Returns the amount of data the user specifies. Returns <info>false</info> if the data cannot be
          retrieved.

<comment>See Also:</comment>
   * <strong>db2_bind_param()</strong>
   * <strong>db2_exec()</strong>
   * <strong>db2_execute()</strong>
   * <strong>db2_fetch_row()</strong>
   * <strong>db2_prepare()</strong>
   * <strong>db2_result()</strong>


id: db2_next_result
type: function
doc:
<comment>Description:</comment>
  Requests the next result set from a stored procedure
    
  
  A stored procedure can return zero or more result sets. While you handle the first result set in
  exactly the same way you would handle the results returned by a simple SELECT statement, to fetch
  the second and subsequent result sets from a stored procedure you must call the <strong>db2_next_result()</strong>
  function and return the result to a uniquely named PHP variable.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt</strong>  A prepared statement returned from <strong>db2_exec()</strong> or <strong>db2_execute()</strong>.

<comment>Return:</comment>
  <info>resource</info>  Returns a new statement resource containing the next result set if the stored procedure
            returned another result set. Returns <info>false</info> if the stored procedure did not return
            another result set.


id: db2_num_fields
type: function
doc:
<comment>Description:</comment>
  Returns the number of fields contained in a result set
    
  
  Returns the number of fields contained in a result set. This is most useful for handling the
  result sets returned by dynamically generated queries, or for result sets returned by stored
  procedures, where your application cannot otherwise know how to retrieve and use the results.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt</strong>  A valid statement resource containing a result set.

<comment>Return:</comment>
  <info>int</info>  Returns an integer value representing the number of fields in the result set associated with
       the specified statement resource. Returns <info>false</info> if the statement resource is not a valid
       input value.

<comment>See Also:</comment>
   * <strong>db2_execute()</strong>
   * <strong>db2_field_display_size()</strong>
   * <strong>db2_field_name()</strong>
   * <strong>db2_field_num()</strong>
   * <strong>db2_field_precision()</strong>
   * <strong>db2_field_scale()</strong>
   * <strong>db2_field_type()</strong>
   * <strong>db2_field_width()</strong>


id: db2_num_rows
type: function
doc:
<comment>Description:</comment>
  Returns the number of rows affected by an SQL statement
    
  
  Returns the number of rows deleted, inserted, or updated by an SQL statement.
  
  To determine the number of rows that will be returned by a SELECT statement, issue SELECT COUNT(*)
  with the same predicates as your intended SELECT statement and retrieve the value.
  
  If your application logic checks the number of rows returned by a SELECT statement and branches if
  the number of rows is 0, consider modifying your application to attempt to return the first row
  with one of <strong>db2_fetch_assoc()</strong>, <strong>db2_fetch_both()</strong>, <strong>db2_fetch_array()</strong>, or <strong>db2_fetch_row()</strong>, and branch
  if the fetch function returns <info>false</info>.
  
  If you issue a SELECT statement using a scrollable cursor, <strong>db2_num_rows()</strong> returns the number of
  rows returned by the SELECT statement. However, the overhead associated with scrollable cursors
  significantly degrades the performance of your application, so if this is the only reason you are
  considering using scrollable cursors, you should use a forward-only cursor and either call SELECT
  COUNT(*) or rely on the <info>bool</info> return value of the fetch functions to achieve the equivalent
  functionality with much better performance.

<comment>Param:</comment>
  <info>resource</info>  <strong>$stmt</strong>  A valid <return>stmt</return> resource containing a result set.

<comment>Return:</comment>
  <info>int</info>  Returns the number of rows affected by the last SQL statement issued by the specified
       statement handle.


id: db2_pclose
type: function
doc:
<comment>Description:</comment>
  Closes a persistent database connection
  
  This function closes a DB2 client connection created with  <strong>db2_pconnect()</strong> and returns the
  corresponding resources  to the database server.    This function is only available on i5/OS in
  response to i5/OS system  administration requests.
  
  This function is only available on i5/OS in response to i5/OS system  administration requests.
  
  If you have a persistent DB2 client connection created with  <strong>db2_pconnect()</strong>, you may use this
  function to close the  connection. To avoid substantial connection performance penalties, this
  function should only be used in rare cases when the persistent connection  has become unresponsive
  or the persistent connection will not be needed for  a long period of time.

<comment>Param:</comment>
  <info></info>  <strong>$connection</strong>  Specifies an active DB2 client connection.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>db2_close()</strong>
   * <strong>db2_pconnect()</strong>


id: db2_pconnect
type: function
doc:
<comment>Description:</comment>
  Returns a persistent connection to a database
    
  
  Returns a persistent connection to an IBM DB2 Universal Database, IBM Cloudscape, or Apache Derby
  database.
  
  For more information on persistent connections, refer to .
  
  Calling <strong>db2_close()</strong> on a persistent connection always returns <info>true</info>, but the underlying DB2 client
  connection remains open and waiting to serve the next matching <strong>db2_pconnect()</strong> request.
  
  Users running version 1.9.0 or later of ibm_db2 should be aware that the extension will perform a
  transaction rollback on persistent connections at the end of a request, thus ending the
  transaction.  This prevents the transaction block from carrying over to the next request which
  uses that connection if script execution ends before the transaction block does.

<comment>Param:</comment>
  <info>string</info>  <strong>$database         </strong>  The database alias in the DB2 client catalog.
  <info>string</info>  <strong>$username         </strong>  The username with which you are connecting to the database.
  <info>string</info>  <strong>$password         </strong>  The password with which you are connecting to the database.
  <info>array </info>  <strong>$options          </strong>  An associative array of connection options that affect the behavior of
                              the connection, where valid array keys include: <strong>$autocommit</strong> Passing
                              the <return>DB2_AUTOCOMMIT_ON</return> value turns autocommit on for this connection
                              handle.  Passing the <return>DB2_AUTOCOMMIT_OFF</return> value turns autocommit off for
                              this connection handle. <strong>$DB2_ATTR_CASE</strong> Passing the <return>DB2_CASE_NATURAL</return>
                              value specifies that column names are returned in natural case.
                              Passing the <return>DB2_CASE_LOWER</return> value specifies that column names are
                              returned in lower case.  Passing the <return>DB2_CASE_UPPER</return> value specifies
                              that column names are returned in upper case. <strong>$CURSOR</strong> Passing the
                              <return>DB2_FORWARD_ONLY</return> value specifies a forward-only cursor for a statement
                              resource. This is the default cursor type and is supported on all
                              database servers.  Passing the <return>DB2_SCROLLABLE</return> value specifies a
                              scrollable cursor for a statement resource. This mode enables random
                              access to rows in a result set, but currently is supported only by IBM
                              DB2 Universal Database.
                              
                              Passing the <return>DB2_AUTOCOMMIT_ON</return> value turns autocommit on for this
                              connection handle.
                              
                              Passing the <return>DB2_AUTOCOMMIT_OFF</return> value turns autocommit off for this
                              connection handle.
                              
                              Passing the <return>DB2_CASE_NATURAL</return> value specifies that column names are
                              returned in natural case.
                              
                              Passing the <return>DB2_CASE_LOWER</return> value specifies that column names are
                              returned in lower case.
                              
                              Passing the <return>DB2_CASE_UPPER</return> value specifies that column names are
                              returned in upper case.
                              
                              Passing the <return>DB2_FORWARD_ONLY</return> value specifies a forward-only cursor for
                              a statement resource. This is the default cursor type and is supported
                              on all database servers.
                              
                              Passing the <return>DB2_SCROLLABLE</return> value specifies a scrollable cursor for a
                              statement resource. This mode enables random access to rows in a
                              result set, but currently is supported only by IBM DB2 Universal
                              Database.
                              
                              The following new option is available in ibm_db2 version 1.7.0  and
                              later.  <strong>$trustedcontext</strong> Passing the DB2_TRUSTED_CONTEXT_ENABLE value
                              turns trusted context  on for this connection handle. This parameter
                              cannot be set using  <strong>db2_set_option()</strong>.  This key works only if the
                              database is cataloged (even if the  database is local), or if you
                              specify the full DSN when you create   the connection.  To catalog the
                              database, use following commands: db2 catalog tcpip node loopback
                              remote \<SERVERNAME&gt; server \<SERVICENAME&gt;
                              db2 catalog database \<LOCALDBNAME&gt; as \<REMOTEDBNAME&gt; at node loopback
                              db2 "update dbm cfg using svcename \<SERVICENAME&gt;"
                              db2set DB2COMM=TCPIP
                              
                              Passing the DB2_TRUSTED_CONTEXT_ENABLE value turns trusted context  on
                              for this connection handle. This parameter cannot be set using
                              <strong>db2_set_option()</strong>.
                              
                              This key works only if the database is cataloged (even if the
                              database is local), or if you specify the full DSN when you create
                              the connection.
                              
                              To catalog the database, use following commands:
                              
                              db2 catalog tcpip node loopback remote \<SERVERNAME&gt; server \<SERVICENAME&gt;
                              db2 catalog database \<LOCALDBNAME&gt; as \<REMOTEDBNAME&gt; at node loopback
                              db2 "update dbm cfg using svcename \<SERVICENAME&gt;"
                              db2set DB2COMM=TCPIP
                              
                              The following new i5/OS options are available in ibm_db2 version 1.5.1
                              and later. Conflicting connection attributes used in conjunction with
                              persistent  connections can produce indeterminate results on i5/OS.
                              Site policies should  be establish for all applications using each
                              persistent connection user  profile. The default DB2_AUTOCOMMIT_ON is
                              suggested when using persistent connections.  <strong>$i5_lib</strong> A character
                              value that indicates the default library that will be  used for
                              resolving unqualified file references. This is not valid  if the
                              connection is using system naming mode. <strong>$i5_naming</strong><return>DB2_I5_NAMING_ON</return>
                              value turns on DB2 UDB CLI iSeries  system naming mode. Files are
                              qualified using the slash (/) delimiter.  Unqualified files are
                              resolved using the library list for the job. <return>DB2_I5_NAMING_OFF</return> value
                              turns off DB2 UDB CLI default  naming mode, which is SQL naming. Files
                              are qualified using the period (.)  delimiter. Unqualified files are
                              resolved using either the default library  or the current user ID.
                              <strong>$i5_commit</strong> The <strong>$i5_commit</strong> attribute should be set before the
                              <strong>db2_pconnect()</strong>. If the value is changed after the  connection has been
                              established, and the connection is to a remote data  source, the
                              change does not take effect until the next successful  <strong>db2_pconnect()</strong>
                              for the connection handle.  The php.ini setting
                              <strong>$ibm_db2.i5_allow_commit</strong>==0  or <return>DB2_I5_TXN_NO_COMMIT</return> is the default,
                              but may be  overridden with the <strong>$i5_commit</strong> option.
                              <return>DB2_I5_TXN_NO_COMMIT</return> - Commitment control is not used.
                              <return>DB2_I5_TXN_READ_UNCOMMITTED</return> - Dirty reads, nonrepeatable  reads, and
                              phantoms are possible. <return>DB2_I5_TXN_READ_COMMITTED</return> - Dirty reads are not
                              possible.  Nonrepeatable reads, and phantoms are possible.
                              <return>DB2_I5_TXN_REPEATABLE_READ</return> - Dirty reads and nonrepeatable  reads are
                              not possible. Phantoms are possible. <return>DB2_I5_TXN_SERIALIZABLE</return> -
                              Transactions are serializable.  Dirty reads, non-repeatable reads, and
                              phantoms are not possible <strong>$i5_query_optimize</strong><return>DB2_FIRST_IO</return> All queries
                              are optimized with the goal of  returning the first page of output as
                              fast as possible. This goal works well  when the output is controlled
                              by a user who is most likely to cancel the query  after viewing the
                              first page of output data. Queries coded with an  OPTIMIZE FOR nnn
                              ROWS clause honor the goal specified by the clause. <return>DB2_ALL_IO</return> All
                              queries are optimized with the goal of running  the entire query to
                              completion in the shortest amount of elapsed time. This is a  good
                              option when the output of a query is being written to a file or
                              report, or  the interface is queuing the output data. Queries coded
                              with an OPTIMIZE FOR nnn  ROWS clause honor the goal specified by the
                              clause. This is the default. <strong>$i5_dbcs_alloc</strong><return>DB2_I5_DBCS_ALLOC_ON</return> value
                              turns on DB2 6X allocation scheme  for DBCS translation column size
                              growth. <return>DB2_I5_DBCS_ALLOC_OFF</return> value turns off DB2 6X allocation scheme
                              for DBCS translation column size growth.   The php.ini setting
                              <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or  <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default,
                              but may be overridden  with the <strong>$i5_dbcs_alloc</strong> option.
                              <strong>$i5_date_fmt</strong><return>DB2_I5_FMT_ISO</return> - The International Organization for
                              Standardization  (ISO) date format yyyy-mm-dd is used. This is the
                              default. <return>DB2_I5_FMT_USA</return> - The United States date format mm/dd/yyyy is
                              used. <return>DB2_I5_FMT_EUR</return> - The European date format dd.mm.yyyy is used.
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard date format
                              yyyy-mm-dd is used.  <return>DB2_I5_FMT_MDY</return> - The date format mm/dd/yyyy is
                              used.  <return>DB2_I5_FMT_DMY</return> - The date format dd/mm/yyyy is used.
                              <return>DB2_I5_FMT_YMD</return> - The date format yy/mm/dd is used. <return>DB2_I5_FMT_JUL</return> -
                              The Julian date format yy/ddd is used. <return>DB2_I5_FMT_JOB</return> - The job
                              default is used. <strong>$i5_date_sep</strong><return>DB2_I5_SEP_SLASH</return> - A slash ( / ) is used
                              as the date separator.  This is the default. <return>DB2_I5_SEP_DASH</return> - A dash
                              ( - ) is used as the date separator. <return>DB2_I5_SEP_PERIOD</return> - A period ( .
                              ) is used as the date  separator. <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is
                              used as the date separator. <return>DB2_I5_SEP_BLANK</return> - A blank is used as the
                              date separator. <return>DB2_I5_SEP_JOB</return> - The job default is used
                              <strong>$i5_time_fmt</strong><return>DB2_I5_FMT_ISO</return> - The International Organization for
                              Standardization (ISO) time format hh.mm.ss is used. This is the
                              default. <return>DB2_I5_FMT_USA</return> - The United States time format  hh:mmxx is
                              used, where xx is AM or PM. <return>DB2_I5_FMT_EUR</return> - The European time format
                              hh.mm.ss  is used. <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard
                              time format hh:mm:ss is used. <return>DB2_I5_FMT_HMS</return> - The hh:mm:ss format is
                              used. <strong>$i5_time_sep</strong><return>DB2_I5_SEP_COLON</return> - A colon ( : ) is used as the time
                              separator. This is the default. <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is
                              used as the time  separator. <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used
                              as the time  separator. <return>DB2_I5_SEP_BLANK</return> - A blank is used as the time
                              separator. <return>DB2_I5_SEP_JOB</return> - The job default is used.
                              <strong>$i5_decimal_sep</strong><return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as  the
                              decimal separator. This is the default. <return>DB2_I5_SEP_COMMA</return> - A comma ( ,
                              ) is used as the  decimal separator. <return>DB2_I5_SEP_JOB</return> - The job default
                              is used.
                              
                              Conflicting connection attributes used in conjunction with persistent
                              connections can produce indeterminate results on i5/OS. Site policies
                              should  be establish for all applications using each persistent
                              connection user  profile. The default DB2_AUTOCOMMIT_ON is suggested
                              when using persistent connections.
                              
                              A character value that indicates the default library that will be
                              used for resolving unqualified file references. This is not valid  if
                              the connection is using system naming mode.
                              
                              <return>DB2_I5_NAMING_ON</return> value turns on DB2 UDB CLI iSeries  system naming
                              mode. Files are qualified using the slash (/) delimiter.  Unqualified
                              files are resolved using the library list for the job.
                              
                              <return>DB2_I5_NAMING_OFF</return> value turns off DB2 UDB CLI default  naming mode,
                              which is SQL naming. Files are qualified using the period (.)
                              delimiter. Unqualified files are resolved using either the default
                              library  or the current user ID.
                              
                              The <strong>$i5_commit</strong> attribute should be set before the  <strong>db2_pconnect()</strong>. If
                              the value is changed after the  connection has been established, and
                              the connection is to a remote data  source, the change does not take
                              effect until the next successful  <strong>db2_pconnect()</strong> for the connection
                              handle.  The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              <return>DB2_I5_TXN_NO_COMMIT</return> - Commitment control is not used.
                              
                              <return>DB2_I5_TXN_READ_UNCOMMITTED</return> - Dirty reads, nonrepeatable  reads, and
                              phantoms are possible.
                              
                              <return>DB2_I5_TXN_READ_COMMITTED</return> - Dirty reads are not possible.
                              Nonrepeatable reads, and phantoms are possible.
                              
                              <return>DB2_I5_TXN_REPEATABLE_READ</return> - Dirty reads and nonrepeatable  reads are
                              not possible. Phantoms are possible.
                              
                              <return>DB2_I5_TXN_SERIALIZABLE</return> - Transactions are serializable.  Dirty reads,
                              non-repeatable reads, and phantoms are not possible
                              
                              <return>DB2_FIRST_IO</return> All queries are optimized with the goal of  returning the
                              first page of output as fast as possible. This goal works well  when
                              the output is controlled by a user who is most likely to cancel the
                              query  after viewing the first page of output data. Queries coded with
                              an  OPTIMIZE FOR nnn ROWS clause honor the goal specified by the
                              clause.
                              
                              <return>DB2_ALL_IO</return> All queries are optimized with the goal of running  the
                              entire query to completion in the shortest amount of elapsed time.
                              This is a  good option when the output of a query is being written to
                              a file or report, or  the interface is queuing the output data.
                              Queries coded with an OPTIMIZE FOR nnn  ROWS clause honor the goal
                              specified by the clause. This is the default.
                              
                              <return>DB2_I5_DBCS_ALLOC_ON</return> value turns on DB2 6X allocation scheme  for DBCS
                              translation column size growth.
                              
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> value turns off DB2 6X allocation scheme  for
                              DBCS translation column size growth.   The php.ini setting
                              <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or  <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default,
                              but may be overridden  with the <strong>$i5_dbcs_alloc</strong> option.
                              
                              The php.ini setting <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default, but may be overridden  with the
                              <strong>$i5_dbcs_alloc</strong> option.
                              
                              <return>DB2_I5_FMT_ISO</return> - The International Organization for Standardization
                              (ISO) date format yyyy-mm-dd is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European date format dd.mm.yyyy is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard date format
                              yyyy-mm-dd is used.
                              
                              <return>DB2_I5_FMT_MDY</return> - The date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_DMY</return> - The date format dd/mm/yyyy is used.
                              
                              <return>DB2_I5_FMT_YMD</return> - The date format yy/mm/dd is used.
                              
                              <return>DB2_I5_FMT_JUL</return> - The Julian date format yy/ddd is used.
                              
                              <return>DB2_I5_FMT_JOB</return> - The job default is used.
                              
                              <return>DB2_I5_SEP_SLASH</return> - A slash ( / ) is used as the date separator.  This
                              is the default.
                              
                              <return>DB2_I5_SEP_DASH</return> - A dash ( - ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the date  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the date separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used
                              
                              <return>DB2_I5_FMT_ISO</return> - The International Organization for  Standardization
                              (ISO) time format hh.mm.ss is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States time format  hh:mmxx is used, where
                              xx is AM or PM.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European time format hh.mm.ss  is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard  time format
                              hh:mm:ss is used.
                              
                              <return>DB2_I5_FMT_HMS</return> - The hh:mm:ss format is used.
                              
                              <return>DB2_I5_SEP_COLON</return> - A colon ( : ) is used as the time  separator. This
                              is the default.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the time separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as  the decimal separator.
                              This is the default.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the  decimal separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
                              
                              The following new i5/OS option is available in ibm_db2 version 1.8.0
                              and later.   <strong>$i5_libl</strong> A character value that indicates the library
                              list that will be used for  resolving unqualified file references.
                              Specify the library list  elements separated by blanks
                              'i5_libl'=&gt;"MYLIB YOURLIB ANYLIB".   i5_libl calls
                              qsys2/qcmdexc('cmd',cmdlen), which is only available  in i5/OS V5R4
                              and later.
                              
                              A character value that indicates the library list that will be used
                              for  resolving unqualified file references. Specify the library list
                              elements separated by blanks 'i5_libl'=&gt;"MYLIB YOURLIB ANYLIB".
                              i5_libl calls qsys2/qcmdexc('cmd',cmdlen), which is only available  in
                              i5/OS V5R4 and later.
                              
                              i5_libl calls qsys2/qcmdexc('cmd',cmdlen), which is only available  in
                              i5/OS V5R4 and later.
  <info>      </info>  <strong>$autocommit       </strong>  Passing the <return>DB2_AUTOCOMMIT_ON</return> value turns autocommit on for this
                              connection handle.
                              
                              Passing the <return>DB2_AUTOCOMMIT_OFF</return> value turns autocommit off for this
                              connection handle.
  <info>      </info>  <strong>$DB2_ATTR_CASE    </strong>  Passing the <return>DB2_CASE_NATURAL</return> value specifies that column names are
                              returned in natural case.
                              
                              Passing the <return>DB2_CASE_LOWER</return> value specifies that column names are
                              returned in lower case.
                              
                              Passing the <return>DB2_CASE_UPPER</return> value specifies that column names are
                              returned in upper case.
  <info>      </info>  <strong>$CURSOR           </strong>  Passing the <return>DB2_FORWARD_ONLY</return> value specifies a forward-only cursor for
                              a statement resource. This is the default cursor type and is supported
                              on all database servers.
                              
                              Passing the <return>DB2_SCROLLABLE</return> value specifies a scrollable cursor for a
                              statement resource. This mode enables random access to rows in a
                              result set, but currently is supported only by IBM DB2 Universal
                              Database.
  <info>      </info>  <strong>$trustedcontext   </strong>  Passing the DB2_TRUSTED_CONTEXT_ENABLE value turns trusted context  on
                              for this connection handle. This parameter cannot be set using
                              <strong>db2_set_option()</strong>.
                              
                              This key works only if the database is cataloged (even if the
                              database is local), or if you specify the full DSN when you create
                              the connection.
                              
                              To catalog the database, use following commands:
                              
                              db2 catalog tcpip node loopback remote \<SERVERNAME&gt; server \<SERVICENAME&gt;
                              db2 catalog database \<LOCALDBNAME&gt; as \<REMOTEDBNAME&gt; at node loopback
                              db2 "update dbm cfg using svcename \<SERVICENAME&gt;"
                              db2set DB2COMM=TCPIP
  <info>      </info>  <strong>$i5_lib           </strong>  A character value that indicates the default library that will be
                              used for resolving unqualified file references. This is not valid  if
                              the connection is using system naming mode.
  <info>      </info>  <strong>$i5_naming        </strong>  <return>DB2_I5_NAMING_ON</return> value turns on DB2 UDB CLI iSeries  system naming
                              mode. Files are qualified using the slash (/) delimiter.  Unqualified
                              files are resolved using the library list for the job.
                              
                              <return>DB2_I5_NAMING_OFF</return> value turns off DB2 UDB CLI default  naming mode,
                              which is SQL naming. Files are qualified using the period (.)
                              delimiter. Unqualified files are resolved using either the default
                              library  or the current user ID.
  <info>      </info>  <strong>$i5_commit        </strong>  The <strong>$i5_commit</strong> attribute should be set before the  <strong>db2_pconnect()</strong>. If
                              the value is changed after the  connection has been established, and
                              the connection is to a remote data  source, the change does not take
                              effect until the next successful  <strong>db2_pconnect()</strong> for the connection
                              handle.  The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              The php.ini setting <strong>$ibm_db2.i5_allow_commit</strong>==0  or
                              <return>DB2_I5_TXN_NO_COMMIT</return> is the default, but may be  overridden with the
                              <strong>$i5_commit</strong> option.
                              
                              <return>DB2_I5_TXN_NO_COMMIT</return> - Commitment control is not used.
                              
                              <return>DB2_I5_TXN_READ_UNCOMMITTED</return> - Dirty reads, nonrepeatable  reads, and
                              phantoms are possible.
                              
                              <return>DB2_I5_TXN_READ_COMMITTED</return> - Dirty reads are not possible.
                              Nonrepeatable reads, and phantoms are possible.
                              
                              <return>DB2_I5_TXN_REPEATABLE_READ</return> - Dirty reads and nonrepeatable  reads are
                              not possible. Phantoms are possible.
                              
                              <return>DB2_I5_TXN_SERIALIZABLE</return> - Transactions are serializable.  Dirty reads,
                              non-repeatable reads, and phantoms are not possible
  <info>      </info>  <strong>$i5_query_optimize</strong>  <return>DB2_FIRST_IO</return> All queries are optimized with the goal of  returning the
                              first page of output as fast as possible. This goal works well  when
                              the output is controlled by a user who is most likely to cancel the
                              query  after viewing the first page of output data. Queries coded with
                              an  OPTIMIZE FOR nnn ROWS clause honor the goal specified by the
                              clause.
                              
                              <return>DB2_ALL_IO</return> All queries are optimized with the goal of running  the
                              entire query to completion in the shortest amount of elapsed time.
                              This is a  good option when the output of a query is being written to
                              a file or report, or  the interface is queuing the output data.
                              Queries coded with an OPTIMIZE FOR nnn  ROWS clause honor the goal
                              specified by the clause. This is the default.
  <info>      </info>  <strong>$i5_dbcs_alloc    </strong>  <return>DB2_I5_DBCS_ALLOC_ON</return> value turns on DB2 6X allocation scheme  for DBCS
                              translation column size growth.
                              
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> value turns off DB2 6X allocation scheme  for
                              DBCS translation column size growth.   The php.ini setting
                              <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or  <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default,
                              but may be overridden  with the <strong>$i5_dbcs_alloc</strong> option.
                              
                              The php.ini setting <strong>$ibm_db2.i5_dbcs_alloc</strong>==0 or
                              <return>DB2_I5_DBCS_ALLOC_OFF</return> is the default, but may be overridden  with the
                              <strong>$i5_dbcs_alloc</strong> option.
  <info>      </info>  <strong>$i5_date_fmt      </strong>  <return>DB2_I5_FMT_ISO</return> - The International Organization for Standardization
                              (ISO) date format yyyy-mm-dd is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European date format dd.mm.yyyy is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard date format
                              yyyy-mm-dd is used.
                              
                              <return>DB2_I5_FMT_MDY</return> - The date format mm/dd/yyyy is used.
                              
                              <return>DB2_I5_FMT_DMY</return> - The date format dd/mm/yyyy is used.
                              
                              <return>DB2_I5_FMT_YMD</return> - The date format yy/mm/dd is used.
                              
                              <return>DB2_I5_FMT_JUL</return> - The Julian date format yy/ddd is used.
                              
                              <return>DB2_I5_FMT_JOB</return> - The job default is used.
  <info>      </info>  <strong>$i5_date_sep      </strong>  <return>DB2_I5_SEP_SLASH</return> - A slash ( / ) is used as the date separator.  This
                              is the default.
                              
                              <return>DB2_I5_SEP_DASH</return> - A dash ( - ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the date  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the date separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the date separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used
  <info>      </info>  <strong>$i5_time_fmt      </strong>  <return>DB2_I5_FMT_ISO</return> - The International Organization for  Standardization
                              (ISO) time format hh.mm.ss is used. This is the default.
                              
                              <return>DB2_I5_FMT_USA</return> - The United States time format  hh:mmxx is used, where
                              xx is AM or PM.
                              
                              <return>DB2_I5_FMT_EUR</return> - The European time format hh.mm.ss  is used.
                              
                              <return>DB2_I5_FMT_JIS</return> - The Japanese Industrial Standard  time format
                              hh:mm:ss is used.
                              
                              <return>DB2_I5_FMT_HMS</return> - The hh:mm:ss format is used.
  <info>      </info>  <strong>$i5_time_sep      </strong>  <return>DB2_I5_SEP_COLON</return> - A colon ( : ) is used as the time  separator. This
                              is the default.
                              
                              <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the time  separator.
                              
                              <return>DB2_I5_SEP_BLANK</return> - A blank is used as the time separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
  <info>      </info>  <strong>$i5_decimal_sep   </strong>  <return>DB2_I5_SEP_PERIOD</return> - A period ( . ) is used as  the decimal separator.
                              This is the default.
                              
                              <return>DB2_I5_SEP_COMMA</return> - A comma ( , ) is used as the  decimal separator.
                              
                              <return>DB2_I5_SEP_JOB</return> - The job default is used.
  <info>      </info>  <strong>$i5_libl          </strong>  A character value that indicates the library list that will be used
                              for  resolving unqualified file references. Specify the library list
                              elements separated by blanks 'i5_libl'=&gt;"MYLIB YOURLIB ANYLIB".
                              i5_libl calls qsys2/qcmdexc('cmd',cmdlen), which is only available  in
                              i5/OS V5R4 and later.
                              
                              i5_libl calls qsys2/qcmdexc('cmd',cmdlen), which is only available  in
                              i5/OS V5R4 and later.

<comment>Return:</comment>
  <info>resource</info>  Returns a connection handle resource if the connection attempt is successful.
            <strong>db2_pconnect()</strong> tries to reuse an existing connection resource that exactly matches the
            <strong>$database</strong>, <strong>$username</strong>, and <strong>$password</strong> parameters. If the connection attempt fails,
            <strong>db2_pconnect()</strong> returns <info>false</info>.

<comment>See Also:</comment>
   * <strong>db2_connect()</strong>


