# php_manual

id: MongoDB\Driver\WriteConcern
type: class
doc:
<comment>Description:</comment>
  <class>MongoDB\Driver\WriteConcern</class> describes the level of acknowledgement requested from MongoDB for
  write operations to a standalone <return>mongod</return> or to replica sets or to sharded clusters. In sharded
  clusters, <return>mongos</return> instances will pass the write concern on to the shards.


id: MongoDB\Driver\WriteConcern::MAJORITY
type: constant
doc:
<comment>Description:</comment>
  Majority of all the members in the set; arbiters, non-voting members, passive members, hidden
  members and delayed members are all included in the definition of majority write concern.


id: MongoDB\Driver\WriteConcern::__construct
type: function
doc:
<comment>Description:</comment>
  Create a new WriteConcern
  
  Constructs a new <class>MongoDB\Driver\WriteConcern</class>, which is an immutable value object.

<comment>Param:</comment>
  <info>stringint</info>  <strong>$w       </strong>  Write concernValueDescription1 Requests acknowledgement that the write
                        operation has propagated to the standalone <return>mongod</return> or the primary in a
                        replica set. This is the default write concern for MongoDB. 0 Requests no
                        acknowledgment of the write operation. However, this may return information
                        about socket exceptions and networking errors to the application. \<integer greater than 1&gt; Numbers greater than 1 are valid only for replica sets to request acknowledgement from specified number of members, including the primary. <info>MongoDB\Driver\WriteConcern::MAJORITY</info> Requests acknowledgment that write operations have propagated to the majority of voting nodes, including the primary, and have been written to the on-disk journal for these nodes.  Prior to MongoDB 3.0, this refers to the majority of replica set members (not just voting nodes). string A string value is interpereted as a tag set. Requests acknowledgement that the write operations have propagated to a replica set member with the specified tag.
                        
                        Requests acknowledgment that write operations have propagated to the
                        majority of voting nodes, including the primary, and have been written to
                        the on-disk journal for these nodes.
                        
                        Prior to MongoDB 3.0, this refers to the majority of replica set members
                        (not just voting nodes).
  <info>int      </info>  <strong>$wtimeout</strong>  How long to wait (in milliseconds) for secondaries before failing.
                        
                        <return>wtimeout</return> causes write operations to return with an error (<class>WriteConcernError</class>)
                        after the specified limit, even if the required write concern will
                        eventually succeed. When these write operations return, MongoDB does not
                        undo successful data modifications performed before the write concern
                        exceeded the <return>wtimeout</return> time limit.
                        
                        If specified, <return>wtimeout</return> must be a signed 64-bit integer greater than or equal
                        to zero.
                        
                        Write concern timeoutValueDescription0Block indefinitely. This is the
                        default.\<integer greater than 0&gt; Milliseconds to wait until returning.
  <info>bool     </info>  <strong>$journal </strong>  Wait until mongod has applied the write to the journal.

<comment>See Also:</comment>
   * Write Concern reference


id: MongoDB\Driver\WriteConcern::bsonSerialize
type: function
doc:
<comment>Description:</comment>
  Returns an object for BSON serialization

<comment>Return:</comment>
  <info>object</info>  Returns an object for serializing the WriteConcern as BSON.

<comment>See Also:</comment>
   * MongoDB\BSON\Serializable::bsonSerialize
   * Write Concern reference


id: MongoDB\Driver\WriteConcern::getJournal
type: function
doc:
<comment>Description:</comment>
  Returns the WriteConcern's "journal" option

<comment>Return:</comment>
  <info>boolnull</info>  Returns the WriteConcern's "journal" option.

<comment>See Also:</comment>
   * Write Concern reference


id: MongoDB\Driver\WriteConcern::getW
type: function
doc:
<comment>Description:</comment>
  Returns the WriteConcern's "w" option

<comment>Return:</comment>
  <info>stringintnull</info>  Returns the WriteConcern's "w" option.

<comment>See Also:</comment>
   * Write Concern reference


id: MongoDB\Driver\WriteConcern::getWtimeout
type: function
doc:
<comment>Description:</comment>
  Returns the WriteConcern's "wtimeout" option

<comment>Return:</comment>
  <info>intMongoDB\BSON\Int64</info>  Returns the WriteConcern's "wtimeout" option.

<comment>See Also:</comment>
   * Write Concern reference


id: MongoDB\Driver\WriteConcern::isDefault
type: function
doc:
<comment>Description:</comment>
  Checks if this is the default write concern
  
  Returns whether this is the default write concern (i.e. no options are specified). This method is
  primarily intended to be used in conjunction with MongoDB\Driver\Manager::getWriteConcern to
  determine whether the Manager has been constructed without any write concern options.
  
  The driver will not include a default write concern in its write operations (e.g.
  MongoDB\Driver\Manager::executeBulkWrite) in order to allow the server to apply its own default,
  which may have been modified. Libraries that access the Manager's write concern to include it in
  their own write commands should use this method to ensure that default write concerns are left
  unset.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if this is the default write concern and <info>false</info> otherwise.

<comment>See Also:</comment>
   * MongoDB\Driver\Manager::getWriteConcern
   * Modify Default Write Concern in the MongoDB manual
   * Write Concern reference


id: MongoDB\Driver\WriteConcern::serialize
type: function
doc:
<comment>Description:</comment>
  Serialize a WriteConcern

<comment>Return:</comment>
  <info>string</info>  Returns the serialized representation of the <class>MongoDB\Driver\WriteConcern</class>.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteConcern::unserialize
   * <strong>serialize()</strong>
   * Serializing Objects


id: MongoDB\Driver\WriteConcern::unserialize
type: function
doc:
<comment>Description:</comment>
  Unserialize a WriteConcern

<comment>Param:</comment>
  <info>string</info>  <strong>$serialized</strong>  The serialized <class>MongoDB\Driver\WriteConcern</class>.

<comment>Return:</comment>
  <info>void</info>  Returns the unserialized <class>MongoDB\Driver\WriteConcern</class>.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteConcern::serialize
   * <strong>unserialize()</strong>
   * Serializing Objects


id: MongoDB\Driver\WriteConcernError
type: class
doc:
<comment>Description:</comment>
  The <class>MongoDB\Driver\WriteConcernError</class> class encapsulates information about a write concern error
  and may be returned by MongoDB\Driver\WriteResult::getWriteConcernError.


id: MongoDB\Driver\WriteConcernError::getCode
type: function
doc:
<comment>Description:</comment>
  Returns the WriteConcernError's error code

<comment>Return:</comment>
  <info>int</info>  Returns the WriteConcernError's error code.

<comment>See Also:</comment>
   * Write Concern reference


id: MongoDB\Driver\WriteConcernError::getInfo
type: function
doc:
<comment>Description:</comment>
  Returns metadata document for the WriteConcernError

<comment>Return:</comment>
  <info>objectnull</info>  Returns the metadata document for the WriteConcernError, or <info>null</info> if no metadata is
              available.

<comment>See Also:</comment>
   * Write Concern reference


id: MongoDB\Driver\WriteConcernError::getMessage
type: function
doc:
<comment>Description:</comment>
  Returns the WriteConcernError's error message

<comment>Return:</comment>
  <info>string</info>  Returns the WriteConcernError's error message.

<comment>See Also:</comment>
   * Write Concern reference


id: MongoDB\Driver\WriteError
type: class
doc:
<comment>Description:</comment>
  The <class>MongoDB\Driver\WriteError</class> class encapsulates information about a write error and may be
  returned as an array element from MongoDB\Driver\WriteResult::getWriteErrors.


id: MongoDB\Driver\WriteError::getCode
type: function
doc:
<comment>Description:</comment>
  Returns the WriteError's error code

<comment>Return:</comment>
  <info>int</info>  Returns the WriteError's error code.


id: MongoDB\Driver\WriteError::getIndex
type: function
doc:
<comment>Description:</comment>
  Returns the index of the write operation corresponding to this WriteError

<comment>Return:</comment>
  <info>int</info>  Returns the index of the write operation (from <class>MongoDB\Driver\BulkWrite</class>) corresponding to
       this WriteError.

<comment>See Also:</comment>
   * <class>MongoDB\Driver\BulkWrite</class>


id: MongoDB\Driver\WriteError::getInfo
type: function
doc:
<comment>Description:</comment>
  Returns metadata document for the WriteError

<comment>Return:</comment>
  <info>objectnull</info>  Returns the metadata document for the WriteError, or <info>null</info> if no metadata is available.


id: MongoDB\Driver\WriteError::getMessage
type: function
doc:
<comment>Description:</comment>
  Returns the WriteError's error message

<comment>Return:</comment>
  <info>string</info>  Returns the WriteError's error message.


id: MongoDB\Driver\WriteResult
type: class
doc:
<comment>Description:</comment>
  The <class>MongoDB\Driver\WriteResult</class> class encapsulates information about an executed
  <class>MongoDB\Driver\BulkWrite</class> and may be returned by MongoDB\Driver\Manager::executeBulkWrite.


id: MongoDB\Driver\WriteResult::getDeletedCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of documents deleted

<comment>Return:</comment>
  <info>intnull</info>  Returns the number of documents deleted, or <info>null</info> if the write was not acknowledged.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteResult::isAcknowledged


id: MongoDB\Driver\WriteResult::getInsertedCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of documents inserted (excluding upserts)

<comment>Return:</comment>
  <info>intnull</info>  Returns the number of documents inserted (excluding upserts), or <info>null</info> if the write was
           not acknowledged.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteResult::isAcknowledged


id: MongoDB\Driver\WriteResult::getMatchedCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of documents selected for update
  
  If the update operation results in no change to the document (e.g. setting the value of a field to
  its current value), the matched count may be greater than the value returned by
  MongoDB\Driver\WriteResult::getModifiedCount.

<comment>Return:</comment>
  <info>intnull</info>  Returns the number of documents selected for update, or <info>null</info> if the write was not
           acknowledged.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteResult::getModifiedCount
   * MongoDB\Driver\WriteResult::isAcknowledged


id: MongoDB\Driver\WriteResult::getModifiedCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of existing documents updated
  
  If the update operation results in no change to the document (e.g. setting the value of a field to
  its current value), the modified count may be less than the value returned by
  MongoDB\Driver\WriteResult::getMatchedCount.

<comment>Return:</comment>
  <info>intnull</info>  Returns the number of existing documents updated, or <info>null</info> if the write was not
           acknowledged.
           
           The modified count is not available on versions of MongoDB before 2.6, which used the
           legacy wire protocol version (i.e. OP_UPDATE). If this is the case, the modified count
           will also be <info>null</info>.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteResult::getMatchedCount
   * MongoDB\Driver\WriteResult::isAcknowledged


id: MongoDB\Driver\WriteResult::getServer
type: function
doc:
<comment>Description:</comment>
  Returns the server associated with this write result
  
  Returns the <class>MongoDB\Driver\Server</class> associated with this write result. This is the server that
  executed the <class>MongoDB\Driver\BulkWrite</class>.

<comment>Return:</comment>
  <info>MongoDB\Driver\Server</info>  Returns the <class>MongoDB\Driver\Server</class> associated with this write result.

<comment>See Also:</comment>
   * <class>MongoDB\Driver\Server</class>


id: MongoDB\Driver\WriteResult::getUpsertedCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of documents inserted by an upsert

<comment>Return:</comment>
  <info>intnull</info>  Returns the number of documents inserted by an upsert.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteResult::getUpsertedIds
   * MongoDB\Driver\WriteResult::isAcknowledged


id: MongoDB\Driver\WriteResult::getUpsertedIds
type: function
doc:
<comment>Description:</comment>
  Returns an array of identifiers for upserted documents

<comment>Return:</comment>
  <info>array</info>  Returns an array of identifiers (i.e. <return>"_id"</return> field values) for upserted documents. The array
         keys will correspond to the index of the write operation (from <class>MongoDB\Driver\BulkWrite</class>)
         responsible for the upsert.

<comment>See Also:</comment>
   * MongoDB\Driver\WriteResult::getUpsertedCount
   * MongoDB\Driver\WriteResult::isAcknowledged


id: MongoDB\Driver\WriteResult::getWriteConcernError
type: function
doc:
<comment>Description:</comment>
  Returns any write concern error that occurred

<comment>Return:</comment>
  <info>MongoDB\Driver\WriteConcernErrornull</info>  Returns a <class>MongoDB\Driver\WriteConcernError</class> if a write
                                        concern error was encountered during the write operation,
                                        and <info>null</info> otherwise.

<comment>See Also:</comment>
   * <class>MongoDB\Driver\WriteConcern</class>
   * Write Concern reference


id: MongoDB\Driver\WriteResult::getWriteErrors
type: function
doc:
<comment>Description:</comment>
  Returns any write errors that occurred

<comment>Return:</comment>
  <info>array</info>  Returns an array of <class>MongoDB\Driver\WriteError</class> objects for any write errors encountered
         during the write operation. The array will be empty if no write errors occurred.

<comment>See Also:</comment>
   * <class>MongoDB\Driver\WriteError</class>


id: MongoDB\Driver\WriteResult::isAcknowledged
type: function
doc:
<comment>Description:</comment>
  Returns whether the write was acknowledged
  
  If the write is acknowledged, other count fields will be available on the
  <class>MongoDB\Driver\WriteResult</class> object.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the write was acknowledged, and <info>false</info> otherwise.

<comment>See Also:</comment>
   * <class>MongoDB\Driver\WriteConcern</class>
   * Write Concern reference


id: MongoDate
type: class
doc:
<comment>Description:</comment>
  Represent date objects for the database.  This class should be used to save dates to the database
  and to query for dates.  For example:
  
  MongoDB stores dates as milliseconds past the epoch.  This means that dates  do not contain
  timezone information.  Timezones must be stored in a separate field if needed.  Second, this means
  that any precision beyond milliseconds will be lost when the document is sent to/from the
  database.


id: MongoDate::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new date
  
  Creates a new date.  If no parameters are given, the current time is used.

<comment>Param:</comment>
  <info>int</info>  <strong>$sec </strong>  Number of seconds since the epoch (i.e. 1 Jan 1970 00:00:00.000 UTC).
  <info>int</info>  <strong>$usec</strong>  Microseconds. Please be aware though that MongoDB's resolution is milliseconds and not
              microseconds, which means this value will be truncated to millisecond resolution.

<comment>Return:</comment>
  <info>unknown</info>  Returns this new date.

<comment>See Also:</comment>
   * MongoDate::__toString


id: MongoDate::__toString
type: function
doc:
<comment>Description:</comment>
  Returns a string representation of this date
  
  Returns a string representation of this date, similar to the representation returned by
  <strong>microtime()</strong>.

<comment>Return:</comment>
  <info>string</info>  This date.


id: MongoDate::toDateTime
type: function
doc:
<comment>Description:</comment>
  Returns a DateTime object representing this date
  
  Returns the <class>DateTime</class> representation of this date. The returned <class>DateTime</class> will use the UTC time
  zone.

<comment>Return:</comment>
  <info>DateTime</info>  This date as a <class>DateTime</class> object.


id: MongoDeleteBatch
type: class
doc:
<comment>Description:</comment>
  Constructs a batch of DELETE operations. See <class>MongoWriteBatch</class>.


id: MongoDeleteBatch::__construct
type: function
doc:
<comment>Description:</comment>
  Description
  
  Constructs a batch of DELETE operations. See <class>MongoWriteBatch</class>.

<comment>Param:</comment>
  <info>MongoCollection</info>  <strong>$collection   </strong>  Clasa <class>MongoCollection</class> asupra căreia se execută setul.
                                   Gradele ei de participare vor fi
                                   copiate și folosite ca implicite dacă nu au fost furnizate cu
                                   <strong>$write_options</strong>
                                   sau în timpul executării MongoWriteBatch::execute.
  <info>array          </info>  <strong>$write_options</strong>  Un tablou cu Opiuni de Înscriere.
                                   cheiaînsemnătatea valoriiw (int|string)Valoare a Gradului de
                                   participare la înscrierewtimeout (int)Timpul maximal de așteptare
                                   a replicăriiorderedDetermină dacă MongoDB trebuie să aplice acest
                                   set
                                   în ordinea stabilită. Înscrierile ordonate se execută secvențial
                                   (adică câte o
                                   înregistrare) și execuția se întrerupe după prima eroare.
                                   Înscrierile neordonate
                                   pot fi executate în paralel și execuția nu se va stopa după prima
                                   eroare.
                                   Valoarea implicită este <info>true</info>j (bool)Așteaptă jurnalizarea pe
                                   primar. Această valoare e nerecomandată, utilizați WriteConcern
                                   în locfsync (bool)Așteaptă fsync pe primar. Această valoare e
                                   nerecomandată, utilizați WriteConcern în loc

<comment>Return:</comment>
  <info>unknown</info>  A new MongoDeleteBatch.


id: MongoDuplicateKeyException
type: class
doc:
<comment>Description:</comment>
  Thrown when attempting to insert a document into a collection which already contains the same
  values for the unique keys.


id: MongoException
type: class
doc:
<comment>Description:</comment>
  Default Mongo exception.
  
  This covers a bunch of different error conditions that may eventually be moved to more specific
  exceptions, but will always extend  <class>MongoException</class>.
  
  <return>The MongoSomething object has not been correctly initialized by its constructor</return>
  
  Code: 0
  
  Probably your Mongo object is not connected to a database server.
  
  <return>zero-length keys are not allowed, did you use $ with double quotes?</return>
  
  Code: 1
  
  You tried to save "" as a key.  You generally should not do this.  "" can  mess up subobject
  access and is used by MongoDB internally.  However, if  you really want, you can set
  mongo.allow_empty_keys  to true in your php.ini file to override this sanity check.  If you
  override this, it is highly recommended that you set error checking to  strict to avoid string
  interpolation errors.
  
  <return>'.' not allowed in key: \<key&gt;</return>
  
  Code: 2
  
  You attempted to write a key with '.' in it, which is prohibited.
  
  <return>insert too large: \<size&gt;, max: \<max&gt;</return>
  
  Code: 3
  
  You're attempting to send too much data to the database at once: the database will only accept
  inserts up to a certain size (currently 16 MB).
  
  <return>no elements in doc</return>
  
  Code: 4
  
  You're attempting to save a document with no fields.
  
  <return>size of BSON doc is \<size&gt; bytes, max \<max&gt;MB</return>
  
  Code: 5
  
  You're attempting to save a document that is larger than MongoDB can save.
  
  <return>no documents given</return>
  
  Code: 6
  
  You're attempting to batch insert an empty array of documents.
  
  <return>MongoCollection::group takes an array, object, or MongoCode key</return>
  
  Code: 7
  
  Wrong type parameter send to <strong>MongoCollection::group()</strong>.
  
  <return>field names must be strings</return>
  
  Code: 8
  
  You should format field selectors as  <return>array("field1" =&gt; 1, "field2" =&gt; 1, ..., "fieldN"
  =&gt; 1)</return>.
  
  <return>invalid regex</return>
  
  Code: 9
  
  The regex passed to <class>MongoRegex</class> is not of the  correct form.
  
  <return>MongoDBRef::get: $ref field must be a string</return>
  
  Code: 10
  
  <return>MongoDBRef::get: $db field must be a string</return>
  
  Code: 11
  
  <return>non-utf8 string: \<str&gt;</return>
  
  Code: 12
  
  This error occurs if you attempt to send a non-utf8 string to the  database.  All strings going
  into the database should be UTF8. See php.ini options for the transition option of quieting this
  exception.
  
  <return>mutex error: \<err&gt;</return>
  
  Code: 13
  
  The driver uses mutexes for synchronizing requests and responses in  multithreaded environments.
  This is a fairly serious error and may not have a stack trace.  It's unusual and should be
  reported to maintainers with any system information and steps to reproduce that you can provide.
  
  <return>index name too long: \<len&gt;, max \<max&gt; characters</return>
  
  Code: 14
  
  Indexes with names longer than 128 characters cannot be created.  If you get this error, you
  should use  <strong>MongoCollection::ensureIndex()</strong>'s "name" option to  create a shorter name for your
  index.


id: MongoExecutionTimeoutException
type: class
doc:
<comment>Description:</comment>
  Thrown when a operation times out server side (i.e. in MongoDB).
  
  To configure the operation timeout threshold, use MongoCursor::maxTimeMS or the <return>"maxTimeMS"</return>
  command option.


id: MongoGridFS
type: class
doc:
<comment>Description:</comment>
  Utilities for storing and retrieving files from the database.
  
  GridFS is a storage specification all supported drivers implement.  Basically, it defines two
  collections: <return>files</return>, for file  metadata, and <return>chunks</return>, for file content.  If the file is  large, it
  will automatically be split into smaller chunks and each chunk  will be saved as a document in the
  chunks collection.
  
  Each document in the files collection contains the filename, upload date,  and md5 hash.  It also
  contains a unique <return>_id</return> field, which can be used to query the chunks collection for the file's
  content.  Each  document in the chunks collection contains a chunk of binary data, a  <return>files_id</return>
  field that matches its file's  <return>_id</return>, and the position of this chunk in the overall file.
  
  For example, the files document is something like:  123456789, "filename" => "foo.txt",
  "chunkSize" => 3, "length" => 12);
  ?>
  ]]> and the chunks documents look like:  123456789, "n" => 0, "data" => new MongoBinData("abc"));
  array("files_id" => 123456789, "n" => 1, "data" => new MongoBinData("def"));
  array("files_id" => 123456789, "n" => 2, "data" => new MongoBinData("ghi"));
  array("files_id" => 123456789, "n" => 3, "data" => new MongoBinData("jkl"));
  ?>
  ]]> Of course, the default chunk size is thousands of bytes, but that makes an unwieldy example.


id: MongoGridFS::__construct
type: function
doc:
<comment>Description:</comment>
  Creates new file collections
  
  Files as stored across two collections, the first containing file meta information, the second
  containing chunks of the actual file. By default, fs.files and fs.chunks are the collection names
  used.
  
  Use one argument to specify a prefix other than "fs":
   uses myfiles.files and myfiles.chunks collections.

<comment>Param:</comment>
  <info>MongoDB</info>  <strong>$db   </strong>  Database.
  <info>       </info>  <strong>$files</strong>  Optional collection name prefix.


id: MongoGridFS::delete
type: function
doc:
<comment>Description:</comment>
  Remove a file and its chunks from the database
  
  MongoGridFS::delete is a convenience method for calling MongoGridFS::remove with specific
  <strong>$criteria</strong> and default <strong>$options</strong> parameters.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$id</strong>  <return>_id</return> of the file to remove.

<comment>Return:</comment>
  <info>boolarray</info>  Returns an array containing the status of the removal (with respect to the <return>files</return>
             collection) if a write concern is applied. Otherwise, returns <info>true</info>.
             
             Fields in the status array are described in the documentation for
             <strong>MongoCollection::insert()</strong>.


id: MongoGridFS::drop
type: function
doc:
<comment>Description:</comment>
  Drops the files and chunks collections

<comment>Return:</comment>
  <info>array</info>  The database response.


id: MongoGridFS::find
type: function
doc:
<comment>Description:</comment>
  Queries for files

<comment>Param:</comment>
  <info>array</info>  <strong>$query </strong>  The query.
  <info>array</info>  <strong>$fields</strong>  Fields to return.

<comment>Return:</comment>
  <info>MongoGridFSCursor</info>  A <class>MongoGridFSCursor</class>.


id: MongoGridFS::findOne
type: function
doc:
<comment>Description:</comment>
  Returns a single file matching the criteria

<comment>Param:</comment>
  <info>mixed</info>  <strong>$query</strong>  The filename or criteria for which to search.

<comment>Return:</comment>
  <info>MongoGridFSFile</info>  Returns a <class>MongoGridFSFile</class> or <info>null</info>.


id: MongoGridFS::get
type: function
doc:
<comment>Description:</comment>
  Retrieve a file from the database

<comment>Param:</comment>
  <info>mixed</info>  <strong>$id</strong>  <return>_id</return> of the file to find.

<comment>Return:</comment>
  <info>MongoGridFSFile</info>  Returns the file, if found, or <info>null</info>.


id: MongoGridFS::put
type: function
doc:
<comment>Description:</comment>
  Stores a file in the database
  
  MongoGridFS::put is an alias of MongoGridFS::storeFile.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  Name of the file to store.
  <info>array </info>  <strong>$metadata</strong>  Other metadata fields to include in the file document.
                     
                     Aceste câmpuri pot să le rescrie pe cele create automat de către driver,
                     după cum e descris în documentația de bază MongoDB pentru
                     colecția de fișiere.
                     Ca un exemplu de utilizare practică a acestui comportament ar fi specificarea
                     unor valori specifice pentru <return>chunkSize</return> sau
                     <return>_id</return> pentru fișier.
  <info>array </info>  <strong>$options </strong>  An array of options for the insert operations executed against the <return>chunks</return> and
                     <return>files</return> collections. See <strong>MongoCollection::insert()</strong> for documentation on these
                     these options.

<comment>Return:</comment>
  <info>mixed</info>  Întoarce valoarea <return>_id</return> a fișierului cu documentul salvat.
         Acesta va fi un <class>MongoId</class> generat, doar dacă un
         <return>_id</return> nu a fost specificat în mod explicit în parametrul
         <strong>$metadata</strong>.

<comment>See Also:</comment>
   * <strong>MongoGridFS::storeBytes()</strong>
   * <strong>MongoGridFS::storeFile()</strong>
   * <strong>MongoGridFS::storeUpload()</strong>
   * MongoDB core docs on GridFS


id: MongoGridFS::remove
type: function
doc:
<comment>Description:</comment>
  Remove files and their chunks from the database

<comment>Param:</comment>
  <info>array</info>  <strong>$criteria</strong>  The filename or criteria for which to search.
  <info>array</info>  <strong>$options </strong>  An array of options for the remove operations executed against the <return>chunks</return> and
                    <return>files</return> collections. See <strong>MongoCollection::remove()</strong> for documentation on these
                    options.

<comment>Return:</comment>
  <info>boolarray</info>  Returns an array containing the status of the removal (with respect to the <return>files</return>
             collection) if the <return>"w"</return> option is set. Otherwise, returns <info>true</info>.
             
             Fields in the status array are described in the documentation for
             <strong>MongoCollection::insert()</strong>.


id: MongoGridFS::storeBytes
type: function
doc:
<comment>Description:</comment>
  Stores a string of bytes in the database

<comment>Param:</comment>
  <info>string</info>  <strong>$bytes   </strong>  String of bytes to store.
  <info>array </info>  <strong>$metadata</strong>  Other metadata fields to include in the file document.
                     
                     Aceste câmpuri pot să le rescrie pe cele create automat de către driver,
                     după cum e descris în documentația de bază MongoDB pentru
                     colecția de fișiere.
                     Ca un exemplu de utilizare practică a acestui comportament ar fi specificarea
                     unor valori specifice pentru <return>chunkSize</return> sau
                     <return>_id</return> pentru fișier.
  <info>array </info>  <strong>$options </strong>  An array of options for the insert operations executed against the <return>chunks</return> and
                     <return>files</return> collections. See <strong>MongoCollection::insert()</strong> for documentation on these
                     these options.

<comment>Return:</comment>
  <info>mixed</info>  Întoarce valoarea <return>_id</return> a fișierului cu documentul salvat.
         Acesta va fi un <class>MongoId</class> generat, doar dacă un
         <return>_id</return> nu a fost specificat în mod explicit în parametrul
         <strong>$metadata</strong>.

<comment>See Also:</comment>
   * <strong>MongoGridFS::put()</strong>
   * <strong>MongoGridFS::storeFile()</strong>
   * <strong>MongoGridFS::storeUpload()</strong>
   * MongoDB core docs on GridFS


id: MongoGridFS::storeFile
type: function
doc:
<comment>Description:</comment>
  Stores a file in the database

<comment>Param:</comment>
  <info>stringresource</info>  <strong>$filename</strong>  Name of the file or a readable stream to store.
  <info>array         </info>  <strong>$metadata</strong>  Other metadata fields to include in the file document.
                             
                             Aceste câmpuri pot să le rescrie pe cele create automat de către
                             driver,
                             după cum e descris în documentația de bază MongoDB pentru
                             colecția de fișiere.
                             Ca un exemplu de utilizare practică a acestui comportament ar fi
                             specificarea
                             unor valori specifice pentru <return>chunkSize</return> sau
                             <return>_id</return> pentru fișier.
  <info>array         </info>  <strong>$options </strong>  An array of options for the insert operations executed against the
                             <return>chunks</return> and <return>files</return> collections. See <strong>MongoCollection::insert()</strong> for
                             documentation on these these options.

<comment>Return:</comment>
  <info>mixed</info>  Întoarce valoarea <return>_id</return> a fișierului cu documentul salvat.
         Acesta va fi un <class>MongoId</class> generat, doar dacă un
         <return>_id</return> nu a fost specificat în mod explicit în parametrul
         <strong>$metadata</strong>.

<comment>See Also:</comment>
   * <strong>MongoGridFS::put()</strong>
   * <strong>MongoGridFS::storeBytes()</strong>
   * <strong>MongoGridFS::storeUpload()</strong>
   * MongoDB core docs on GridFS


id: MongoGridFS::storeUpload
type: function
doc:
<comment>Description:</comment>
  Stores an uploaded file in the database

<comment>Param:</comment>
  <info>string</info>  <strong>$name    </strong>  The name of the uploaded file(s) to store. This should correspond to the file
                     field's <return>name</return> attribute in the HTML form.
  <info>array </info>  <strong>$metadata</strong>  Other metadata fields to include in the file document.
                     
                     Aceste câmpuri pot să le rescrie pe cele create automat de către driver,
                     după cum e descris în documentația de bază MongoDB pentru
                     colecția de fișiere.
                     Ca un exemplu de utilizare practică a acestui comportament ar fi specificarea
                     unor valori specifice pentru <return>chunkSize</return> sau
                     <return>_id</return> pentru fișier.
                     
                     The <return>filename</return> field will be populated with the client's filename (e.g.
                     <return>$_FILES['foo']['name']</return>).

<comment>Return:</comment>
  <info>mixed</info>  Întoarce valoarea <return>_id</return> a fișierului cu documentul salvat.
         Acesta va fi un <class>MongoId</class> generat, doar dacă un
         <return>_id</return> nu a fost specificat în mod explicit în parametrul
         <strong>$metadata</strong>.
         
         If multiple files are uploaded using the same field name, this method will not return
         anything; however, the files themselves will still be processed.

<comment>See Also:</comment>
   * <strong>MongoGridFS::put()</strong>
   * <strong>MongoGridFS::storeBytes()</strong>
   * <strong>MongoGridFS::storeFile()</strong>
   * MongoDB core docs on GridFS


id: MongoGridFSCursor::__construct
type: function
doc:
<comment>Description:</comment>
  Create a new cursor

<comment>Param:</comment>
  <info>MongoGridFS</info>  <strong>$gridfs    </strong>  Related GridFS collection.
  <info>resource   </info>  <strong>$connection</strong>  Database connection.
  <info>string     </info>  <strong>$ns        </strong>  Full name of database and collection.
  <info>array      </info>  <strong>$query     </strong>  Database query.
  <info>array      </info>  <strong>$fields    </strong>  Fields to return.

<comment>Return:</comment>
  <info>unknown</info>  Returns the new cursor.


id: MongoGridFSCursor::current
type: function
doc:
<comment>Description:</comment>
  Returns the current file

<comment>Return:</comment>
  <info>MongoGridFSFile</info>  The current file.


id: MongoGridFSCursor::getNext
type: function
doc:
<comment>Description:</comment>
  Return the next file to which this cursor points, and advance the cursor

<comment>Return:</comment>
  <info>MongoGridFSFile</info>  Returns the next file.


id: MongoGridFSCursor::key
type: function
doc:
<comment>Description:</comment>
  Returns the current result's filename

<comment>Return:</comment>
  <info>string</info>  The current result's _id as a string.


id: MongoGridFSException
type: class
doc:
<comment>Description:</comment>
  Thrown when there are errors reading or writing files to or from the database.


id: MongoGridFSFile::getBytes
type: function
doc:
<comment>Description:</comment>
  Returns this file's contents as a string of bytes
  
  Warning: this will load the file into memory.  If the file is bigger than your memory, this will
  cause problems!

<comment>Return:</comment>
  <info>string</info>  Returns a string of the bytes in the file.


id: MongoGridFSFile::getFilename
type: function
doc:
<comment>Description:</comment>
  Returns this file's filename

<comment>Return:</comment>
  <info>string</info>  Returns the filename.


id: MongoGridFSFile::getResource
type: function
doc:
<comment>Description:</comment>
  Returns a resource that can be used to read the stored file
  
  This method returns a stream resource that can be used with all file functions in PHP that deal
  with reading files. The contents of the file are pulled out of MongoDB on the fly, so that the
  whole file does not have to be loaded into memory first.
  
  At most two GridFSFile chunks will be loaded in memory.

<comment>Return:</comment>
  <info>resource</info>  Returns a resource that can be used to read the file with


id: MongoGridFSFile::getSize
type: function
doc:
<comment>Description:</comment>
  Returns this file's size

<comment>Return:</comment>
  <info>int</info>  Returns this file's size


id: MongoGridFSFile::write
type: function
doc:
<comment>Description:</comment>
  Writes this file to the filesystem

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  The location to which to write the file.  If none is given, the stored filename
                     will be used.

<comment>Return:</comment>
  <info>int</info>  Returns the number of bytes written.


id: MongoGridfsFile::__construct
type: function
doc:
<comment>Description:</comment>
  Create a new GridFS file

<comment>Param:</comment>
  <info>MongoGridFS</info>  <strong>$gridfs</strong>  The parent MongoGridFS instance.
  <info>array      </info>  <strong>$file  </strong>  A file from the database.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new MongoGridFSFile.


id: MongoId
type: class
doc:
<comment>Description:</comment>
  A unique identifier created for database objects.  If an object is inserted into the database
  without an _id field, an _id field will be added to it with a <class>MongoId</class> instance as its value.  If
  the data  has a naturally occuring unique field (e.g. username or timestamp) it is fine to use
  this as the _id field instead, and it will not be replaced with  a <class>MongoId</class>.
  
  Instances of the <class>MongoId</class> class fulfill the role that  autoincrementing does in a relational
  database: to provide a unique key if  the data does not naturally have one. Autoincrementing does
  not work well  with a sharded database, as it is difficult to determine the next number in the
  sequence. This class fulfills the constraints of quickly generating a value that is unique across
  shards.
  
  Each MongoId is 12 bytes (making its string form 24 hexadecimal characters). The first four bytes
  are a timestamp, the next three are a hash of the client machine's hostname, the next two are the
  two least significant bytes of the process id running the script, and the last three bytes are an
  incrementing value.
  
  <class>MongoId</class>s are serializable/unserializable.  Their serialized form is similar to their string form: 


id: MongoId::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new id

<comment>Param:</comment>
  <info>stringMongoId</info>  <strong>$id</strong>  A string (must be 24 hexadecimal characters) or a <class>MongoId</class> instance.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new id.

<comment>See Also:</comment>
   * MongoId::__toString
   * MongoId::isvalid


id: MongoId::__set_state
type: function
doc:
<comment>Description:</comment>
  Create a dummy MongoId
  
  This function is only used by PHP internally, it shouldn't need to ever be called by the user.
  
  It is identical to the function:

<comment>Param:</comment>
  <info>array</info>  <strong>$props</strong>  Theoretically, an array of properties used to create the new id.   However, as
                 MongoId instances have no properties, this is not used.

<comment>Return:</comment>
  <info>MongoId</info>  A new id with the value "000000000000000000000000".


id: MongoId::__toString
type: function
doc:
<comment>Description:</comment>
  Returns a hexidecimal representation of this id

<comment>Return:</comment>
  <info>string</info>  This id.


id: MongoId::getHostname
type: function
doc:
<comment>Description:</comment>
  Gets the hostname being used for this machine's ids
  
  This returns the hostname <class>MongoId</class> is using to  generate unique ids.  This should be the same value
  <strong>gethostname()</strong> returns.
  
  It is identical to the function:

<comment>Return:</comment>
  <info>string</info>  Returns the hostname.


id: MongoId::getInc
type: function
doc:
<comment>Description:</comment>
  Gets the incremented value to create this id

<comment>Return:</comment>
  <info>int</info>  Returns the incremented value used to create this <class>MongoId</class>.


id: MongoId::getPID
type: function
doc:
<comment>Description:</comment>
  Gets the process ID
  
  Extracts the pid from the Mongo ID

<comment>Return:</comment>
  <info>int</info>  Returns the PID of the <class>MongoId</class>.


id: MongoId::getTimestamp
type: function
doc:
<comment>Description:</comment>
  Gets the number of seconds since the epoch that this id was created
  
  This returns the same thing as running <strong>time()</strong> when the id is created.

<comment>Return:</comment>
  <info>int</info>  Returns the number of seconds since the epoch that this id was created.  There are only  four
       bytes of timestamp stored, so <class>MongoDate</class> is a better choice  for storing exact or wide-ranging
       times.


id: MongoId::isValid
type: function
doc:
<comment>Description:</comment>
  Check if a value is a valid ObjectId
  
  This method may be used to check a variable before passing it as an argument to
  <strong>MongoId::__construct()</strong>.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$value</strong>  The value to check for validity.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if <strong>$value</strong> is a <class>MongoId</class> instance or a string consisting of exactly 24
        hexadecimal characters; otherwise, <info>false</info> is returned.


id: MongoInsertBatch
type: class
doc:
<comment>Description:</comment>
  Constructs a batch of INSERT operations. See <class>MongoWriteBatch</class>.


id: MongoInsertBatch::__construct
type: function
doc:
<comment>Description:</comment>
  Description
  
  Constructs a batch of INSERT operations. See <class>MongoWriteBatch</class>.

<comment>Param:</comment>
  <info>MongoCollection</info>  <strong>$collection   </strong>  Clasa <class>MongoCollection</class> asupra căreia se execută setul.
                                   Gradele ei de participare vor fi
                                   copiate și folosite ca implicite dacă nu au fost furnizate cu
                                   <strong>$write_options</strong>
                                   sau în timpul executării MongoWriteBatch::execute.
  <info>array          </info>  <strong>$write_options</strong>  Un tablou cu Opiuni de Înscriere.
                                   cheiaînsemnătatea valoriiw (int|string)Valoare a Gradului de
                                   participare la înscrierewtimeout (int)Timpul maximal de așteptare
                                   a replicăriiorderedDetermină dacă MongoDB trebuie să aplice acest
                                   set
                                   în ordinea stabilită. Înscrierile ordonate se execută secvențial
                                   (adică câte o
                                   înregistrare) și execuția se întrerupe după prima eroare.
                                   Înscrierile neordonate
                                   pot fi executate în paralel și execuția nu se va stopa după prima
                                   eroare.
                                   Valoarea implicită este <info>true</info>j (bool)Așteaptă jurnalizarea pe
                                   primar. Această valoare e nerecomandată, utilizați WriteConcern
                                   în locfsync (bool)Așteaptă fsync pe primar. Această valoare e
                                   nerecomandată, utilizați WriteConcern în loc

<comment>Return:</comment>
  <info>unknown</info>  A new MongoInsertBatch.


id: MongoInt32
type: class
doc:
<comment>Description:</comment>
  The class can be used to save 32-bit integers to the database on a 64-bit  system.


id: MongoInt32::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new 32-bit integer
  
  Creates a new 32-bit number with the given value.

<comment>Param:</comment>
  <info>string</info>  <strong>$value</strong>  A number.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new integer.


id: MongoInt32::__toString
type: function
doc:
<comment>Description:</comment>
  Returns the string representation of this 32-bit integer

<comment>Return:</comment>
  <info>string</info>  Returns the string representation of this integer.


id: MongoInt64
type: class
doc:
<comment>Description:</comment>
  The class can be used to save 64-bit integers to the database on a 32-bit  system.


id: MongoInt64::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new 64-bit integer
  
  Creates a new 64-bit number with the given value.

<comment>Param:</comment>
  <info>string</info>  <strong>$value</strong>  A number.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new integer.


id: MongoInt64::__toString
type: function
doc:
<comment>Description:</comment>
  Returns the string representation of this 64-bit integer

<comment>Return:</comment>
  <info>string</info>  Returns the string representation of this integer.


id: MongoLog
type: class
doc:
<comment>Description:</comment>
  Logging can be used to get detailed information about what the driver is doing. Logging is
  disabled by default, but this class allows you to activate specific levels of logging for various
  parts of the driver. Some examples:
  
  By default, MongoLog emits all log messages as PHP notices. Depending on the SAPI you use,
  messages may be sent to <return>stderr</return> (for CLI) or the web server's error log. If, after configuring
  MongoLog, log messages are not appearing as expected, ensure that the <info>E_NOTICE</info> bit is included in
  error_reporting and that display_errors is on.


id: MongoLog::CON
type: constant
doc:
<comment>Description:</comment>
  Log connection activity. Creating new connections, authentication, pinging, timeouts, etc.


id: MongoLog::FINE
type: constant
doc:
<comment>Description:</comment>
  Log most events that the driver performs (e.g. server selection, socket communication). Depending
  on the module being logged, this can be extremely noisy and is primarily useful for debugging.


id: MongoLog::INFO
type: constant
doc:
<comment>Description:</comment>
  Log events that may be of interest to administrators, but are not particularly noteworthy (e.g.
  option parsing, authentication steps).


id: MongoLog::IO
type: constant
doc:
<comment>Description:</comment>
  Log traffic to/from the database. Unless your program is trivial, this will create an enormous
  number of log messages.


id: MongoLog::PARSE
type: constant
doc:
<comment>Description:</comment>
  Log parsing of the connection string and options when constructing <class>MongoClient</class>.


id: MongoLog::POOL
type: constant
doc:
<comment>Description:</comment>
  Previously used to log connection pool activity. This option is now a deprecated alias of
  <info>MongoLog::RS</info>.


id: MongoLog::RS
type: constant
doc:
<comment>Description:</comment>
  Log replica set activity. Failovers, read preference selection, etc.


id: MongoLog::SERVER
type: constant
doc:
<comment>Description:</comment>
  Previously used to log server status changes. This option is deprecated in favor of <info>MongoLog::RS</info>.


id: MongoLog::WARNING
type: constant
doc:
<comment>Description:</comment>
  Log events that are somewhat exceptional, but not quite worthy of an actual exception (e.g.
  recoverable connection errors).


id: MongoLog::getCallback
type: function
doc:
<comment>Description:</comment>
  Gets the previously set callback function
  
  Retrieves the callback function.

<comment>Return:</comment>
  <info>callable</info>  Returns the callback function, or <info>false</info> if not set yet.


id: MongoLog::getLevel
type: function
doc:
<comment>Description:</comment>
  Gets the level(s) currently being logged
  
  This function can be used to see which log levels are currently enabled. The returned integer may
  be compared with the MongoLog level constants using bitwise operators to check for specific log
  levels.

<comment>Return:</comment>
  <info>int</info>  Returns the level(s) currently being logged.


id: MongoLog::getModule
type: function
doc:
<comment>Description:</comment>
  Gets the module(s) currently being logged
  
  This function can be used to see which driver modules are currently being logged. The returned
  integer may be compared with the MongoLog module constants using bitwise operators to check if
  specific modules are being logged.

<comment>Return:</comment>
  <info>int</info>  Returns the module(s) currently being logged.


id: MongoLog::setCallback
type: function
doc:
<comment>Description:</comment>
  Sets a callback function to be invoked for events
  
  This function will set a callback function to be invoked for events in lieu of emitting of PHP
  notice.

<comment>Param:</comment>
  <info>callable</info>  <strong>$log_function</strong>  The callback function to be invoked on events. It should have the
                           following prototype:
                           
                           log_function<info>int</info><strong>$module</strong><info>int</info><strong>$level</strong><info>string</info><strong>$message</strong><strong>$module</strong> One of the MongoLog
                           module constants. <strong>$level</strong> One of the MongoLog level constants. <strong>$message</strong>
                           The log message itself.
                           
                           One of the MongoLog module constants.
                           
                           One of the MongoLog level constants.
                           
                           The log message itself.
  <info>int     </info>  <strong>$module      </strong>  One of the MongoLog module constants.
  <info>int     </info>  <strong>$level       </strong>  One of the MongoLog level constants.
  <info>string  </info>  <strong>$message     </strong>  The log message itself.

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


id: MongoLog::setLevel
type: function
doc:
<comment>Description:</comment>
  Sets the level(s) to be logged
  
  This function can be used to control logging verbosity and the types of activities that should be
  logged. The MongoLog level constants may be used with bitwise operators to specify multiple
  levels.
  
  Note that you must also call <strong>MongoLog::setModule()</strong> to specify which modules(s) of the driver
  should log.

<comment>Param:</comment>
  <info>int</info>  <strong>$level</strong>  The level(s) you would like to log.

<comment>Return:</comment>
  <info>void</info>  


id: MongoLog::setModule
type: function
doc:
<comment>Description:</comment>
  Sets the module(s) to be logged
  
  This function can be used to set which driver modules should be logged. The MongoLog module
  constants may be used with bitwise operators to specify multiple modules.
  
  Note that you must also call <strong>MongoLog::setLevel()</strong> to enable logging.

<comment>Param:</comment>
  <info>int</info>  <strong>$module</strong>  The module(s) you would like to log.

<comment>Return:</comment>
  <info>void</info>  


id: MongoMaxKey
type: class
doc:
<comment>Description:</comment>
  <class>MongoMaxKey</class> is an special type used by the database that compares greater than all other possible
  BSON values. Thus, if a query is sorted by a given field in ascending order, any document with a
  <class>MongoMaxKey</class> as its value will be returned last.
  
  <class>MongoMaxKey</class> has no associated fields, methods, or constants. It is merely the "greatest" value
  that can be represented in the database.
  
  <class>MongoMaxKey</class> is used internally by MongoDB for indexing and sharding. There is generally no reason
  to use this class in an application.


id: MongoMinKey
type: class
doc:
<comment>Description:</comment>
  <class>MongoMinKey</class> is an special type used by the database that compares less than all other possible
  BSON values. Thus, if a query is sorted by a given field in ascending order, any document with a
  <class>MongoMinKey</class> as its value will be returned first.
  
  <class>MongoMinKey</class> has no associated fields, methods, or constants. It is merely the "smallest" value
  that can be represented in the database.
  
  <class>MongoMinKey</class> is used internally by MongoDB for indexing and sharding. There is generally no reason
  to use this class in an application.


id: MongoPool
type: class
doc:
<comment>Description:</comment>
  The current (1.3.0+) releases of the driver no longer implements pooling. This class and its
  methods are therefore deprecated and should not be used.


id: MongoPool::getSize
type: function
doc:
<comment>Description:</comment>
  Get pool size for connection pools

<comment>Return:</comment>
  <info>int</info>  Returns the current pool size.

<comment>See Also:</comment>
   * <strong>MongoPool::setSize()</strong>
   * <strong>MongoPool::info()</strong>
   * The connection documentation.


id: MongoPool::info
type: function
doc:
<comment>Description:</comment>
  Returns information about all connection pools
  
  Returns an array of information about all connection pools.

<comment>Return:</comment>
  <info>array</info>  Each connection pool has an identifier, which starts with the host. For each pool, this
         function shows the following fields: <strong>$in use</strong> The number of connections currently being used
         by <class>Mongo</class> instances. <strong>$in pool</strong> The number of connections currently in the pool (not being
         used). <strong>$remaining</strong> The number of connections that could be created by this pool. For
         example, suppose a pool had 5 connections remaining and 3 connections in the pool.  We
         could create 8 new instances of <class>MongoClient</class> before we exhausted this pool (assuming no
         instances of <class>MongoClient</class> went out of scope, returning their connections to the pool).  A
         negative number means that this pool will spawn unlimited connections.  Before a pool is
         created, you can change the max number of connections by calling <strong>Mongo::setPoolSize()</strong>. Once
         a pool is showing up in the output of this function, its size cannot be changed. <strong>$total</strong> The
         total number of connections allowed for this pool.  This should be greater than or equal to
         "in use" + "in pool" (or -1). <strong>$timeout</strong> The socket timeout for connections in this pool.
         This is how long connections in this pool will attempt to connect to a server before giving
         up. <strong>$waiting</strong> If you have capped the pool size, workers requesting connections from the pool
         may block until other workers return their connections. This field shows how many
         milliseconds workers have blocked for connections to be released.  If this number keeps
         increasing, you may want to use <strong>MongoPool::setSize()</strong> to add more connections to your pool.
         
         The number of connections currently being used by <class>Mongo</class> instances.
         
         The number of connections currently in the pool (not being used).
         
         The number of connections that could be created by this pool. For example, suppose a pool
         had 5 connections remaining and 3 connections in the pool.  We could create 8 new instances
         of <class>MongoClient</class> before we exhausted this pool (assuming no instances of <class>MongoClient</class> went out
         of scope, returning their connections to the pool).
         
         A negative number means that this pool will spawn unlimited connections.
         
         Before a pool is created, you can change the max number of connections by calling
         <strong>Mongo::setPoolSize()</strong>. Once a pool is showing up in the output of this function, its size
         cannot be changed.
         
         The total number of connections allowed for this pool.  This should be greater than or
         equal to "in use" + "in pool" (or -1).
         
         The socket timeout for connections in this pool. This is how long connections in this pool
         will attempt to connect to a server before giving up.
         
         If you have capped the pool size, workers requesting connections from the pool may block
         until other workers return their connections. This field shows how many milliseconds
         workers have blocked for connections to be released.  If this number keeps increasing, you
         may want to use <strong>MongoPool::setSize()</strong> to add more connections to your pool.


id: MongoPool::setSize
type: function
doc:
<comment>Description:</comment>
  Set the size for future connection pools
  
  Sets the max number of connections new pools will be able to create.

<comment>Param:</comment>
  <info>int</info>  <strong>$size</strong>  The max number of connections future pools will be able to create. Negative numbers
              mean that the pool will spawn an infinite number of connections.

<comment>Return:</comment>
  <info>bool</info>  Returns the former value of pool size.

<comment>See Also:</comment>
   * <strong>MongoPool::getSize()</strong>
   * <strong>MongoPool::info()</strong>
   * The connection documentation.


id: MongoProtocolException
type: class
doc:
<comment>Description:</comment>
  When talking to MongoDB 2.6.0, and later, certain operations (such as writes) may throw
  MongoProtocolException when the response from the server did not make sense - for example during
  network failure (we could read the entire response) or data corruption.
  
  This exception is also thrown when attempting to talk newer protocols then the server supports,
  for example using the <class>MongoWriteBatch</class> when talking to a MongoDB server prior to 2.6.0.


id: MongoRegex
type: class
doc:
<comment>Description:</comment>
  This class can be used to create regular expressions.  Typically, these expressions will be used
  to query the database and find matching strings. More unusually, they can be saved to the database
  and retrieved.
  
  Regular expressions consist of four parts. First a <return>/</return> as starting delimiter, then the pattern,
  another <return>/</return>  and finally a string containing flags.
  
  Regular expression pattern
  
  MongoDB recognizes six regular expression flags:
  
  <return>i</return>: Case insensitive
  
  <return>m</return>: Multiline
  
  <return>x</return>: Can contain comments
  
  <return>l</return>: locale
  
  <return>s</return>: dotall, "." matches everything, including newlines
  
  <return>u</return>: match unicode


id: MongoRegex::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new regular expression
  
  Creates a new regular expression.

<comment>Param:</comment>
  <info>string</info>  <strong>$regex</strong>  Regular expression string of the form <return>/expr/flags</return>.

<comment>Return:</comment>
  <info>unknown</info>  Returns a new regular expression.

<comment>See Also:</comment>
   * MongoRegex::__toString


id: MongoRegex::__toString
type: function
doc:
<comment>Description:</comment>
  A string representation of this regular expression
  
  Returns a string representation of this regular expression.

<comment>Return:</comment>
  <info>string</info>  This regular expression in the form "/expr/flags".


id: MongoResultException
type: class
doc:
<comment>Description:</comment>
  The MongoResultException is thrown by several command helpers (such as
  MongoCollection::findAndModify) in the event of failure. The original result document is available
  through MongoResultException::getDocument.


id: MongoResultException::getDocument
type: function
doc:
<comment>Description:</comment>
  Retrieve the full result document
  
  Retrieves the full error result document.

<comment>Return:</comment>
  <info>array</info>  The full result document as an array, including partial data if available and additional
         keys.


id: MongoTimestamp
type: class
doc:
<comment>Description:</comment>
  <class>MongoTimestamp</class> is an internal type used by MongoDB for replication and sharding. It consists of a
  4-byte timestamp (i.e. seconds since the epoch) and a 4-byte increment. This type is not intended
  for storing time or date values (e.g. a "createdAt" field on a document).
  
  Unless you are writing an application that interacts with MongoDB's replication oplog or sharding
  internals: stop, go directly to <class>MongoDate</class>, do not pass go, and do not collect 200 dollars. This is
  not the class you are looking for.


id: MongoTimestamp::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new timestamp
  
  Creates a new timestamp.  If no parameters are given, the current time is  used and the increment
  is automatically provided.  The increment is set to 0 when the module is loaded and is incremented
  every time this constructor is  called (without the $inc parameter passed in).

<comment>Param:</comment>
  <info>int</info>  <strong>$sec</strong>  Number of seconds since the epoch (i.e. 1 Jan 1970 00:00:00.000 UTC).
  <info>int</info>  <strong>$inc</strong>  Increment.

<comment>Return:</comment>
  <info>unknown</info>  Returns this new timestamp.

<comment>See Also:</comment>
   * MongoTimestamp::__toString


id: MongoTimestamp::__toString
type: function
doc:
<comment>Description:</comment>
  Returns a string representation of this timestamp
  
  Returns the "sec" field of this timestamp.

<comment>Return:</comment>
  <info>string</info>  The seconds since epoch represented by this timestamp.


id: MongoUpdateBatch
type: class
doc:
<comment>Description:</comment>
  Constructs a batch of UPDATE operations. See <class>MongoWriteBatch</class>.


id: MongoUpdateBatch::__construct
type: function
doc:
<comment>Description:</comment>
  Description
  
  Constructs a batch of UPDATE operations. See <class>MongoWriteBatch</class>.

<comment>Param:</comment>
  <info>MongoCollection</info>  <strong>$collection   </strong>  Clasa <class>MongoCollection</class> asupra căreia se execută setul.
                                   Gradele ei de participare vor fi
                                   copiate și folosite ca implicite dacă nu au fost furnizate cu
                                   <strong>$write_options</strong>
                                   sau în timpul executării MongoWriteBatch::execute.
  <info>array          </info>  <strong>$write_options</strong>  Un tablou cu Opiuni de Înscriere.
                                   cheiaînsemnătatea valoriiw (int|string)Valoare a Gradului de
                                   participare la înscrierewtimeout (int)Timpul maximal de așteptare
                                   a replicăriiorderedDetermină dacă MongoDB trebuie să aplice acest
                                   set
                                   în ordinea stabilită. Înscrierile ordonate se execută secvențial
                                   (adică câte o
                                   înregistrare) și execuția se întrerupe după prima eroare.
                                   Înscrierile neordonate
                                   pot fi executate în paralel și execuția nu se va stopa după prima
                                   eroare.
                                   Valoarea implicită este <info>true</info>j (bool)Așteaptă jurnalizarea pe
                                   primar. Această valoare e nerecomandată, utilizați WriteConcern
                                   în locfsync (bool)Așteaptă fsync pe primar. Această valoare e
                                   nerecomandată, utilizați WriteConcern în loc

<comment>Return:</comment>
  <info>unknown</info>  A new MongoUpdateBatch.


id: MongoWriteBatch
type: class
doc:
<comment>Description:</comment>
  MongoWriteBatch is the base class for the <class>MongoInsertBatch</class>, <class>MongoUpdateBatch</class> and <class>MongoDeleteBatch</class>
  classes.
  
  MongoWriteBatch allows you to "batch up" multiple operations (of same type) and shipping them all
  to MongoDB at the same time. This can be especially useful when operating on many documents at the
  same time to reduce roundtrips.
  
  Prior to version 1.5.0 of the driver it was possible to use MongoCollection::batchInsert, however,
  as of 1.5.0 that method is now discouraged.
  
  Note: This class is only available when talking to MongoDB 2.6.0 (and later) servers. It will
  throw <class>MongoProtocolException</class> if attempting to use it on older MongoDB servers.


id: MongoWriteBatch::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a new batch of write operations
  
  Constructs a new MongoWriteBatch.
  
  This is a protected constructor. Please use one of the classes inheriting <class>MongoWriteBatch</class>.

<comment>Param:</comment>
  <info>MongoCollection</info>  <strong>$collection   </strong>  Clasa <class>MongoCollection</class> asupra căreia se execută setul.
                                   Gradele ei de participare vor fi
                                   copiate și folosite ca implicite dacă nu au fost furnizate cu
                                   <strong>$write_options</strong>
                                   sau în timpul executării MongoWriteBatch::execute.
  <info>string         </info>  <strong>$batch_type   </strong>  One of: <return>0</return> - make an MongoWriteBatch::COMMAND_INSERT batch<return>1</return> - make
                                   an MongoWriteBatch::COMMAND_UPDATE batch<return>2</return> - make a
                                   MongoWriteBatch::COMMAND_DELETE batch
  <info>array          </info>  <strong>$write_options</strong>  Un tablou cu Opiuni de Înscriere.
                                   cheiaînsemnătatea valoriiw (int|string)Valoare a Gradului de
                                   participare la înscrierewtimeout (int)Timpul maximal de așteptare
                                   a replicăriiorderedDetermină dacă MongoDB trebuie să aplice acest
                                   set
                                   în ordinea stabilită. Înscrierile ordonate se execută secvențial
                                   (adică câte o
                                   înregistrare) și execuția se întrerupe după prima eroare.
                                   Înscrierile neordonate
                                   pot fi executate în paralel și execuția nu se va stopa după prima
                                   eroare.
                                   Valoarea implicită este <info>true</info>j (bool)Așteaptă jurnalizarea pe
                                   primar. Această valoare e nerecomandată, utilizați WriteConcern
                                   în locfsync (bool)Așteaptă fsync pe primar. Această valoare e
                                   nerecomandată, utilizați WriteConcern în loc

<comment>Return:</comment>
  <info>unknown</info>  A new MongoWriteBatch of type <strong>$batch_type</strong>.

<comment>See Also:</comment>
   * <class>MongoInsertBatch</class>
   * <class>MongoUpdateBatch</class>
   * <class>MongoDeleteBatch</class>


id: MongoWriteBatch::add
type: function
doc:
<comment>Description:</comment>
  Adds a write operation to a batch
  
  Adds a write operation to the batch.
  
  If <strong>$item</strong> causes the batch to exceed the <return>maxWriteBatchSize</return> or <return>maxBsonObjectSize</return> limits, the driver
  will internally split the batches into multiple write commands upon calling
  MongoWriteBatch::execute.

<comment>Param:</comment>
  <info>array</info>  <strong>$item</strong>  An array that describes a write operation. The structure of this value depends on
                the batch's operation type. Batch typeArgument
                expectation<info>MongoWriteBatch::COMMAND_INSERT</info>The document to
                add.<info>MongoWriteBatch::COMMAND_UPDATE</info>Raw update operation.Required keys are <return>"q"</return> and
                <return>"u"</return>, which correspond to the <strong>$criteria</strong> and <strong>$new_object</strong> parameters of
                <strong>MongoCollection::update()</strong>, respectively.Optional keys are <return>"multi"</return> and <return>"upsert"</return>,
                which correspond to the <return>"multiple"</return> and <return>"upsert"</return> options for
                <strong>MongoCollection::update()</strong>, respectively. If unspecified, both options default to
                <info>false</info>.<info>MongoWriteBatch::COMMAND_DELETE</info>Raw delete operation.Required keys are: <return>"q"</return> and
                <return>"limit"</return>, which correspond to the <strong>$criteria</strong> parameter and <return>"justOne"</return> option of
                <strong>MongoCollection::remove()</strong>, respectively.The <return>"limit"</return> option is an <info>int</info>; however,
                MongoDB only supports <return>0</return> (i.e. remove all matching documents) and <return>1</return> (i.e. remove at
                most one matching document) at this time.
                
                The document to add.
                
                Raw update operation.
                
                Required keys are <return>"q"</return> and <return>"u"</return>, which correspond to the <strong>$criteria</strong> and <strong>$new_object</strong>
                parameters of <strong>MongoCollection::update()</strong>, respectively.
                
                Optional keys are <return>"multi"</return> and <return>"upsert"</return>, which correspond to the <return>"multiple"</return> and
                <return>"upsert"</return> options for <strong>MongoCollection::update()</strong>, respectively. If unspecified, both
                options default to <info>false</info>.
                
                Raw delete operation.
                
                Required keys are: <return>"q"</return> and <return>"limit"</return>, which correspond to the <strong>$criteria</strong> parameter and
                <return>"justOne"</return> option of <strong>MongoCollection::remove()</strong>, respectively.
                
                The <return>"limit"</return> option is an <info>int</info>; however, MongoDB only supports <return>0</return> (i.e. remove all
                matching documents) and <return>1</return> (i.e. remove at most one matching document) at this time.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success and throws an exception on failure.


id: MongoWriteBatch::execute
type: function
doc:
<comment>Description:</comment>
  Executes a batch of write operations
  
  Executes the batch of write operations.

<comment>Param:</comment>
  <info>array</info>  <strong>$write_options</strong>  See MongoWriteBatch::__construct.

<comment>Return:</comment>
  <info>array</info>  Returns an array containing statistical information for the full batch. If the batch had to
         be split into multiple batches, the return value will aggregate the values from individual
         batches and return only the totals.
         
         If the batch was empty, an array containing only the 'ok' field is returned (as <info>true</info>)
         although nothing will be shipped over the wire (NOOP).
         
         Array keyValue meaningReturned for batch typenInsertedNumber of inserted
         documentsMongoWriteBatch::COMMAND_INSERT batchnMatchedNumber of documents matching the
         query criteriaMongoWriteBatch::COMMAND_UPDATE batchnModifiedNumber of documents actually
         needed to be modiedMongoWriteBatch::COMMAND_UPDATE batchnUpsertedNumber of upserted
         documentsMongoWriteBatch::COMMAND_UPDATE batchnRemovedNumber of documents
         removedMongoWriteBatch::COMMAND_DELETE batchokCommand success indicatorAll


id: MongoWriteConcernException
type: class
doc:
<comment>Description:</comment>
  MongoWriteConcernException is thrown when a write fails. See  for how to set failure thresholds.
  
  Prior to MongoDB 2.6.0, the getLastError command would determine whether a write failed.


id: MongoWriteConcernException::getDocument
type: function
doc:
<comment>Description:</comment>
  Get the error document
  
  Returns the actual response from the server that was interperated as an error.

<comment>Return:</comment>
  <info>array</info>  A MongoDB document, if available, as an array.


id: MultipleIterator
type: class
doc:
<comment>Description:</comment>
  An Iterator that sequentially iterates over all attached iterators


id: MultipleIterator::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a new MultipleIterator
  
  Construct a new MultipleIterator.

<comment>Param:</comment>
  <info>int</info>  <strong>$flags</strong>  The flags to set, according to the Flag Constants. <info>MultipleIterator::MIT_NEED_ALL</info> or
               <info>MultipleIterator::MIT_NEED_ANY</info> <info>MultipleIterator::MIT_KEYS_NUMERIC</info> or
               <info>MultipleIterator::MIT_KEYS_ASSOC</info>
               
               Defaults to <info>MultipleIterator::MIT_NEED_ALL</info>|<info>MultipleIterator::MIT_KEYS_NUMERIC</info>.

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

<comment>See Also:</comment>
   * Flag Constants
   * MultipleIterator::valid


id: MultipleIterator::attachIterator
type: function
doc:
<comment>Description:</comment>
  Attaches iterator information
  
  Attaches iterator information.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>Iterator</info>  <strong>$iterator</strong>  The new iterator to attach.
  <info>string  </info>  <strong>$infos   </strong>  The associative information for the Iterator, which must be an <info>int</info>, a <info>string</info>,
                       or <info>null</info>.

<comment>Return:</comment>
  <info>void</info>  Description...

<comment>See Also:</comment>
   * MultipleIterator::__construct


id: MultipleIterator::containsIterator
type: function
doc:
<comment>Description:</comment>
  Checks if an iterator is attached
  
  Checks if an iterator is attached or not.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>Iterator</info>  <strong>$iterator</strong>  The iterator to check.

<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>
   * MultipleIterator::valid


id: MultipleIterator::countIterators
type: function
doc:
<comment>Description:</comment>
  Gets the number of attached iterator instances
  
  Gets the number of attached iterator instances.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>int</info>  The number of attached iterator instances (as an <info>int</info>).

<comment>See Also:</comment>
   * MultipleIterator::containsIterator


id: MultipleIterator::current
type: function
doc:
<comment>Description:</comment>
  Gets the registered iterator instances
  
  Get the registered iterator instances current() result.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>array</info>  An <info>array</info> containing the current values of each attached iterator, or <info>false</info> if no iterators
         are attached.

<comment>See Also:</comment>
   * MultipleIterator::valid


id: MultipleIterator::detachIterator
type: function
doc:
<comment>Description:</comment>
  Detaches an iterator
  
  Detaches an iterator.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>Iterator</info>  <strong>$iterator</strong>  The iterator to detach.

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

<comment>See Also:</comment>
   * MultipleIterator::attachIterator


id: MultipleIterator::getFlags
type: function
doc:
<comment>Description:</comment>
  Gets the flag information
  
  Gets information about the flags.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>int</info>  Information about the flags, as an <info>int</info>.

<comment>See Also:</comment>
   * Flag Constants
   * MultipleIterator::__construct
   * MultipleIterator::setFlags


id: MultipleIterator::key
type: function
doc:
<comment>Description:</comment>
  Gets the registered iterator instances
  
  Get the registered iterator instances key() result.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>array</info>  An <info>array</info> of all registered iterator instances, or <info>false</info> if no sub iterator is attached.

<comment>See Also:</comment>
   * MultipleIterator::current


id: MultipleIterator::next
type: function
doc:
<comment>Description:</comment>
  Moves all attached iterator instances forward
  
  Moves all attached iterator instances forward.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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

<comment>See Also:</comment>
   * MultipleIterator::rewind


id: MultipleIterator::rewind
type: function
doc:
<comment>Description:</comment>
  Rewinds all attached iterator instances
  
  Rewinds all attached iterator instances.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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

<comment>See Also:</comment>
   * MultipleIterator::next


id: MultipleIterator::setFlags
type: function
doc:
<comment>Description:</comment>
  Sets flags
  
  Sets flags.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>int</info>  <strong>$flags</strong>  The flags to set, according to the Flag Constants

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

<comment>See Also:</comment>
   * Flag Constants
   * MultipleIterator::__construct
   * MultipleIterator::getFlags


id: MultipleIterator::valid
type: function
doc:
<comment>Description:</comment>
  Checks the validity of sub iterators
  
  Checks the validity of sub iterators.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if one or all sub iterators are valid depending on flags, otherwise <info>false</info>

<comment>See Also:</comment>
   * MultipleIterator::__construct


id: Mutex
type: class
doc:
<comment>Description:</comment>
  The <class>Mutex</class> class has been removed in pthreads v3.
  
  The static methods contained in the Mutex class provide direct access to Posix Mutex
  functionality.


id: Mutex::create
type: function
doc:
<comment>Description:</comment>
  Create a Mutex
  
  Create, and optionally lock a new Mutex for the caller

<comment>Param:</comment>
  <info>bool</info>  <strong>$lock</strong>  Setting lock to true will lock the Mutex for the caller before returning the handle

<comment>Return:</comment>
  <info>int</info>  A newly created and optionally locked Mutex handle


id: Mutex::destroy
type: function
doc:
<comment>Description:</comment>
  Destroy Mutex
  
  Destroying Mutex handles must be carried out explicitly by the programmer when they are finished
  with the Mutex handle.

<comment>Param:</comment>
  <info>int</info>  <strong>$mutex</strong>  A handle returned by a previous call to <strong>Mutex::create()</strong>. The handle should not be
               locked by any Thread when <strong>Mutex::destroy()</strong> is called.

<comment>Return:</comment>
  <info>bool</info>  A boolean indication of success


id: Mutex::lock
type: function
doc:
<comment>Description:</comment>
  Acquire Mutex
  
  Attempt to lock the Mutex for the caller.
  
  An attempt to lock a Mutex owned (locked) by another Thread will result in blocking.

<comment>Param:</comment>
  <info>int</info>  <strong>$mutex</strong>  A handle returned by a previous call to <strong>Mutex::create()</strong>.

<comment>Return:</comment>
  <info>bool</info>  A boolean indication of success.


id: Mutex::trylock
type: function
doc:
<comment>Description:</comment>
  Attempt to Acquire Mutex
  
  Attempt to lock the Mutex for the caller without blocking if the Mutex is owned (locked) by
  another Thread.

<comment>Param:</comment>
  <info>int</info>  <strong>$mutex</strong>  A handle returned by a previous call to <strong>Mutex::create()</strong>.

<comment>Return:</comment>
  <info>bool</info>  A boolean indication of success.


id: Mutex::unlock
type: function
doc:
<comment>Description:</comment>
  Release Mutex
  
  Attempts to unlock the Mutex for the caller, optionally destroying the Mutex handle. The calling
  thread should own the Mutex at the time of the call.

<comment>Param:</comment>
  <info>int </info>  <strong>$mutex  </strong>  A handle returned by a previous call to <strong>Mutex::create()</strong>.
  <info>bool</info>  <strong>$destroy</strong>  When true pthreads will destroy the Mutex after a successful unlock.

<comment>Return:</comment>
  <info>bool</info>  A boolean indication of success.


id: MysqlndUhConnection::__construct
type: function
doc:
<comment>Description:</comment>
  The __construct purpose
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.


id: MysqlndUhConnection::changeUser
type: function
doc:
<comment>Description:</comment>
  Changes the user of the specified mysqlnd database connection
  
  Changes the user of the specified mysqlnd database connection

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$user      </strong>  The MySQL user name.
  <info>string            </info>  <strong>$password  </strong>  The MySQL password.
  <info>string            </info>  <strong>$database  </strong>  The MySQL database to change to.
  <info>bool              </info>  <strong>$silent    </strong>  Controls if mysqlnd is allowed to emit errors or not.
  <info>int               </info>  <strong>$passwd_len</strong>  Length of the MySQL password.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_change_user()</strong>


id: MysqlndUhConnection::charsetName
type: function
doc:
<comment>Description:</comment>
  Returns the default character set for the database connection
  
  Returns the default character set for the database connection.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>string</info>  The default character set.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_character_set_name()</strong>


id: MysqlndUhConnection::close
type: function
doc:
<comment>Description:</comment>
  Closes a previously opened database connection
  
  Closes a previously opened database connection.
  
  Failing to call the parent implementation may cause memory leaks or crash PHP. This is not
  considered a bug. Please, keep in mind that the <return>mysqlnd</return> library functions have never been designed
  to be exposed to the user space.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  The connection to be closed. Do not modify!
  <info>int               </info>  <strong>$close_type</strong>  Why the connection is to be closed. The value of <strong>$close_type</strong> is
                                   one of <info>MYSQLND_UH_MYSQLND_CLOSE_EXPLICIT</info>,
                                   <info>MYSQLND_UH_MYSQLND_CLOSE_IMPLICIT</info>,
                                   <info>MYSQLND_UH_MYSQLND_CLOSE_DISCONNECTED</info> or
                                   <info>MYSQLND_UH_MYSQLND_CLOSE_LAST</info>. The latter should never be seen,
                                   unless the default behaviour of the <return>mysqlnd</return> library has been
                                   changed by a plugin.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_close()</strong>
   * <strong>mysql_close()</strong>


id: MysqlndUhConnection::connect
type: function
doc:
<comment>Description:</comment>
  Open a new connection to the MySQL server
  
  Open a new connection to the MySQL server.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection </strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$host       </strong>  Can be either a host name or an IP address. Passing the NULL
                                    value or the string "localhost" to this parameter, the local
                                    host is assumed. When possible, pipes will be used instead of
                                    the TCP/IP protocol.
  <info>                  </info>  <strong>$user       </strong>  The MySQL user name.
  <info>string            </info>  <strong>$password   </strong>  If not provided or <info>null</info>, the MySQL server will attempt to
                                    authenticate the user against those user records which have no
                                    password only. This allows one username to be used with
                                    different permissions (depending on if a password as provided or
                                    not).
  <info>string            </info>  <strong>$database   </strong>  If provided will specify the default database to be used when
                                    performing queries.
  <info>int               </info>  <strong>$port       </strong>  Specifies the port number to attempt to connect to the MySQL
                                    server.
  <info>string            </info>  <strong>$socket     </strong>  Specifies the socket or named pipe that should be used. If <info>null</info>,
                                    mysqlnd will default to <return>/tmp/mysql.sock</return>.
  <info>int               </info>  <strong>$mysql_flags</strong>  Connection options.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_connect()</strong>
   * <strong>mysql_connect()</strong>


id: MysqlndUhConnection::endPSession
type: function
doc:
<comment>Description:</comment>
  End a persistent connection
  
  End a persistent connection
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::escapeString
type: function
doc:
<comment>Description:</comment>
  Escapes special characters in a string for use in an SQL statement,
     taking into account the current charset of the connection
    
  
  Escapes special characters in a string for use in an SQL statement, taking into account the
  current charset of the connection.

<comment>Param:</comment>
  <info>      </info>  <strong>$MYSQLND_UH_RES_MYSQLND_NAME</strong>  Mysqlnd connection handle. Do not modify!
  <info>string</info>  <strong>$escape_string              </strong>  The string to be escaped.

<comment>Return:</comment>
  <info>string</info>  The escaped string.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_real_escape_string()</strong>
   * <strong>mysql_real_escape_string()</strong>


id: MysqlndUhConnection::getAffectedRows
type: function
doc:
<comment>Description:</comment>
  Gets the number of affected rows in a previous MySQL operation
  
  Gets the number of affected rows in a previous MySQL operation.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>int</info>  Number of affected rows.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_affected_rows()</strong>
   * <strong>mysql_affected_rows()</strong>


id: MysqlndUhConnection::getErrorNumber
type: function
doc:
<comment>Description:</comment>
  Returns the error code for the most recent function call
  
  Returns the error code for the most recent function call.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>int</info>  Error code for the most recent function call.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>MysqlndUhConnection::getErrorString()</strong>
   * <strong>mysqli_errno()</strong>
   * <strong>mysql_errno()</strong>


id: MysqlndUhConnection::getErrorString
type: function
doc:
<comment>Description:</comment>
  Returns a string description of the last error
  
  Returns a string description of the last error.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>string</info>  Error string for the most recent function call.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>MysqlndUhConnection::getErrorNumber()</strong>
   * <strong>mysqli_error()</strong>
   * <strong>mysql_error()</strong>


id: MysqlndUhConnection::getFieldCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of columns for the most recent query
  
  Returns the number of columns for the most recent query.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>int</info>  Number of columns.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_field_count()</strong>


id: MysqlndUhConnection::getHostInformation
type: function
doc:
<comment>Description:</comment>
  Returns a string representing the type of connection used
  
  Returns a string representing the type of connection used.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>string</info>  Connection description.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_get_host_info()</strong>
   * <strong>mysql_get_host_info()</strong>


id: MysqlndUhConnection::getLastInsertId
type: function
doc:
<comment>Description:</comment>
  Returns the auto generated id used in the last query
  
  Returns the auto generated id used in the last query.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>int</info>  Last insert id.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_insert_id()</strong>
   * <strong>mysql_insert_id()</strong>


id: MysqlndUhConnection::getLastMessage
type: function
doc:
<comment>Description:</comment>
  Retrieves information about the most recently executed query
  
  Retrieves information about the most recently executed query.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>void</info>  Last message. Trying to return a string longer than 511 bytes will cause an error of the
        type <return>E_WARNING</return> and result in the string being truncated.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_info()</strong>
   * <strong>mysql_info()</strong>


id: MysqlndUhConnection::getProtocolInformation
type: function
doc:
<comment>Description:</comment>
  Returns the version of the MySQL protocol used
  
  Returns the version of the MySQL protocol used.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>string</info>  The protocol version.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_get_proto_info()</strong>
   * <strong>mysql_get_proto_info()</strong>


id: MysqlndUhConnection::getServerInformation
type: function
doc:
<comment>Description:</comment>
  Returns the version of the MySQL server
  
  Returns the version of the MySQL server.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>string</info>  The server version.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_get_server_info()</strong>
   * <strong>mysql_get_server_info()</strong>


id: MysqlndUhConnection::getServerStatistics
type: function
doc:
<comment>Description:</comment>
  Gets the current system status
  
  Gets the current system status.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>string</info>  The system status message.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_stat()</strong>
   * <strong>mysql_stat()</strong>


id: MysqlndUhConnection::getServerVersion
type: function
doc:
<comment>Description:</comment>
  Returns the version of the MySQL server as an integer
  
  Returns the version of the MySQL server as an integer.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>int</info>  The MySQL version.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_get_server_version()</strong>
   * <strong>mysql_get_server_version()</strong>


id: MysqlndUhConnection::getSqlstate
type: function
doc:
<comment>Description:</comment>
  Returns the SQLSTATE error from previous MySQL operation
  
  Returns the SQLSTATE error from previous MySQL operation.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>string</info>  The SQLSTATE code.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_sql_state()</strong>


id: MysqlndUhConnection::getStatistics
type: function
doc:
<comment>Description:</comment>
  Returns statistics about the client connection
  
  Returns statistics about the client connection.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>array</info>  Connection statistics collected by mysqlnd.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_get_connection_stats()</strong>


id: MysqlndUhConnection::getThreadId
type: function
doc:
<comment>Description:</comment>
  Returns the thread ID for the current connection
  
  Returns the thread ID for the current connection.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>int</info>  Connection thread id.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_thread_id()</strong>
   * <strong>mysql_thread_id()</strong>


id: MysqlndUhConnection::getWarningCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of warnings from the last query for the given link
  
  Returns the number of warnings from the last query for the given link.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>int</info>  Number of warnings.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_warning_count()</strong>


id: MysqlndUhConnection::init
type: function
doc:
<comment>Description:</comment>
  Initialize mysqlnd connection
  
  Initialize mysqlnd connection. This is an mysqlnd internal call to initialize the connection
  object.
  
  Failing to call the parent implementation may cause memory leaks or crash PHP. This is not
  considered a bug. Please, keep in mind that the <return>mysqlnd</return> library functions have never been designed
  to be exposed to the user space.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::killConnection
type: function
doc:
<comment>Description:</comment>
  Asks the server to kill a MySQL thread
  
  Asks the server to kill a MySQL thread.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>int               </info>  <strong>$pid       </strong>  Thread Id of the connection to be killed.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_kill()</strong>


id: MysqlndUhConnection::listFields
type: function
doc:
<comment>Description:</comment>
  List MySQL table fields
  
  List MySQL table fields.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$table     </strong>  The name of the table that's being queried.
  <info>                  </info>  <strong>$pattern   </strong>  Name pattern.

<comment>Return:</comment>
  <info>array</info>  

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysql_list_fields()</strong>


id: MysqlndUhConnection::listMethod
type: function
doc:
<comment>Description:</comment>
  Wrapper for assorted list commands
  
  Wrapper for assorted list commands.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection  </strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$query       </strong>  SHOW command to be executed.
  <info>string            </info>  <strong>$achtung_wild</strong>  
  <info>string            </info>  <strong>$par1        </strong>  

<comment>Return:</comment>
  <info>void</info>  TODO

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysql_list_dbs()</strong>


id: MysqlndUhConnection::moreResults
type: function
doc:
<comment>Description:</comment>
  Check if there are any more query results from a multi query
  
  Check if there are any more query results from a multi query.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_more_results()</strong>


id: MysqlndUhConnection::nextResult
type: function
doc:
<comment>Description:</comment>
  Prepare next result from multi_query
  
  Prepare next result from multi_query.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_next_result()</strong>


id: MysqlndUhConnection::ping
type: function
doc:
<comment>Description:</comment>
  Pings a server connection, or tries to reconnect if the connection has gone down
  
  Pings a server connection, or tries to reconnect if the connection has gone down.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_ping()</strong>
   * <strong>mysql_ping()</strong>


id: MysqlndUhConnection::query
type: function
doc:
<comment>Description:</comment>
  Performs a query on the database
  
  Performs a query on the database (COM_QUERY).

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$query     </strong>  The query string.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_query()</strong>
   * <strong>mysql_query()</strong>


id: MysqlndUhConnection::queryReadResultsetHeader
type: function
doc:
<comment>Description:</comment>
  Read a result set header
  
  Read a result set header.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection  </strong>  Mysqlnd connection handle. Do not modify!
  <info>mysqlnd_statement </info>  <strong>$mysqlnd_stmt</strong>  Mysqlnd statement handle. Do not modify! Set to <info>null</info>, if
                                     function is not used in the context of a prepared statement.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::reapQuery
type: function
doc:
<comment>Description:</comment>
  Get result from async query
  
  Get result from async query.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_real_async_query()</strong>


id: MysqlndUhConnection::refreshServer
type: function
doc:
<comment>Description:</comment>
  Flush or reset tables and caches
  
  Flush or reset tables and caches.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>int               </info>  <strong>$options   </strong>  What to refresh.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::restartPSession
type: function
doc:
<comment>Description:</comment>
  Restart a persistent mysqlnd connection
  
  Restart a persistent mysqlnd connection.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::selectDb
type: function
doc:
<comment>Description:</comment>
  Selects the default database for database queries
  
  Selects the default database for database queries.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$database  </strong>  The database name.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_select_db()</strong>
   * <strong>mysql_select_db()</strong>


id: MysqlndUhConnection::sendClose
type: function
doc:
<comment>Description:</comment>
  Sends a close command to MySQL
  
  Sends a close command to MySQL.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::sendQuery
type: function
doc:
<comment>Description:</comment>
  Sends a query to MySQL
  
  Sends a query to MySQL.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$query     </strong>  The query string.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::serverDumpDebugInformation
type: function
doc:
<comment>Description:</comment>
  Dump debugging information into the log for the MySQL server
  
  Dump debugging information into the log for the MySQL server.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_dump_debug_info()</strong>


id: MysqlndUhConnection::setAutocommit
type: function
doc:
<comment>Description:</comment>
  Turns on or off auto-committing database modifications
  
  Turns on or off auto-committing database modifications

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>int               </info>  <strong>$mode      </strong>  Whether to turn on auto-commit or not.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_autocommit()</strong>


id: MysqlndUhConnection::setCharset
type: function
doc:
<comment>Description:</comment>
  Sets the default client character set
  
  Sets the default client character set.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$charset   </strong>  The charset to be set as default.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_set_charset()</strong>


id: MysqlndUhConnection::setClientOption
type: function
doc:
<comment>Description:</comment>
  Sets a client option
  
  Sets a client option.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>int               </info>  <strong>$option    </strong>  The option to be set.
  <info>int               </info>  <strong>$value     </strong>  Optional option value, if required.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_real_connect()</strong>
   * <strong>mysqli_options()</strong>


id: MysqlndUhConnection::setServerOption
type: function
doc:
<comment>Description:</comment>
  Sets a server option
  
  Sets a server option.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>int               </info>  <strong>$option    </strong>  The option to be set.

<comment>Return:</comment>
  <info>void</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_real_connect()</strong>
   * <strong>mysqli_options()</strong>
   * <strong>mysqli_multi_query()</strong>


id: MysqlndUhConnection::shutdownServer
type: function
doc:
<comment>Description:</comment>
  The shutdownServer purpose
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$MYSQLND_UH_RES_MYSQLND_NAME</strong>  
  <info>string</info>  <strong>$level                      </strong>  

<comment>Return:</comment>
  <info>void</info>  


id: MysqlndUhConnection::simpleCommand
type: function
doc:
<comment>Description:</comment>
  Sends a basic COM_* command
  
  Sends a basic COM_* command to MySQL.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection          </strong>  Mysqlnd connection handle. Do not modify!
  <info>int               </info>  <strong>$command             </strong>  The COM command to be send.
  <info>string            </info>  <strong>$arg                 </strong>  Optional COM command arguments.
  <info>int               </info>  <strong>$ok_packet           </strong>  The OK packet type.
  <info>bool              </info>  <strong>$silent              </strong>  Whether mysqlnd may emit errors.
  <info>bool              </info>  <strong>$ignore_upsert_status</strong>  Whether to ignore <return>UPDATE</return>/<return>INSERT</return> status.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::simpleCommandHandleResponse
type: function
doc:
<comment>Description:</comment>
  Process a response for a basic COM_* command send to the client
  
  Process a response for a basic COM_* command send to the client.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection          </strong>  Mysqlnd connection handle. Do not modify!
  <info>int               </info>  <strong>$ok_packet           </strong>  The OK packet type.
  <info>bool              </info>  <strong>$silent              </strong>  Whether mysqlnd may emit errors.
  <info>int               </info>  <strong>$command             </strong>  The COM command to process results from.
  <info>bool              </info>  <strong>$ignore_upsert_status</strong>  Whether to ignore <return>UPDATE</return>/<return>INSERT</return> status.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

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


id: MysqlndUhConnection::sslSet
type: function
doc:
<comment>Description:</comment>
  Used for establishing secure connections using SSL
  
  Used for establishing secure connections using SSL.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!
  <info>string            </info>  <strong>$key       </strong>  The path name to the key file.
  <info>string            </info>  <strong>$cert      </strong>  The path name to the certificate file.
  <info>string            </info>  <strong>$ca        </strong>  The path name to the certificate authority file.
  <info>string            </info>  <strong>$capath    </strong>  The pathname to a directory that contains trusted SSL CA
                                   certificates in PEM format.
  <info>string            </info>  <strong>$cipher    </strong>  A list of allowable ciphers to use for SSL encryption.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_ssl_set()</strong>


id: MysqlndUhConnection::stmtInit
type: function
doc:
<comment>Description:</comment>
  Initializes a statement and returns a resource for use with mysqli_statement::prepare
  
  Initializes a statement and returns a resource for use with mysqli_statement::prepare.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>resource</info>  Resource of type <return>Mysqlnd Prepared Statement (internal only - you must not modify it!)</return>.
            The documentation may also refer to such resources using the alias name
            <return>mysqlnd_prepared_statement</return>.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_stmt_init()</strong>


id: MysqlndUhConnection::storeResult
type: function
doc:
<comment>Description:</comment>
  Transfers a result set from the last query
  
  Transfers a result set from the last query.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>resource</info>  Resource of type <return>Mysqlnd Resultset (internal only - you must not modify it!)</return>. The
            documentation may also refer to such resources using the alias name <return>mysqlnd_resultset</return>.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_store_result()</strong>
   * <strong>mysqli_real_query()</strong>


id: MysqlndUhConnection::txCommit
type: function
doc:
<comment>Description:</comment>
  Commits the current transaction
  
  Commits the current transaction.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_commit()</strong>


id: MysqlndUhConnection::txRollback
type: function
doc:
<comment>Description:</comment>
  Rolls back current transaction
  
  Rolls back current transaction.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_commit()</strong>


id: MysqlndUhConnection::useResult
type: function
doc:
<comment>Description:</comment>
  Initiate a result set retrieval
  
  Initiate a result set retrieval.

<comment>Param:</comment>
  <info>mysqlnd_connection</info>  <strong>$connection</strong>  Mysqlnd connection handle. Do not modify!

<comment>Return:</comment>
  <info>resource</info>  Resource of type <return>Mysqlnd Resultset (internal only - you must not modify it!)</return>. The
            documentation may also refer to such resources using the alias name <return>mysqlnd_resultset</return>.

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_connection_proxy()</strong>
   * <strong>mysqli_use_result()</strong>
   * <strong>mysqli_real_query()</strong>


id: MysqlndUhPreparedStatement::execute
type: function
doc:
<comment>Description:</comment>
  Executes a prepared Query
  
  Executes a prepared Query.

<comment>Param:</comment>
  <info>mysqlnd_prepared_statement</info>  <strong>$statement</strong>  Mysqlnd prepared statement handle. Do not modify! Resource
                                          of type <return>Mysqlnd Prepared Statement (internal only - you
                                          must not modify it!)</return>.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_statement_proxy()</strong>
   * <strong>mysqli_stmt_execute()</strong>


id: MysqlndUhPreparedStatement::prepare
type: function
doc:
<comment>Description:</comment>
  Prepare an SQL statement for execution
  
  Prepare an SQL statement for execution.

<comment>Param:</comment>
  <info>mysqlnd_prepared_statement</info>  <strong>$statement</strong>  Mysqlnd prepared statement handle. Do not modify! Resource
                                          of type <return>Mysqlnd Prepared Statement (internal only - you
                                          must not modify it!)</return>.
  <info>string                    </info>  <strong>$query    </strong>  The query to be prepared.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success. Otherwise, returns <info>false</info>

<comment>See Also:</comment>
   * <strong>mysqlnd_uh_set_statement_proxy()</strong>
   * <strong>mysqli_stmt_prepare()</strong>
   * <strong>mysqli_prepare()</strong>


id: NORM_IGNOREKASHIDA
type: constant
doc:
<comment>Description:</comment>
  Ignore Arabic kashida characters.
  
  Availability is dependent upon under lying library.


id: NoRewindIterator
type: class
doc:
<comment>Description:</comment>
  This iterator ignores rewind operations. This allows processing an iterator in multiple partial
  foreach loops.


id: NoRewindIterator::__construct
type: function
doc:
<comment>Description:</comment>
  Construct a NoRewindIterator
  
  Constructs a NoRewindIterator.

<comment>Param:</comment>
  <info>Iterator</info>  <strong>$iterator</strong>  The iterator being used.

<comment>Return:</comment>
  <info>unknown</info>  A NoRewindIterator based on the passed in <strong>$iterator</strong>.

<comment>See Also:</comment>
   * NoRewindIterator::valid


id: NoRewindIterator::current
type: function
doc:
<comment>Description:</comment>
  Get the current value
  
  Gets the current value.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>mixed</info>  The current value.

<comment>See Also:</comment>
   * NoRewindIterator::key


id: NoRewindIterator::getInnerIterator
type: function
doc:
<comment>Description:</comment>
  Get the inner iterator
  
  Gets the inner iterator, that was passed in to <class>NoRewindIterator</class>.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>iterator</info>  The inner iterator, as passed to NoRewindIterator::__construct.

<comment>See Also:</comment>
   * NoRewindIterator::valid


id: NoRewindIterator::key
type: function
doc:
<comment>Description:</comment>
  Get the current key
  
  Gets the current key.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>mixed</info>  The current key.

<comment>See Also:</comment>
   * NoRewindIterator::next


id: NoRewindIterator::next
type: function
doc:
<comment>Description:</comment>
  Forward to the next element
  
  Forwards to the next element.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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

<comment>See Also:</comment>
   * NoRewindIterator::rewind


id: NoRewindIterator::rewind
type: function
doc:
<comment>Description:</comment>
  Prevents the rewind operation on the inner iterator
  
  Prevents the rewind operation on the inner iterator.

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


id: NoRewindIterator::valid
type: function
doc:
<comment>Description:</comment>
  Validates the iterator
  
  Checks whether the iterator is valid.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<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>
   * NoRewindIterator::getInnerIterator


id: Normalizer
type: class
doc:
<comment>Description:</comment>
  Normalization is a process that involves transforming characters and sequences of characters into
  a formally-defined underlying representation. This process is most important when text needs to be
  compared for sorting and searching, but it is also used when storing text to ensure that the text
  is stored in a consistent representation.
  
  The Unicode Consortium has defined a number of normalization forms reflecting the various needs of
  applications: Normalization Form D (NFD) - Canonical Decomposition Normalization Form C (NFC) -
  Canonical Decomposition followed by Canonical Composition  Normalization Form KD (NFKD) -
  Compatibility Decomposition  Normalization Form KC (NFKC) - Compatibility Decomposition followed
  by Canonical Composition  The different forms are defined in terms of a set of transformations on
  the text, transformations that are expressed by both an algorithm and a set of data files.


id: Normalizer::FORM_C
type: constant
doc:
<comment>Description:</comment>
  Normalization Form C (NFC) - Canonical Decomposition followed by Canonical Composition


id: Normalizer::FORM_KC
type: constant
doc:
<comment>Description:</comment>
  Normalization Form KC (NFKC) - Compatibility Decomposition, followed by Canonical Composition


id: Normalizer::getRawDecomposition
type: function
doc:
<comment>Description:</comment>
  Gets the Decomposition_Mapping property for the given UTF-8 encoded code point
  
  Stil obiect-orientat
  
  Stil procedural
  
  Gets the Decomposition_Mapping property, as specified in the Unicode Character Database (UCD), for
  the given UTF-8 encoded code point.

<comment>Param:</comment>
  <info>string</info>  <strong>$input</strong>  The input string, which should be a single, UTF-8 encoded, code point.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> containing the Decomposition_Mapping property, if present in the UCD.
          
          Returns <info>null</info> if there is no Decomposition_Mapping property for the character.

<comment>See Also:</comment>
   * Normalizer::normalize
   * Normalizer::isNormalized


id: Normalizer::isNormalized
type: function
doc:
<comment>Description:</comment>
  Checks if the provided string is already in the specified normalization
     form
    
  
  Stil obiect-orientat
  
  Stil procedural
  
  Checks if the provided string is already in the specified normalization form.

<comment>Param:</comment>
  <info>string</info>  <strong>$input</strong>  The input string to normalize
  <info>int   </info>  <strong>$form </strong>  One of the normalization forms.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if normalized, <info>false</info> otherwise or if there an error

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


id: Normalizer::normalize
type: function
doc:
<comment>Description:</comment>
  Normalizes the input provided and returns the normalized string
    
  
  Stil obiect-orientat
  
  Stil procedural
  
  Normalizes the input provided and returns the normalized string

<comment>Param:</comment>
  <info>string</info>  <strong>$input</strong>  The input string to normalize
  <info>int   </info>  <strong>$form </strong>  One of the normalization forms.

<comment>Return:</comment>
  <info>string</info>  The normalized string or <info>false</info> if an error occurred.

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


id: NumberFormatter
type: class
doc:
<comment>Description:</comment>
  Programs store and operate on numbers using a locale-independent binary representation. When
  displaying or printing a number it is converted to a locale-specific string. For example, the
  number 12345.67 is "12,345.67" in the US, "12 345,67" in France and "12.345,67" in Germany.
  
  By invoking the methods provided by the NumberFormatter class, you can format numbers, currencies,
  and percentages according to the specified or default locale. NumberFormatter is locale-sensitive
  so you need to create a new NumberFormatter for each locale. NumberFormatter methods format
  primitive-type numbers, such as double and output the number as a locale-specific string.
  
  For currencies you can use currency format type to create a formatter that returns a string with
  the formatted number and the appropriate currency sign. Of course, the NumberFormatter class is
  unaware of exchange rates so, the number output is the same regardless of the specified currency.
  This means that the same number has different monetary values depending on the currency locale. If
  the number is 9988776.65 the results will be: 9 988 776,65 € in France9.988.776,65 € in
  Germany$9,988,776.65 in the United States
  
  In order to format percentages, create a locale-specific formatter with percentage format type.
  With this formatter, a decimal fraction such as 0.75 is displayed as 75%.
  
  For more complex formatting, like spelled-out numbers, the rule-based number formatters are used.


id: NumberFormatter::CURRENCY_ACCOUNTING
type: constant
doc:
<comment>Description:</comment>
  Currency format for accounting, e.g., <return>($3.00)</return> for negative currency amount instead of <return>-$3.00</return>.
  Available as of PHP 7.4.1 and ICU 53.


id: NumberFormatter::DEFAULT_RULESET
type: constant
doc:
<comment>Description:</comment>
  The default rule set. This is only available with rule-based formatters.


id: NumberFormatter::PADDING_POSITION
type: constant
doc:
<comment>Description:</comment>
  The position at which padding will take place. See pad position constants for possible argument
  values.


id: NumberFormatter::PUBLIC_RULESETS
type: constant
doc:
<comment>Description:</comment>
  The public rule sets. This is only available with rule-based formatters. This is a read-only
  attribute. The public rulesets are returned as a single string, with each ruleset name delimited
  by ';' (semicolon).


id: NumberFormatter::ROUND_HALFDOWN
type: constant
doc:
<comment>Description:</comment>
  Rounding mode to round towards "nearest neighbor" unless both neighbors are equidistant, in which
  case round down.


id: NumberFormatter::ROUND_HALFEVEN
type: constant
doc:
<comment>Description:</comment>
  Rounding mode to round towards the "nearest neighbor" unless both neighbors are equidistant, in
  which case, round towards the even neighbor.


id: NumberFormatter::ROUND_HALFUP
type: constant
doc:
<comment>Description:</comment>
  Rounding mode to round towards "nearest neighbor" unless both neighbors are equidistant, in which
  case round up.


id: NumberFormatter::__construct
type: function
doc:
<comment>Description:</comment>
  Create a number formatter
  
  Stil obiect-orientat (method)
  
  Stil procedural
  
  Stil obiect-orientat (constructor):
  
  Creates a number formatter.

<comment>Param:</comment>
  <info>string</info>  <strong>$locale </strong>  Locale in which the number would be formatted (locale name, e.g. en_CA).
  <info>int   </info>  <strong>$style  </strong>  Style of the formatting, one of the  format style constants. If
                    <info>NumberFormatter::PATTERN_DECIMAL</info> or <info>NumberFormatter::PATTERN_RULEBASED</info> is passed
                    then the number format is opened using the given pattern, which must conform to
                    the syntax described in ICU DecimalFormat documentation or ICU
                    RuleBasedNumberFormat documentation, respectively.
  <info>string</info>  <strong>$pattern</strong>  Pattern string if the chosen style requires a pattern.

<comment>Return:</comment>
  <info>NumberFormatter</info>  Returns <class>NumberFormatter</class> object or <info>false</info> on error.

<comment>See Also:</comment>
   * <strong>numfmt_format()</strong>
   * <strong>numfmt_parse()</strong>


id: NumberFormatter::format
type: function
doc:
<comment>Description:</comment>
  Format a number
  
  Stil obiect-orientat
  
  Stil procedural
  
  Format a numeric value according to the formatter rules.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt  </strong>  <class>NumberFormatter</class> object.
  <info>intfloat       </info>  <strong>$value</strong>  The value to format. Can be <info>int</info> or <info>float</info>, other values will be converted
                           to a numeric value.
  <info>int            </info>  <strong>$type </strong>  The  formatting type to use.

<comment>Return:</comment>
  <info>string</info>  Returns the string containing formatted value, or <info>false</info> on error.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_format_currency()</strong>
   * <strong>numfmt_parse()</strong>


id: NumberFormatter::formatCurrency
type: function
doc:
<comment>Description:</comment>
  Format a currency value
  
  Stil obiect-orientat
  
  Stil procedural
  
  Format the currency value according to the formatter rules.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt     </strong>  <class>NumberFormatter</class> object.
  <info>float          </info>  <strong>$value   </strong>  The numeric currency value.
  <info>string         </info>  <strong>$currency</strong>  The 3-letter ISO 4217 currency code indicating the currency to use.

<comment>Return:</comment>
  <info>stringfalse</info>  String representing the formatted currency value,  sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_format()</strong>
   * <strong>numfmt_parse_currency()</strong>


id: NumberFormatter::getAttribute
type: function
doc:
<comment>Description:</comment>
  Get an attribute
  
  Stil obiect-orientat
  
  Stil procedural
  
  Get a numeric attribute associated with the formatter. An example of a numeric attribute is the
  number of integer digits the formatter will produce.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$attr</strong>  Attribute specifier - one of the  numeric attribute constants.

<comment>Return:</comment>
  <info>int</info>  Return attribute value on success, or <info>false</info> on error.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_get_text_attribute()</strong>
   * <strong>numfmt_set_attribute()</strong>


id: NumberFormatter::getErrorCode
type: function
doc:
<comment>Description:</comment>
  Get formatter's last error code
  
  Stil obiect-orientat
  
  Stil procedural
  
  Get error code from the last function performed by the formatter.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt</strong>  <class>NumberFormatter</class> object.

<comment>Return:</comment>
  <info>int</info>  Returns error code from last formatter call.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_message()</strong>
   * <strong>intl_get_error_code()</strong>
   * <strong>intl_is_failure()</strong>


id: NumberFormatter::getErrorMessage
type: function
doc:
<comment>Description:</comment>
  Get formatter's last error message
  
  Stil obiect-orientat
  
  Stil procedural
  
  Get error message from the last function performed by the formatter.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt</strong>  <class>NumberFormatter</class> object.

<comment>Return:</comment>
  <info>string</info>  Returns error message from last formatter call.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>intl_get_error_code()</strong>
   * <strong>intl_is_failure()</strong>


id: NumberFormatter::getLocale
type: function
doc:
<comment>Description:</comment>
  Get formatter locale
  
  Stil obiect-orientat
  
  Stil procedural
  
  Get formatter locale name.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$type</strong>  You can choose between valid and actual locale ( <info>Locale::VALID_LOCALE</info>,
                          <info>Locale::ACTUAL_LOCALE</info>, respectively). The default is the actual locale.

<comment>Return:</comment>
  <info>string</info>  The locale name used to create the formatter.

<comment>See Also:</comment>
   * <strong>numfmt_create()</strong>
   * <strong>numfmt_get_error_code()</strong>


id: NumberFormatter::getPattern
type: function
doc:
<comment>Description:</comment>
  Get formatter pattern
  
  Stil obiect-orientat
  
  Stil procedural
  
  Extract pattern used by the formatter.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt</strong>  <class>NumberFormatter</class> object.

<comment>Return:</comment>
  <info>string</info>  Pattern <info>string</info> that is used by the formatter, or <info>false</info> if an error happens.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_set_pattern()</strong>
   * <strong>numfmt_create()</strong>


id: NumberFormatter::getSymbol
type: function
doc:
<comment>Description:</comment>
  Get a symbol value
  
  Stil obiect-orientat
  
  Stil procedural
  
  Get a symbol associated with the formatter. The formatter uses symbols to represent the special
  locale-dependent characters in a number, for example the percent sign. This API is not supported
  for rule-based formatters.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$attr</strong>  Symbol specifier, one of the  format symbol constants.

<comment>Return:</comment>
  <info>string</info>  The symbol string or <info>false</info> on error.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_set_symbol()</strong>


id: NumberFormatter::getTextAttribute
type: function
doc:
<comment>Description:</comment>
  Get a text attribute
  
  Stil obiect-orientat
  
  Stil procedural
  
  Get a text attribute associated with the formatter. An example of a text attribute is the suffix
  for positive numbers. If the formatter does not understand the attribute, <info>U_UNSUPPORTED_ERROR</info>
  error is produced. Rule-based formatters only understand <info>NumberFormatter::DEFAULT_RULESET</info> and
  <info>NumberFormatter::PUBLIC_RULESETS</info>.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$attr</strong>  Attribute specifier - one of the  text attribute constants.

<comment>Return:</comment>
  <info>string</info>  Return attribute value on success, or <info>false</info> on error.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_get_attribute()</strong>
   * <strong>numfmt_set_text_attribute()</strong>


id: NumberFormatter::parse
type: function
doc:
<comment>Description:</comment>
  Parse a number
  
  Stil obiect-orientat
  
  Stil procedural
  
  Parse a string into a number using the current formatter rules.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt     </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$type    </strong>  The  formatting type to use. By default, <info>NumberFormatter::TYPE_DOUBLE</info>
                              is used.
  <info>int            </info>  <strong>$position</strong>  Offset in the string at which to begin parsing. On return, this value
                              will hold the offset at which parsing ended.

<comment>Return:</comment>
  <info>mixed</info>  The value of the parsed number or <info>false</info> on error.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_format()</strong>
   * <strong>numfmt_parse_currency()</strong>


id: NumberFormatter::parseCurrency
type: function
doc:
<comment>Description:</comment>
  Parse a currency number
  
  Stil obiect-orientat
  
  Stil procedural
  
  Parse a string into a double and a currency using the current formatter.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt     </strong>  <class>NumberFormatter</class> object.
  <info>string         </info>  <strong>$currency</strong>  Parameter to receive the currency name (3-letter ISO 4217 currency
                              code).
  <info>int            </info>  <strong>$position</strong>  Offset in the string at which to begin parsing. On return, this value
                              will hold the offset at which parsing ended.

<comment>Return:</comment>
  <info>float</info>  The parsed numeric value or <info>false</info> on error.

<comment>See Also:</comment>
   * <strong>numfmt_get_error_code()</strong>
   * <strong>numfmt_parse()</strong>
   * <strong>numfmt_format_currency()</strong>


id: NumberFormatter::setAttribute
type: function
doc:
<comment>Description:</comment>
  Set an attribute
  
  Stil obiect-orientat
  
  Stil procedural
  
  Set a numeric attribute associated with the formatter. An example of a numeric attribute is the
  number of integer digits the formatter will produce.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt  </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$attr </strong>  Attribute specifier - one of the  numeric attribute constants.
  <info>int            </info>  <strong>$value</strong>  The attribute value.

<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>numfmt_get_error_code()</strong>
   * <strong>numfmt_get_attribute()</strong>
   * <strong>numfmt_set_text_attribute()</strong>


id: NumberFormatter::setPattern
type: function
doc:
<comment>Description:</comment>
  Set formatter pattern
  
  Stil obiect-orientat
  
  Stil procedural
  
  Set the pattern used by the formatter. Can not be used on a rule-based formatter.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt    </strong>  <class>NumberFormatter</class> object.
  <info>string         </info>  <strong>$pattern</strong>  Pattern in syntax described in ICU DecimalFormat documentation.

<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>numfmt_get_error_code()</strong>
   * <strong>numfmt_create()</strong>
   * <strong>numfmt_get_pattern()</strong>


id: NumberFormatter::setSymbol
type: function
doc:
<comment>Description:</comment>
  Set a symbol value
  
  Stil obiect-orientat
  
  Stil procedural
  
  Set a symbol associated with the formatter. The formatter uses symbols to represent the special
  locale-dependent characters in a number, for example the percent sign. This API is not supported
  for rule-based formatters.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt  </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$attr </strong>  Symbol specifier, one of the  format symbol constants.
  <info>string         </info>  <strong>$value</strong>  Text for the symbol.

<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>numfmt_get_error_code()</strong>
   * <strong>numfmt_get_symbol()</strong>


id: NumberFormatter::setTextAttribute
type: function
doc:
<comment>Description:</comment>
  Set a text attribute
  
  Stil obiect-orientat
  
  Stil procedural
  
  Set a text attribute associated with the formatter. An example of a text attribute is the suffix
  for positive numbers. If the formatter does not understand the attribute, <info>U_UNSUPPORTED_ERROR</info>
  error is produced. Rule-based formatters only understand <info>NumberFormatter::DEFAULT_RULESET</info> and
  <info>NumberFormatter::PUBLIC_RULESETS</info>.

<comment>Param:</comment>
  <info>NumberFormatter</info>  <strong>$fmt  </strong>  <class>NumberFormatter</class> object.
  <info>int            </info>  <strong>$attr </strong>  Attribute specifier - one of the text attribute constants.
  <info>string         </info>  <strong>$value</strong>  Text for the attribute value.

<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>numfmt_get_error_code()</strong>
   * <strong>numfmt_get_text_attribute()</strong>
   * <strong>numfmt_set_attribute()</strong>


id: OAUTH_AUTH_TYPE_AUTHORIZATION
type: constant
doc:
<comment>Description:</comment>
  This constant represents putting OAuth parameters in the <return>Authorization</return> header.


id: OAUTH_AUTH_TYPE_FORM
type: constant
doc:
<comment>Description:</comment>
  This constant represents putting OAuth parameters as part of the HTTP POST body.


id: OAUTH_AUTH_TYPE_URI
type: constant
doc:
<comment>Description:</comment>
  This constant represents putting OAuth parameters in the request URI.


id: OAUTH_BAD_NONCE
type: constant
doc:
<comment>Description:</comment>
  The oauth_nonce value was used in a previous request, therefore it cannot be used now.


id: OAUTH_BAD_TIMESTAMP
type: constant
doc:
<comment>Description:</comment>
  The oauth_timestamp value was not accepted by the service provider. In this case, the response
  should also contain the oauth_acceptable_timestamps parameter.


id: OAUTH_CONSUMER_KEY_UNKNOWN
type: constant
doc:
<comment>Description:</comment>
  The oauth_consumer_key is temporarily unacceptable to the service provider. For example, the
  service provider may be throttling the consumer.


id: OAUTH_INVALID_SIGNATURE
type: constant
doc:
<comment>Description:</comment>
  The oauth_signature is invalid, as it does not match the signature computed by the service
  provider.


id: OAUTH_PARAMETER_ABSENT
type: constant
doc:
<comment>Description:</comment>
  A required parameter was not received. In this case, the response should also contain the
  oauth_parameters_absent parameter.


id: OAUTH_REQENGINE_CURL
type: constant
doc:
<comment>Description:</comment>
  Used by OAuth::setRequestEngine to set the engine to  Curl, as opposed to  <info>OAUTH_REQENGINE_STREAMS</info>
  for PHP streams.


id: OAUTH_REQENGINE_STREAMS
type: constant
doc:
<comment>Description:</comment>
  Used by OAuth::setRequestEngine to set the engine to  PHP streams, as opposed to
  <info>OAUTH_REQENGINE_CURL</info> for  Curl.


id: OAUTH_TOKEN_REJECTED
type: constant
doc:
<comment>Description:</comment>
  The oauth_token was not accepted by the service provider. The reason is not known, but it might be
  because the token was never issued, already consumed, expired, and/or forgotten by the service
  provider.


id: OAUTH_TOKEN_USED
type: constant
doc:
<comment>Description:</comment>
  The oauth_token has been consumed. It can no longer be used because it has already been used in
  the previous request(s).


id: OAuth
type: class
doc:
<comment>Description:</comment>
  The OAuth extension provides a simple interface to interact with data providers using the OAuth
  HTTP specification to protect private resources.


id: OAuth::__construct
type: function
doc:
<comment>Description:</comment>
  Create a new OAuth object
  
  Creates a new OAuth object

<comment>Param:</comment>
  <info>string</info>  <strong>$consumer_key    </strong>  The consumer key provided by the service provider.
  <info>string</info>  <strong>$consumer_secret </strong>  The consumer secret provided by the service provider.
  <info>string</info>  <strong>$signature_method</strong>  This optional parameter defines which signature method to use, by
                             default it is <info>OAUTH_SIG_METHOD_HMACSHA1</info> (HMAC-SHA1).
  <info>int   </info>  <strong>$auth_type       </strong>  This optional parameter defines how to pass the OAuth parameters to a
                             consumer, by default it is <info>OAUTH_AUTH_TYPE_AUTHORIZATION</info> (in the
                             <return>Authorization</return> header).


id: OAuth::__destruct
type: function
doc:
<comment>Description:</comment>
  The destructor
  
  The destructor.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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

<comment>See Also:</comment>
   * OAuth::__construct


id: OAuth::disableDebug
type: function
doc:
<comment>Description:</comment>
  Turn off verbose debugging
  
  Turns off verbose request information (off by default). Alternatively, the debug property can be
  set to a <info>false</info> value to turn debug off.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuth::enableDebug


id: OAuth::disableRedirects
type: function
doc:
<comment>Description:</comment>
  Turn off redirects
  
  Disable redirects from being followed automatically, thus allowing the request to be manually
  redirected.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuth::enableRedirects


id: OAuth::disableSSLChecks
type: function
doc:
<comment>Description:</comment>
  Turn off SSL checks
  
  Turns off the usual SSL peer certificate and host checks, this is not for production environments.
  Alternatively, the <strong>$sslChecks</strong> member can be set to <info>false</info> to turn SSL checks off.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuth::enableSSLChecks


id: OAuth::enableDebug
type: function
doc:
<comment>Description:</comment>
  Turn on verbose debugging
  
  Turns on verbose request information useful for debugging, the debug information is stored in the
  <strong>$debugInfo</strong> member. Alternatively, the <strong>$debug</strong> member can  be set to a non-<info>false</info> value to turn debug
  on.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuth::disableDebug


id: OAuth::enableRedirects
type: function
doc:
<comment>Description:</comment>
  Turn on redirects
  
  Follow and sign redirects automatically, which is enabled by default.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuth::disableRedirects


id: OAuth::enableSSLChecks
type: function
doc:
<comment>Description:</comment>
  Turn on SSL checks
  
  Turns on the usual SSL peer certificate and host checks (enabled by default). Alternatively, the
  <strong>$sslChecks</strong> member can be set to a non-<info>false</info> value to turn SSL checks off.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuth::disableSSLChecks


id: OAuth::fetch
type: function
doc:
<comment>Description:</comment>
  Fetch an OAuth protected resource
  
  Fetch a resource.

<comment>Param:</comment>
  <info>string</info>  <strong>$protected_resource_url</strong>  URL to the OAuth protected resource.
  <info>array </info>  <strong>$extra_parameters      </strong>  Extra parameters to send with the request for the resource.
  <info>string</info>  <strong>$http_method           </strong>  One of the <info>OAUTH_HTTP_METHOD_*</info> OAUTH constants, which includes
                                   GET, POST, PUT, HEAD, or DELETE.
                                   
                                   HEAD (<info>OAUTH_HTTP_METHOD_HEAD</info>) can be useful for discovering
                                   information prior to the request (if OAuth credentials are in the
                                   <return>Authorization</return> header).
  <info>array </info>  <strong>$http_headers          </strong>  HTTP client headers (such as User-Agent, Accept, etc.)

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

<comment>See Also:</comment>
   * OAuth::getLastResponse
   * OAuth::getLastResponseInfo
   * OAuth::setToken


id: OAuth::generateSignature
type: function
doc:
<comment>Description:</comment>
  Generate a signature
  
  Generate a signature based on the final HTTP method, URL and a string/array of parameters.

<comment>Param:</comment>
  <info>string</info>  <strong>$http_method     </strong>  HTTP method for request
  <info>string</info>  <strong>$url             </strong>  URL for request
  <info>mixed </info>  <strong>$extra_parameters</strong>  String or array of additional parameters.

<comment>Return:</comment>
  <info>stringfalse</info>  A string containing the generated signature sau <info>false</info> în cazul eșecului


id: OAuth::getAccessToken
type: function
doc:
<comment>Description:</comment>
  Fetch an access token
  
  Fetch an access token, secret and any additional response parameters from the service provider.

<comment>Param:</comment>
  <info>string</info>  <strong>$access_token_url   </strong>  URL to the access token API.
  <info>string</info>  <strong>$auth_session_handle</strong>  Authorization session handle, this parameter does not have any
                                citation in the core OAuth 1.0 specification but may be  implemented
                                by large providers.  See ScalableOAuth for more information.
  <info>string</info>  <strong>$verifier_token     </strong>  For service providers which support 1.0a, a <strong>$verifier_token</strong> must be
                                passed while exchanging the request token for the access token. If
                                the <strong>$verifier_token</strong> is present in <strong>$_GET</strong>  or <strong>$_POST</strong> it is passed
                                automatically and the caller  does not need to specify a
                                <strong>$verifier_token</strong> (usually if the access token  is exchanged at the
                                oauth_callback URL). See ScalableOAuth for more information.
  <info>string</info>  <strong>$http_method        </strong>  HTTP method to use, e.g. <return>GET</return> or <return>POST</return>.

<comment>Return:</comment>
  <info>array</info>  Returns an array containing the parsed OAuth response on success or <info>false</info> on failure.

<comment>See Also:</comment>
   * OAuth::getLastResponse
   * OAuth::getLastResponseInfo
   * OAuth::setToken


id: OAuth::getCAPath
type: function
doc:
<comment>Description:</comment>
  Gets CA information
  
  Gets the Certificate Authority information, which includes the ca_path and ca_info set by
  OAuth::setCaPath.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>array</info>  An <info>array</info> of Certificate Authority information, specifically as <return>ca_path</return> and <return>ca_info</return> keys
         within the returned associative array.

<comment>See Also:</comment>
   * OAuth::setCAPath
   * OAuth::getLastResponseInfo


id: OAuth::getLastResponse
type: function
doc:
<comment>Description:</comment>
  Get the last response
  
  Get the raw response of the most recent request.

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the last response.

<comment>See Also:</comment>
   * OAuth::getLastResponseInfo
   * OAuth::fetch


id: OAuth::getLastResponseHeaders
type: function
doc:
<comment>Description:</comment>
  Get headers for last response
  
  Get headers for last response.

<comment>Return:</comment>
  <info>stringfalse</info>  A string containing the last response's headers sau <info>false</info> în cazul eșecului


id: OAuth::getLastResponseInfo
type: function
doc:
<comment>Description:</comment>
  Get HTTP information about the last response
  
  Get HTTP information about the last response.

<comment>Return:</comment>
  <info>array</info>  Returns an array containing the response information for the last request. Constants from
         <strong>curl_getinfo()</strong> may be used.

<comment>See Also:</comment>
   * OAuth::fetch
   * OAuth::getLastResponse


id: OAuth::getRequestHeader
type: function
doc:
<comment>Description:</comment>
  Generate OAuth header string signature
  
  Generate OAuth header string signature based on the final HTTP method, URL and a string/array of
  parameters

<comment>Param:</comment>
  <info>string</info>  <strong>$http_method     </strong>  HTTP method for request.
  <info>string</info>  <strong>$url             </strong>  URL for request.
  <info>mixed </info>  <strong>$extra_parameters</strong>  String or array of additional parameters.

<comment>Return:</comment>
  <info>stringfalse</info>  A string containing the generated request header sau <info>false</info> în cazul eșecului


id: OAuth::getRequestToken
type: function
doc:
<comment>Description:</comment>
  Fetch a request token
  
  Fetch a request token, secret and any additional response parameters from the service provider.

<comment>Param:</comment>
  <info>string</info>  <strong>$request_token_url</strong>  URL to the request token API.
  <info>string</info>  <strong>$callback_url     </strong>  OAuth callback URL. If <strong>$callback_url</strong> is passed and is an empty value,
                              it is set to "oob" to address the OAuth 2009.1 advisory.
  <info>string</info>  <strong>$http_method      </strong>  HTTP method to use, e.g. <return>GET</return> or <return>POST</return>.

<comment>Return:</comment>
  <info>array</info>  Returns an array containing the parsed OAuth response on success or <info>false</info> on failure.

<comment>See Also:</comment>
   * OAuth::getLastResponse
   * OAuth::getLastResponseInfo


id: OAuth::setAuthType
type: function
doc:
<comment>Description:</comment>
  Set authorization type
  
  Set where the OAuth parameters should be passed.

<comment>Param:</comment>
  <info>int</info>  <strong>$auth_type</strong>  <strong>$auth_type</strong> can be one of the following flags (in order of decreasing preference
                   as per OAuth 1.0 section 5.2): <info>OAUTH_AUTH_TYPE_AUTHORIZATION</info> Pass the OAuth
                   parameters in the HTTP <return>Authorization</return> header. <info>OAUTH_AUTH_TYPE_FORM</info> Append the
                   OAuth parameters to the HTTP POST request body. <info>OAUTH_AUTH_TYPE_URI</info> Append the
                   OAuth parameters to the request URI. <info>OAUTH_AUTH_TYPE_NONE</info> None.
                   
                   Pass the OAuth parameters in the HTTP <return>Authorization</return> header.
                   
                   Append the OAuth parameters to the HTTP POST request body.
                   
                   Append the OAuth parameters to the request URI.
                   
                   None.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if a parameter is correctly set, otherwise <info>false</info> (e.g., if an invalid
        <strong>$auth_type</strong> is passed in.)


id: OAuth::setCAPath
type: function
doc:
<comment>Description:</comment>
  Set CA path and info
  
  Sets the Certificate Authority (CA), both for path and info.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$ca_path</strong>  The CA Path being set.
  <info>string</info>  <strong>$ca_info</strong>  The CA Info being set.

<comment>Return:</comment>
  <info>mixed</info>  Returns <info>true</info> on success, or <info>false</info> if either <strong>$ca_path</strong> or <strong>$ca_info</strong> are considered invalid.

<comment>See Also:</comment>
   * OAuth::getCaPath


id: OAuth::setNonce
type: function
doc:
<comment>Description:</comment>
  Set the nonce for subsequent requests
  
  Sets the nonce for all subsequent requests.

<comment>Param:</comment>
  <info>string</info>  <strong>$nonce</strong>  The value for oauth_nonce.

<comment>Return:</comment>
  <info>mixed</info>  Returns <info>true</info> on success, or <info>false</info> if the <strong>$nonce</strong> is considered invalid.

<comment>See Also:</comment>
   * OAuth::setToken
   * OAuth::setAuthType
   * OAuth::setVersion


id: OAuth::setRSACertificate
type: function
doc:
<comment>Description:</comment>
  Set the RSA certificate
  
  Sets the RSA certificate.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$cert</strong>  The RSA certificate.

<comment>Return:</comment>
  <info>mixed</info>  Returns <info>true</info> on success, or <info>false</info> on failure (e.g., the RSA certificate cannot be parsed.)

<comment>See Also:</comment>
   * OAuth::setCaPath


id: OAuth::setRequestEngine
type: function
doc:
<comment>Description:</comment>
  The setRequestEngine purpose
  
  Sets the Request Engine, that will be sending the HTTP requests.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>int</info>  <strong>$reqengine</strong>  The desired request engine. Set to <info>OAUTH_REQENGINE_STREAMS</info> to use PHP Streams, or
                   <info>OAUTH_REQENGINE_CURL</info> to use Curl.

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

<comment>See Also:</comment>
   * Curl
   * PHP streams
   * <class>OAuthException</class>


id: OAuth::setSSLChecks
type: function
doc:
<comment>Description:</comment>
  Tweak specific SSL checks for requests
  
  Tweak specific SSL checks for requests.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>int</info>  <strong>$sslcheck</strong>  

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


id: OAuth::setTimestamp
type: function
doc:
<comment>Description:</comment>
  Set the timestamp
  
  Sets the OAuth timestamp for subsequent requests.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$timestamp</strong>  The timestamp.

<comment>Return:</comment>
  <info>mixed</info>  Returns <info>true</info>, unless the <strong>$timestamp</strong> is invalid, in which case <info>false</info> is returned.

<comment>See Also:</comment>
   * OAuth::setNonce


id: OAuth::setToken
type: function
doc:
<comment>Description:</comment>
  Sets the token and secret
  
  Set the token and secret for subsequent requests.

<comment>Param:</comment>
  <info>string</info>  <strong>$token       </strong>  The OAuth token.
  <info>string</info>  <strong>$token_secret</strong>  The OAuth token secret.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>


id: OAuth::setVersion
type: function
doc:
<comment>Description:</comment>
  Set the OAuth version
  
  Sets the OAuth version for subsequent requests

<comment>Param:</comment>
  <info>string</info>  <strong>$version</strong>  OAuth version, default value is always "1.0"

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


id: OAuthException
type: class
doc:
<comment>Description:</comment>
  This exception is thrown when exceptional errors occur while using the OAuth extension and
  contains useful debugging information.


id: OAuthProvider
type: class
doc:
<comment>Description:</comment>
  Manages an OAuth provider class.
  
  See also an external in-depth tutorial titled Writing an OAuth Provider Service, which takes a
  hands-on approach to providing this service. There are also  OAuth provider examples within the
  OAuth extensions sources.


id: OAuthProvider::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a new OAuthProvider object
  
  Initiates a new <class>OAuthProvider</class> <info>object</info>.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>array</info>  <strong>$params_array</strong>  Setting these optional parameters is limited to the CLI SAPI.

<comment>Return:</comment>
  <info>unknown</info>  An <class>OAuthProvider</class> <info>object</info>.

<comment>See Also:</comment>
   * OAuthProvider::setParam


id: OAuthProvider::addRequiredParameter
type: function
doc:
<comment>Description:</comment>
  Add required parameters
  
  Add required oauth provider parameters.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$req_params</strong>  The required parameters.

<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>
   * OAuthProvider::removeRequiredParameter


id: OAuthProvider::callTimestampNonceHandler
type: function
doc:
<comment>Description:</comment>
  Calls the timestampNonceHandler callback
  
  Calls the registered timestamp handler callback function, which is set with
  OAuthProvider::timestampNonceHandler.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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

<comment>See Also:</comment>
   * OAuthProvider::timestampNonceHandler


id: OAuthProvider::callconsumerHandler
type: function
doc:
<comment>Description:</comment>
  Calls the consumerNonceHandler callback
  
  Calls the registered consumer handler callback function, which is set with
  OAuthProvider::consumerHandler.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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

<comment>See Also:</comment>
   * OAuthProvider::consumerHandler


id: OAuthProvider::calltokenHandler
type: function
doc:
<comment>Description:</comment>
  Calls the tokenNonceHandler callback
  
  Calls the registered token handler callback function, which is set with
  OAuthProvider::tokenHandler.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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

<comment>See Also:</comment>
   * OAuthProvider::tokenHandler


id: OAuthProvider::checkOAuthRequest
type: function
doc:
<comment>Description:</comment>
  Check an oauth request
  
  Checks an OAuth request.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$uri   </strong>  The optional URI, or endpoint.
  <info>string</info>  <strong>$method</strong>  The HTTP method. Optionally pass in one of the  <info>OAUTH_HTTP_METHOD_*</info> OAuth
                   constants.

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

<comment>See Also:</comment>
   * OAuthProvider::reportProblem


id: OAuthProvider::consumerHandler
type: function
doc:
<comment>Description:</comment>
  Set the consumerHandler handler callback
  
  Sets the consumer handler callback, which will later be called with
  OAuthProvider::callConsumerHandler.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>callable</info>  <strong>$callback_function</strong>  The <info>callable</info> functions name.

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

<comment>See Also:</comment>
   * OAuthProvider::callConsumerHandler


id: OAuthProvider::generateToken
type: function
doc:
<comment>Description:</comment>
  Generate a random token
  
  Generates a <info>string</info> of pseudo-random bytes.

<comment>Param:</comment>
  <info>int </info>  <strong>$size  </strong>  The desired token length, in terms of bytes.
  <info>bool</info>  <strong>$strong</strong>  Setting to <info>true</info> means <return>/dev/random</return> will be used for entropy, as otherwise the
                 non-blocking <return>/dev/urandom</return> is used. This parameter is ignored on Windows.

<comment>Return:</comment>
  <info>string</info>  The generated token, as a <info>string</info> of bytes.

<comment>See Also:</comment>
   * <strong>openssl_random_pseudo_bytes()</strong>
   * <strong>mcrypt_create_iv()</strong>


id: OAuthProvider::is2LeggedEndpoint
type: function
doc:
<comment>Description:</comment>
  is2LeggedEndpoint
  
  The 2-legged flow, or request signing. It does not require a token.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$params_array</strong>  

<comment>Return:</comment>
  <info>void</info>  An <class>OAuthProvider</class> <info>object</info>.

<comment>See Also:</comment>
   * OAuthProvider::__construct


id: OAuthProvider::isRequestTokenEndpoint
type: function
doc:
<comment>Description:</comment>
  Sets isRequestTokenEndpoint
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>bool</info>  <strong>$will_issue_request_token</strong>  Sets whether or not it will issue a request token, thus
                                   determining if OAuthProvider::tokenHandler needs to be called.

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

<comment>See Also:</comment>
   * OAuthProvider::setRequestTokenPath
   * OAuthProvider::reportProblem


id: OAuthProvider::removeRequiredParameter
type: function
doc:
<comment>Description:</comment>
  Remove a required parameter
  
  Removes a required parameter.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$req_params</strong>  The required parameter to be removed.

<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>
   * OAuthProvider::setParam
   * OAuthProvider::addRequiredParameter


id: OAuthProvider::reportProblem
type: function
doc:
<comment>Description:</comment>
  Report a problem
  
  Pass in a problem as an <class>OAuthException</class>, with possible problems listed in the OAuth constants
  section.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$oauthexception</strong>  The <class>OAuthException</class>.

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

<comment>See Also:</comment>
   * OAuthProvider::checkOAuthRequest
   * OAuthProvider::isRequestTokenEndpoint


id: OAuthProvider::setParam
type: function
doc:
<comment>Description:</comment>
  Set a parameter
  
  Sets a parameter.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$param_key</strong>  The parameter key.
  <info>mixed </info>  <strong>$param_val</strong>  The optional parameter value.
                      
                      To exclude a parameter from signature verification, set its value to <info>null</info>.

<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>
   * OAuthProvider::addRequiredParameter


id: OAuthProvider::setRequestTokenPath
type: function
doc:
<comment>Description:</comment>
  Set request token path
  
  Sets the request tokens path.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>string</info>  <strong>$path</strong>  The path.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info>

<comment>See Also:</comment>
   * OAuthProvider::tokenHandler


id: OAuthProvider::timestampNonceHandler
type: function
doc:
<comment>Description:</comment>
  Set the timestampNonceHandler handler callback
  
  Sets the timestamp nonce handler callback, which will later be called with
  OAuthProvider::callTimestampNonceHandler. Errors related to timestamp/nonce are thrown to this
  callback.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>callable</info>  <strong>$callback_function</strong>  The <info>callable</info> functions name.

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

<comment>See Also:</comment>
   * OAuthProvider::callTimestampNonceHandler


id: OAuthProvider::tokenHandler
type: function
doc:
<comment>Description:</comment>
  Set the tokenHandler handler callback
  
  Sets the token handler callback, which will later be called with OAuthProvider::callTokenHandler.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>callable</info>  <strong>$callback_function</strong>  The <info>callable</info> functions name.

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

<comment>See Also:</comment>
   * OAuthProvider::callTokenHandler


id: OCICollection
type: class
doc:
<comment>Description:</comment>
  OCI8 Collection functionality.
  
  The OCI-Collection class was renamed to OCICollection in PHP 8 OCI8 3.0.0 to align with PHP naming
  standards.


id: OCICollection::append
type: function
doc:
<comment>Description:</comment>
  Appends element to the collection
  
  Appends element to the end of the collection.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$value</strong>  The value to be added to the collection. Can be a string or a number.

<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>
   * 


id: OCICollection::assign
type: function
doc:
<comment>Description:</comment>
  Assigns a value to the collection from another existing collection
  
  Assigns a value to the collection from another, previously created collection. Both collections
  must be created with  <strong>oci_new_collection()</strong> prior to using them.

<comment>Param:</comment>
  <info>OCICollection</info>  <strong>$from</strong>  An instance of OCI-Collection.

<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>
   * 


id: OCICollection::assignElem
type: function
doc:
<comment>Description:</comment>
  Assigns a value to the element of the collection
  
  Assigns a value to the element with index <strong>$index</strong>.

<comment>Param:</comment>
  <info>int  </info>  <strong>$index</strong>  The element index. First index is 0.
  <info>mixed</info>  <strong>$value</strong>  Can be a string or a number.

<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>
   * 


id: OCICollection::free
type: function
doc:
<comment>Description:</comment>
  Frees the resources associated with the collection object
  
  Frees the resources associated with the collection object.

<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>
   * 


id: OCICollection::getElem
type: function
doc:
<comment>Description:</comment>
  Returns value of the element
  
  Returns element's value with the index <strong>$index</strong> (0-based).

<comment>Param:</comment>
  <info>int</info>  <strong>$index</strong>  The element index. First index is 0.

<comment>Return:</comment>
  <info>mixed</info>  Returns <info>false</info> if such element doesn't exist; <info>null</info> if element is <info>null</info>; string if element is
         column of a string datatype or number if element is numeric field.

<comment>See Also:</comment>
   * 


id: OCICollection::max
type: function
doc:
<comment>Description:</comment>
  Returns the maximum number of elements in the collection
  
  Returns the maximum number of elements in the collection.

<comment>Return:</comment>
  <info>int</info>  Returns the maximum number as an integer, or <info>false</info> on errors.
       
       If the returned value is 0, then the number of elements is not limited.

<comment>See Also:</comment>
   * 


id: OCICollection::size
type: function
doc:
<comment>Description:</comment>
  Returns size of the collection
  
  Returns the size of the collection.

<comment>Return:</comment>
  <info>int</info>  Returns the number of elements in the collection or <info>false</info> on error.

<comment>See Also:</comment>
   * 


id: OCICollection::trim
type: function
doc:
<comment>Description:</comment>
  Trims elements from the end of the collection
  
  Trims <strong>$num</strong> of elements from the end of the collection.

<comment>Param:</comment>
  <info>int</info>  <strong>$num</strong>  The number of elements to be trimmed.

<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>
   * 


id: OCILob
type: class
doc:
<comment>Description:</comment>
  OCI8 LOB functionality for large binary (BLOB) and character (CLOB) objects.
  
  The OCI-Lob class was renamed to OCILob in PHP 8 and PECL OCI8 3.0.0 to align with PHP naming
  standards.


id: OCILob::eof
type: function
doc:
<comment>Description:</comment>
  Tests for end-of-file on a large object's descriptor
  
  Tells whether the internal pointer of large object is at the end of LOB.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if internal pointer of large object is at the end of LOB. Otherwise returns
        <info>false</info>.

<comment>See Also:</comment>
   * 


id: OCILob::erase
type: function
doc:
<comment>Description:</comment>
  Erases a specified portion of the internal LOB data
  
  Erases a specified portion of the internal LOB data starting at a specified <strong>$offset</strong>. If called
  without parameters, it erases all LOB data.
  
  For BLOBs, erasing means that the existing LOB value is overwritten with zero-bytes. For CLOBs,
  the existing LOB value is overwritten with spaces.

<comment>Param:</comment>
  <info>int</info>  <strong>$offset</strong>  
  <info>int</info>  <strong>$length</strong>  

<comment>Return:</comment>
  <info>intfalse</info>  Returns the actual number of characters/bytes erased  sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * 


id: OCILob::export
type: function
doc:
<comment>Description:</comment>
  Exports LOB's contents to a file
  
  Exports LOB contents to a file.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  Path to the file.
  <info>int   </info>  <strong>$start   </strong>  Indicates from where to start exporting.
  <info>int   </info>  <strong>$length  </strong>  Indicates the length of data to be exported.

<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>
   * 


id: OCILob::free
type: function
doc:
<comment>Description:</comment>
  Frees resources associated with the LOB descriptor
  
  Frees resources associated with the descriptor, previously allocated with  <strong>oci_new_descriptor()</strong>.

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


id: OCILob::getBuffering
type: function
doc:
<comment>Description:</comment>
  Returns current state of buffering for the large object
  
  Tells whether the buffering for the large object is on or off.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>false</info> if buffering for the large object is off and <info>true</info> if buffering is used.

<comment>See Also:</comment>
   * 


id: OCILob::import
type: function
doc:
<comment>Description:</comment>
  Imports file data to the LOB
  
  Writes data from the <strong>$filename</strong> in to the current position of large object.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  Path to the file.

<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>
   * 
   * 


id: OCILob::load
type: function
doc:
<comment>Description:</comment>
  Returns large object's contents
  
  Returns large object's contents. As script execution is terminated when the memory_limit is
  reached, ensure that the LOB does not exceed this limit. In most cases it's recommended to use
  instead.

<comment>Return:</comment>
  <info>string</info>  Returns the contents of the object, or <info>false</info> on errors.

<comment>See Also:</comment>
   * 


id: OCILob::read
type: function
doc:
<comment>Description:</comment>
  Reads part of the large object
  
  Reads <strong>$length</strong> bytes from the current position of LOB's internal pointer.
  
  Reading stops when <strong>$length</strong> bytes have been read or end of the large object is reached. Internal
  pointer of the large object will be shifted on the amount of bytes read.

<comment>Param:</comment>
  <info>int</info>  <strong>$length</strong>  The length of data to read, in bytes.  Large values will be rounded down to 1 MB.

<comment>Return:</comment>
  <info>stringfalse</info>  Returns the contents as a string,  sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * 
   * 


id: OCILob::rewind
type: function
doc:
<comment>Description:</comment>
  Moves the internal pointer to the beginning of the large object
  
  Sets the internal pointer to the beginning of the large object.

<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>
   * 
   * 


id: OCILob::save
type: function
doc:
<comment>Description:</comment>
  Saves data to the large object
  
  Saves <strong>$data</strong> to the large object.

<comment>Param:</comment>
  <info>string</info>  <strong>$data  </strong>  The data to be saved.
  <info>int   </info>  <strong>$offset</strong>  Can be used to indicate offset from the beginning of the large object.

<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>
   * 
   * 


id: OCILob::seek
type: function
doc:
<comment>Description:</comment>
  Sets the internal pointer of the large object
  
  Sets the internal pointer of the large object.

<comment>Param:</comment>
  <info>int</info>  <strong>$offset</strong>  Indicates the amount of bytes, on which internal pointer should be moved from the
                position, pointed by <strong>$whence</strong>.
  <info>int</info>  <strong>$whence</strong>  May be one of: <info>OCI_SEEK_SET</info> - sets the position equal to  <strong>$offset</strong> <info>OCI_SEEK_CUR</info> -
                adds <strong>$offset</strong>  bytes to the current position   <info>OCI_SEEK_END</info> - adds <strong>$offset</strong> bytes to
                the end of large object (use negative value to move to a position before the end of
                large object)

<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>
   * 
   * 
   * 


id: OCILob::setBuffering
type: function
doc:
<comment>Description:</comment>
  Changes current state of buffering for the large object
  
  Sets the buffering for the large object, depending on the value of the <strong>$on_off</strong> parameter.
  
  Use of this function may provide performance improvements by buffering small reads and writes of
  LOBs by reducing the number of network round-trips and LOB versions.  <strong>OCILob::flush()</strong> should be
  used to flush buffers, when you have finished working with the large object.

<comment>Param:</comment>
  <info>bool</info>  <strong>$on_off</strong>  <info>true</info> for on and <info>false</info> for off.

<comment>Return:</comment>
  <info>bool</info>  Întoarce valoarea <info>true</info> în cazul
        succesului sau <info>false</info> în cazul eșecului. Repeated calls to this method with the same flag
        will return <info>true</info>.

<comment>See Also:</comment>
   * 


id: OCILob::size
type: function
doc:
<comment>Description:</comment>
  Returns size of large object
  
  Gets the size of the large object.

<comment>Return:</comment>
  <info>intfalse</info>  Returns length of large object value  sau <info>false</info> în cazul eșecului. Empty objects have
            zero length.


id: OCILob::tell
type: function
doc:
<comment>Description:</comment>
  Returns the current position of internal pointer of large object
  
  Gets the current position of a LOB's internal pointer.

<comment>Return:</comment>
  <info>int</info>  Returns current position of a LOB's internal pointer or <info>false</info> if an error occurred.

<comment>See Also:</comment>
   * 
   * 
   * 


id: OCILob::truncate
type: function
doc:
<comment>Description:</comment>
  Truncates large object
  
  Truncates the LOB.

<comment>Param:</comment>
  <info>int</info>  <strong>$length</strong>  If provided, this method will truncate the LOB to <strong>$length</strong> bytes. Otherwise, it will
                completely purge the LOB.

<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>
   * 


id: OCILob::write
type: function
doc:
<comment>Description:</comment>
  Writes data to the large object
  
  Writes data from the parameter <strong>$data</strong> into the current position of LOB's internal pointer.

<comment>Param:</comment>
  <info>string</info>  <strong>$data  </strong>  The data to write in the LOB.
  <info>int   </info>  <strong>$length</strong>  If this parameter is given, writing will stop after  <strong>$length</strong> bytes have been
                   written or the end of <strong>$data</strong> is reached, whichever comes first.

<comment>Return:</comment>
  <info>intfalse</info>  Returns the number of bytes written  sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * 


id: OCI_ASSOC
type: constant
doc:
<comment>Description:</comment>
  Folosit cu funcția <strong>oci_fetch_all()</strong> și <strong>oci_fetch_array()</strong> pentru preluarea de rezultate sub forma
  unui array asociativ.


id: OCI_BOTH
type: constant
doc:
<comment>Description:</comment>
  Folosit cu funcția <strong>oci_fetch_all()</strong> și <strong>oci_fetch_array()</strong> pentru preluarea rezultatelor sub forma
  unui array cu indecși atât asociativi cât și numerici.


id: OCI_B_BFILE
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea cu obiecte BFILE.


id: OCI_B_BIN
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea cu valori RAW.


id: OCI_B_BLOB
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea de obiecte BLOB.


id: OCI_B_BOL
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> pentru a mapa o variabilă PL/SQL BOOLEAN.


id: OCI_B_CFILEE
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea cu obiecte CFILE.


id: OCI_B_CLOB
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea cu obiecte CLOB.


id: OCI_B_CURSOR
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea cursorilor, construiți în prealabil cu
  <strong>oci_new_descriptor()</strong>.


id: OCI_B_INT
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_array_by_name()</strong> la maparea array-urilor de tip INTEGER.


id: OCI_B_NTY
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea tipurilor de date numite. Notă: în PHP
  \< 5.0 se numea <info>OCI_B_SQLT_NTY</info>.


id: OCI_B_NUM
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_array_by_name()</strong> la maparea array-urilor de tip NUMBER.


id: OCI_B_ROWID
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_bind_by_name()</strong> la maparea ROWID.


id: OCI_COMMIT_ON_SUCCESS
type: constant
doc:
<comment>Description:</comment>
  Modul de execuție a statementului Oracle pentru apelul la <strong>oci_execute()</strong>. Modificările vor fi
  salvate automat dacă statementul a fost executat cu succes.


id: OCI_CRED_EXT
type: constant
doc:
<comment>Description:</comment>
  Folosit cu funcția <strong>oci_connect()</strong> pentru a folosi metoda de autentificare externă Oracle sau a
  sistemului de operare. Introdusă în PHP 5.3 și PECL OCI8 1.3.4.


id: OCI_DESCRIBE_ONLY
type: constant
doc:
<comment>Description:</comment>
  Modul de execuție a statementului Oracle pentru apelul la <strong>oci_execute()</strong>. Acest mod poate fi
  folosit dacă se dorește preluarea de meta date, cum ar fi numele coloanelor, dar nu se dorește
  preluarea efectivă de rânduri din rezultat.


id: OCI_DTYPE_FILE
type: constant
doc:
<comment>Description:</comment>
  Această opțiune semnalizează funcției <strong>oci_new_descriptor()</strong> să inițializeze un descriptor nou de
  tip FILE.


id: OCI_DTYPE_LOB
type: constant
doc:
<comment>Description:</comment>
  Această opțiune semnalizează funcției <strong>oci_new_descriptor()</strong> să inițializeze un descriptor nou de
  tip LOB..


id: OCI_DTYPE_ROWID
type: constant
doc:
<comment>Description:</comment>
  Această opțiune semnalizează funcției <strong>oci_new_descriptor()</strong> să inițializeze un descriptor nou de
  tip ROWID.


id: OCI_EXACT_FETCH
type: constant
doc:
<comment>Description:</comment>
  Învechită. Modul de execuție a statementului Oracle. Folosit când aplicația știe câte rânduri va
  prelua. Acest mod oprește preluarea automată de rânduri pentru Oracle versiunea 8 sau mai nouă.
  Setul de rezultate este distrus după ce rândurile specificate sunt preluate rezultând în
  micșorarea resurselor folosite pe server.


id: OCI_FETCHSTATEMENT_BY_ROW
type: constant
doc:
<comment>Description:</comment>
  Modul alternativ pentru funcția <strong>oci_fetch_all()</strong>.


id: OCI_NO_AUTO_COMMIT
type: constant
doc:
<comment>Description:</comment>
  Modul de execuție a statementului Oracle pentru apelul la <strong>oci_execute()</strong>. Tranzacția nu este
  executată automat când se folosește acest mod. Pentru claritate în cod nou, folosiți această
  constantă în loc de constanta învechită echivalentă <info>OCI_DEFAULT</info>. Introdusă în PHP 5.3.2 (PECL OCI8
  1.4).


id: OCI_NUM
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_fetch_all()</strong> și <strong>oci_fetch_array()</strong> pentru preluarea rezultatului ca un array
  indexat numeric.


id: OCI_RETURN_LOBS
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_fetch_array()</strong> pentru preluarea datelor din LOB în locul descriptorului.


id: OCI_RETURN_NULLS
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_fetch_array()</strong> pentru a fi întoarse elemente goale în array atunci când
  valoarea din baza de date este <info>null</info>.


id: OCI_SYSDBA
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_connect()</strong> pentru conectarea cu privilegii SYSDBA. Opțiunea din php.ini
  oci8.privileged_connect trebuie activată pentru a se putea folosi această constantă.


id: OCI_SYSOPER
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția <strong>oci_connect()</strong> pentru a se conecta cu privilegii SYSOPER. Opțiunea din php.ini
  oci8.privileged_connect trebuie activată pentru a se putea folosi această constantă.


id: OCI_TEMP_BLOB
type: constant
doc:
<comment>Description:</comment>
  Folosită cu funcția  pentru a indica crearea unui obiect BLOB temporar.


id: OPENSSL_ALGO_MD2
type: constant
doc:
<comment>Description:</comment>
  As of PHP 5.2.13 and PHP 5.3.2, this constant is only available  if PHP is compiled with MD2
  support. This requires passing in the  -DHAVE_OPENSSL_MD2_H CFLAG when compiling PHP, and
  enable-md2 when  compiling OpenSSL 1.0.0+.


id: OPENSSL_ALGO_SHA1
type: constant
doc:
<comment>Description:</comment>
  Used as default algorithm by <strong>openssl_sign()</strong> and <strong>openssl_verify()</strong>.


id: OPENSSL_KEYTYPE_EC
type: constant
doc:
<comment>Description:</comment>
  This constant is only available when PHP is compiled with OpenSSL 0.9.8+. Added in PHP 5.2.0.


id: OPENSSL_ZERO_PADDING
type: constant
doc:
<comment>Description:</comment>
  By default encryption operations are padded using standard block padding and the padding is
  checked and removed when decrypting. If <info>OPENSSL_ZERO_PADDING</info> is set in the <strong>openssl_encrypt()</strong> or
  <strong>openssl_decrypt()</strong> <strong>$options</strong> then no padding is performed, the total amount of data encrypted or
  decrypted must then be a multiple of the block size or an error will occur.


id: OP_HALFOPEN
type: constant
doc:
<comment>Description:</comment>
  Pentru nume IMAP și NNTP deschide o conexiune, dar nu deschide o cutie poștală.


id: OpenSSLAsymmetricKey
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces <return>OpenSSL key</return> resources as of PHP 8.0.0.


id: OpenSSLCertificate
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces <return>OpenSSL X.509</return> resources as of PHP 8.0.0.


id: OpenSSLCertificateSigningRequest
type: class
doc:
<comment>Description:</comment>
  A fully opaque class which replaces <return>OpenSSL X.509 CSR</return> resources as of PHP 8.0.0.


id: OuterIterator
type: class
doc:
<comment>Description:</comment>
  Classes implementing <class>OuterIterator</class> can be used to iterate over iterators.


id: OuterIterator::getInnerIterator
type: function
doc:
<comment>Description:</comment>
  Returns the inner iterator for the current entry
  
  Returns the inner iterator for the current iterator entry.

<comment>Return:</comment>
  <info>Iterator</info>  The inner iterator for the current entry.


id: PASSWORD_ARGON2I
type: constant
doc:
<comment>Description:</comment>
  <info>PASSWORD_ARGON2I</info> is used to create new password hashes using the Argon2i algorithm.
  
  Supported Options:
  
  <return>memory_cost</return> (<info>int</info>) - Maximum memory (in bytes) that may  be used to compute the Argon2 hash.
  Defaults to <info>PASSWORD_ARGON2_DEFAULT_MEMORY_COST</info>.
  
  <return>time_cost</return> (<info>int</info>) - Maximum amount of time it may  take to compute the Argon2 hash. Defaults to
  <info>PASSWORD_ARGON2_DEFAULT_TIME_COST</info>.
  
  <return>threads</return> (<info>int</info>) - Number of threads to use for computing  the Argon2 hash. Defaults to
  <info>PASSWORD_ARGON2_DEFAULT_THREADS</info>.
  
  Available as of PHP 7.2.0.


id: PASSWORD_ARGON2ID
type: constant
doc:
<comment>Description:</comment>
  <info>PASSWORD_ARGON2ID</info> is used to create new password hashes using the Argon2id algorithm. It supports
  the same options as <info>PASSWORD_ARGON2I</info>.
  
  Available as of PHP 7.3.0.


id: PASSWORD_ARGON2_DEFAULT_MEMORY_COST
type: constant
doc:
<comment>Description:</comment>
  Default amount of memory in bytes that Argon2lib will use while trying to  compute a hash.
  
  Available as of PHP 7.2.0.


id: PASSWORD_ARGON2_DEFAULT_THREADS
type: constant
doc:
<comment>Description:</comment>
  Default number of threads that Argon2lib will use.
  
  Available as of PHP 7.2.0.


id: PASSWORD_ARGON2_DEFAULT_TIME_COST
type: constant
doc:
<comment>Description:</comment>
  Default amount of time that Argon2lib will spend trying to compute a hash.
  
  Available as of PHP 7.2.0.


id: PASSWORD_BCRYPT
type: constant
doc:
<comment>Description:</comment>
  <info>PASSWORD_BCRYPT</info> is used to create new password hashes using the <info>CRYPT_BLOWFISH</info> algorithm.
  
  This will always result in a hash using the "$2y$" crypt format,  which is always 60 characters
  wide.
  
  Supported Options:
  
  <return>salt</return> (<info>string</info>) - to manually provide a salt to use when hashing the password. Note that this will
  override and prevent a salt from being automatically generated.
  
  If omitted, a random salt will be generated by <strong>password_hash()</strong> for each password hashed. This is
  the intended mode of operation and as of PHP 7.0.0 the salt option has been deprecated.
  
  <return>cost</return> (<info>int</info>) - which denotes the algorithmic cost that  should be used. Examples of these values can
  be found on the <strong>crypt()</strong>  page.
  
  If omitted, a default value of <return>10</return> will be used. This is a good baseline cost, but you may want to
  consider increasing it depending on your hardware.


id: PASSWORD_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  The default algorithm to use for hashing if no algorithm is provided. This may change in newer PHP
  releases when newer, stronger hashing algorithms are supported.
  
  It is worth noting that over time this constant can (and likely will) change. Therefore you should
  be aware that the length of the resulting hash can change. Therefore, if you use <info>PASSWORD_DEFAULT</info>
  you should store the resulting hash in a way that can store more than 60 characters (255 is the
  recommended width).
  
  Values for this constant:
  
  PHP 5.5.0 - <info>PASSWORD_BCRYPT</info>


id: PCRE_VERSION
type: constant
doc:
<comment>Description:</comment>
  PCRE version and release date (e.g. "<return>7.0 18-Dec-2006</return>").
  
  5.2.4


id: PDO::ATTR_AUTOCOMMIT
type: constant
doc:
<comment>Description:</comment>
  If this value is <info>false</info>, PDO attempts to disable autocommit so that the connection begins a
  transaction.


id: PDO::ATTR_CASE
type: constant
doc:
<comment>Description:</comment>
  Force column names to a specific case specified by the <return>PDO::CASE_*</return> constants.


id: PDO::ATTR_CLIENT_VERSION
type: constant
doc:
<comment>Description:</comment>
  This is a read only attribute; it will return information about the version of the client
  libraries that the PDO driver is using.


id: PDO::ATTR_CURSOR
type: constant
doc:
<comment>Description:</comment>
  Selects the cursor type.  PDO currently supports either <info>PDO::CURSOR_FWDONLY</info> and
  <info>PDO::CURSOR_SCROLL</info>. Stick with <info>PDO::CURSOR_FWDONLY</info> unless you know that you need a scrollable
  cursor.


id: PDO::ATTR_CURSOR_NAME
type: constant
doc:
<comment>Description:</comment>
  Get or set the name to use for a cursor.  Most useful when using scrollable cursors and positioned
  updates.


id: PDO::ATTR_DEFAULT_STR_PARAM
type: constant
doc:
<comment>Description:</comment>
  Sets the default string parameter type, this can be one of <info>PDO::PARAM_STR_NATL</info>  and
  <info>PDO::PARAM_STR_CHAR</info>.
  
  Available since PHP 7.2.0.


id: PDO::ATTR_DRIVER_NAME
type: constant
doc:
<comment>Description:</comment>
  Returns the name of the driver.
  
  using <info>PDO::ATTR_DRIVER_NAME</info>getAttribute(PDO::ATTR_DRIVER_NAME) == 'mysql') { echo "Running on
  mysql; doing something mysql specific here\n";
  }
  ?>
  ]]>


id: PDO::ATTR_ERRMODE
type: constant
doc:
<comment>Description:</comment>
  See the Errors and error handling section for more information about this attribute.


id: PDO::ATTR_FETCH_CATALOG_NAMES
type: constant
doc:
<comment>Description:</comment>
  Prepend the containing catalog name to each column name returned in the result set. The catalog
  name and column name are separated by a decimal (.) character.  Support of this attribute is at
  the driver level; it may not be supported by your driver.


id: PDO::ATTR_FETCH_TABLE_NAMES
type: constant
doc:
<comment>Description:</comment>
  Prepend the containing table name to each column name returned in the result set. The table name
  and column name are separated by a decimal (.) character. Support of this attribute is at the
  driver level; it may not be supported by your driver.


id: PDO::ATTR_PERSISTENT
type: constant
doc:
<comment>Description:</comment>
  Request a persistent connection, rather than creating a new connection. See Connections and
  Connection management for more information on this attribute.


id: PDO::ATTR_PREFETCH
type: constant
doc:
<comment>Description:</comment>
  Setting the prefetch size allows you to balance speed against memory usage for your application.
  Not all database/driver combinations support setting of the prefetch size.  A larger prefetch size
  results in increased performance at the cost of higher memory usage.


id: PDO::ATTR_SERVER_INFO
type: constant
doc:
<comment>Description:</comment>
  This is a read only attribute; it will return some meta information about the database server to
  which PDO is connected.


id: PDO::ATTR_SERVER_VERSION
type: constant
doc:
<comment>Description:</comment>
  This is a read only attribute; it will return information about the version of the database server
  to which PDO is connected.


id: PDO::ATTR_TIMEOUT
type: constant
doc:
<comment>Description:</comment>
  Sets the timeout value in seconds for communications with the database.


id: PDO::CURSOR_FWDONLY
type: constant
doc:
<comment>Description:</comment>
  Create a <class>PDOStatement</class> object with a forward-only cursor.  This is the default cursor choice, as it
  is the fastest and most common data access pattern in PHP.


id: PDO::CURSOR_SCROLL
type: constant
doc:
<comment>Description:</comment>
  Create a <class>PDOStatement</class> object with a scrollable cursor. Pass the <return>PDO::FETCH_ORI_*</return> constants to
  control the rows fetched from the result set.


id: PDO::ERRMODE_EXCEPTION
type: constant
doc:
<comment>Description:</comment>
  Throw a <class>PDOException</class> if an error occurs. See Errors and error handling for more information about
  this attribute.


id: PDO::ERRMODE_SILENT
type: constant
doc:
<comment>Description:</comment>
  Do not raise an error or exception if an error occurs. The developer is expected to explicitly
  check for errors.  This is the default mode. See Errors and error handling for more information
  about this attribute.


id: PDO::ERRMODE_WARNING
type: constant
doc:
<comment>Description:</comment>
  Issue a PHP <info>E_WARNING</info> message if an error occurs. See Errors and error handling for more
  information about this attribute.


id: PDO::ERR_NONE
type: constant
doc:
<comment>Description:</comment>
  Corresponds to SQLSTATE '00000', meaning that the SQL statement was successfully issued with no
  errors or warnings.  This constant is for your convenience when checking <strong>PDO::errorCode()</strong> or
  <strong>PDOStatement::errorCode()</strong> to determine if an error occurred.  You will usually know if this is the
  case by examining the return code from the method that raised the error condition anyway.


id: PDO::FETCH_ASSOC
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return each row as an array indexed by column name as
  returned in the corresponding result set. If the result set contains multiple columns with the
  same name, <info>PDO::FETCH_ASSOC</info> returns only a single value per column name.


id: PDO::FETCH_BOTH
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return each row as an array indexed by both column name and
  number as returned in the corresponding result set, starting at column 0.


id: PDO::FETCH_BOUND
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return TRUE and assign the values of the columns in the
  result set to the PHP variables to which they were bound with the <strong>PDOStatement::bindParam()</strong> or
  <strong>PDOStatement::bindColumn()</strong> methods.


id: PDO::FETCH_CLASS
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return a new instance of the requested class, mapping the
  columns to named properties in the class.
  
  The magic __set method is called if the property doesn't exist in the requested class


id: PDO::FETCH_COLUMN
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return only a single requested column from the next row in
  the result set.


id: PDO::FETCH_FUNC
type: constant
doc:
<comment>Description:</comment>
  Allows completely customize the way data is treated on the fly (only  valid inside
  <strong>PDOStatement::fetchAll()</strong>).


id: PDO::FETCH_GROUP
type: constant
doc:
<comment>Description:</comment>
  Group return by values. Usually combined with <info>PDO::FETCH_COLUMN</info> or  <info>PDO::FETCH_KEY_PAIR</info>.


id: PDO::FETCH_INTO
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall update an existing instance of the requested class, mapping
  the columns to named properties in the class.


id: PDO::FETCH_KEY_PAIR
type: constant
doc:
<comment>Description:</comment>
  Fetch a two-column result into an array where the first column is a key and the second column is
  the value. Available since PHP 5.2.3.


id: PDO::FETCH_LAZY
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return each row as an object with variable names that
  correspond to the column names returned in the result set. <info>PDO::FETCH_LAZY</info> creates the object
  variable names as they are accessed. Not valid inside <strong>PDOStatement::fetchAll()</strong>.


id: PDO::FETCH_NAMED
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return each row as an array indexed by column name as
  returned in the corresponding result set. If the result set contains multiple columns with the
  same name, <info>PDO::FETCH_NAMED</info> returns an array of values per column name.


id: PDO::FETCH_NUM
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return each row as an array indexed by column number as
  returned in the corresponding result set, starting at column 0.


id: PDO::FETCH_OBJ
type: constant
doc:
<comment>Description:</comment>
  Specifies that the fetch method shall return each row as an object with property names that
  correspond to the column names returned in the result set.


id: PDO::FETCH_ORI_ABS
type: constant
doc:
<comment>Description:</comment>
  Fetch the requested row by row number from the result set. Valid only for scrollable cursors.


id: PDO::FETCH_ORI_FIRST
type: constant
doc:
<comment>Description:</comment>
  Fetch the first row in the result set. Valid only for scrollable cursors.


id: PDO::FETCH_ORI_LAST
type: constant
doc:
<comment>Description:</comment>
  Fetch the last row in the result set. Valid only for scrollable cursors.


id: PDO::FETCH_ORI_NEXT
type: constant
doc:
<comment>Description:</comment>
  Fetch the next row in the result set. Valid only for scrollable cursors.


id: PDO::FETCH_ORI_PRIOR
type: constant
doc:
<comment>Description:</comment>
  Fetch the previous row in the result set. Valid only for scrollable cursors.


id: PDO::FETCH_ORI_REL
type: constant
doc:
<comment>Description:</comment>
  Fetch the requested row by relative position from the current position of the cursor in the result
  set. Valid only for scrollable cursors.


id: PDO::FETCH_PROPS_LATE
type: constant
doc:
<comment>Description:</comment>
  Call the constructor before setting properties. Available since PHP 5.2.0.


id: PDO::FETCH_SERIALIZE
type: constant
doc:
<comment>Description:</comment>
  As <info>PDO::FETCH_INTO</info> but object is provided as a serialized string. Available since PHP 5.1.0. Since
  PHP 5.3.0 the class constructor is never called if this flag is set.


id: PDO::MYSQL_ATTR_COMPRESS
type: constant
doc:
<comment>Description:</comment>
  Enable network communication compression. This is also supported when  compiled against mysqlnd as
  of PHP 5.3.11.


id: PDO::MYSQL_ATTR_FOUND_ROWS
type: constant
doc:
<comment>Description:</comment>
  Return the number of found (matched) rows, not the  number of changed rows.


id: PDO::MYSQL_ATTR_IGNORE_SPACE
type: constant
doc:
<comment>Description:</comment>
  Permit spaces after function names. Makes all functions  names reserved words.


id: PDO::MYSQL_ATTR_INIT_COMMAND
type: constant
doc:
<comment>Description:</comment>
  Command to execute when connecting to the MySQL server. Will automatically be re-executed when
  reconnecting.
  
  Note, this constant can only be used in the <strong>$driver_options</strong>  array when constructing a new
  database handle.


id: PDO::MYSQL_ATTR_LOCAL_INFILE
type: constant
doc:
<comment>Description:</comment>
  Enable <return>LOAD LOCAL INFILE</return>.
  
  Note, this constant can only be used in the <strong>$driver_options</strong>  array when constructing a new
  database handle.


id: PDO::MYSQL_ATTR_LOCAL_INFILE_DIRECTORY
type: constant
doc:
<comment>Description:</comment>
  Allows restricting LOCAL DATA loading to files located in this designated  directory.
  
  Note, this constant can only be used in the <strong>$driver_options</strong>  array when constructing a new
  database handle.


id: PDO::MYSQL_ATTR_MAX_BUFFER_SIZE
type: constant
doc:
<comment>Description:</comment>
  Maximum buffer size. Defaults to 1 MiB. This constant is not supported when  compiled against
  mysqlnd.


id: PDO::MYSQL_ATTR_MULTI_STATEMENTS
type: constant
doc:
<comment>Description:</comment>
  Disables multi query execution in both <strong>PDO::prepare()</strong> and <strong>PDO::query()</strong> when set to <info>false</info>.
  
  Note, this constant can only be used in the <strong>$driver_options</strong>  array when constructing a new
  database handle.
  
  Aceasta există începând cu PHP  5.5.21 and PHP 5.6.5.


id: PDO::MYSQL_ATTR_READ_DEFAULT_FILE
type: constant
doc:
<comment>Description:</comment>
  Read options from the named option file instead of from my.cnf. This option is not available if
  mysqlnd is used, because mysqlnd does not read the mysql  configuration files.


id: PDO::MYSQL_ATTR_READ_DEFAULT_GROUP
type: constant
doc:
<comment>Description:</comment>
  Read options from the named group from my.cnf or the file specified with <info>MYSQL_READ_DEFAULT_FILE</info>.
  This option  is not available if mysqlnd is used, because mysqlnd does not read the mysql
  configuration files.


id: PDO::MYSQL_ATTR_SSL_CA
type: constant
doc:
<comment>Description:</comment>
  The file path to the SSL certificate authority.
  
  Aceasta există începând cu PHP  5.3.7.


id: PDO::MYSQL_ATTR_SSL_CAPATH
type: constant
doc:
<comment>Description:</comment>
  The file path to the directory that contains the trusted SSL CA certificates, which are stored in
  PEM format.
  
  Aceasta există începând cu PHP  5.3.7.


id: PDO::MYSQL_ATTR_SSL_CERT
type: constant
doc:
<comment>Description:</comment>
  The file path to the SSL certificate.
  
  Aceasta există începând cu PHP  5.3.7.


id: PDO::MYSQL_ATTR_SSL_CIPHER
type: constant
doc:
<comment>Description:</comment>
  A list of one or more permissible ciphers to use for SSL encryption, in a format understood by
  OpenSSL. For example: <return>DHE-RSA-AES256-SHA:AES128-SHA</return>
  
  Aceasta există începând cu PHP  5.3.7.


id: PDO::MYSQL_ATTR_SSL_KEY
type: constant
doc:
<comment>Description:</comment>
  The file path to the SSL key.
  
  Aceasta există începând cu PHP  5.3.7.


id: PDO::MYSQL_ATTR_SSL_VERIFY_SERVER_CERT
type: constant
doc:
<comment>Description:</comment>
  Provides a way to disable verification of the server SSL certificate.
  
  Aceasta există începând cu PHP  7.0.18 and PHP 7.1.4.


id: PDO::MYSQL_ATTR_USE_BUFFERED_QUERY
type: constant
doc:
<comment>Description:</comment>
  If this attribute is set to <info>true</info> on a <class>PDOStatement</class>, the MySQL driver will use the buffered
  versions of the MySQL API.  If you're writing portable code, you should use
  <strong>PDOStatement::fetchAll()</strong> instead.
  
  Forcing queries to be buffered in mysqlgetAttribute(PDO::ATTR_DRIVER_NAME) == 'mysql') { $stmt =
  $db->prepare('select * from foo', array(PDO::MYSQL_ATTR_USE_BUFFERED_QUERY => true));
  } else { die("my application only works with mysql; I should use \$stmt->fetchAll() instead");
  }
  ?>
  ]]>


id: PDO::OCI_ATTR_ACTION
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the action on the database session.
  
  Aceasta există începând cu PHP  7.2.16 and 7.3.3


id: PDO::OCI_ATTR_CLIENT_IDENTIFIER
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the client identifier on the database session.
  
  Aceasta există începând cu PHP  7.2.16 and 7.3.3


id: PDO::OCI_ATTR_CLIENT_INFO
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the client info on the database session.
  
  Aceasta există începând cu PHP  7.2.16 and 7.3.3


id: PDO::OCI_ATTR_MODULE
type: constant
doc:
<comment>Description:</comment>
  Provides a way to specify the module on the database session.
  
  Aceasta există începând cu PHP  7.2.16 and 7.3.3


id: PDO::ODBC_ATTR_ASSUME_UTF8
type: constant
doc:
<comment>Description:</comment>
  Windows only. If <info>true</info>, UTF-16 encoded character data (<return>CHAR</return>, <return>VARCHAR</return> and <return>LONGVARCHAR</return>) is converted
  to UTF-8 when reading from or writing data to the database. If <info>false</info> (the default), no character
  encoding conversion is done.


id: PDO::ODBC_ATTR_USE_CURSOR_LIBRARY
type: constant
doc:
<comment>Description:</comment>
  This option controls whether the ODBC cursor library is used. The ODBC cursor library supports
  some advanced ODBC features (e.g. block scrollable cursors), which may not be implemented by the
  driver. The following values are supported: <info>PDO::ODBC_SQL_USE_IF_NEEDED</info> (the default): use the
  ODBC cursor library when needed. <info>PDO::ODBC_SQL_USE_DRIVER</info>: never use the ODBC cursor library.
  <info>PDO::ODBC_SQL_USE_ODBC</info>: always use the ODBC cursor library.
  
  <info>PDO::ODBC_SQL_USE_IF_NEEDED</info> (the default): use the ODBC cursor library when needed.
  
  <info>PDO::ODBC_SQL_USE_DRIVER</info>: never use the ODBC cursor library.
  
  <info>PDO::ODBC_SQL_USE_ODBC</info>: always use the ODBC cursor library.


id: PDO::PARAM_EVT_FETCH_POST
type: constant
doc:
<comment>Description:</comment>
  Event triggered subsequent to fetching a result from a resultset.


id: PDO::PARAM_EVT_NORMALIZE
type: constant
doc:
<comment>Description:</comment>
  Event triggered during bound parameter registration allowing the driver to normalize the parameter
  name.


id: PDO::PARAM_INPUT_OUTPUT
type: constant
doc:
<comment>Description:</comment>
  Specifies that the parameter is an INOUT parameter for a stored procedure. You must bitwise-OR
  this value with an explicit PDO::PARAM_* data type.


id: PDO::PARAM_STMT
type: constant
doc:
<comment>Description:</comment>
  Represents a recordset type.  Not currently supported by any drivers.


id: PDO::PARAM_STR_CHAR
type: constant
doc:
<comment>Description:</comment>
  Flag to denote a string uses the regular character set.
  
  Available since PHP 7.2.0


id: PDO::PARAM_STR_NATL
type: constant
doc:
<comment>Description:</comment>
  Flag to denote a string uses the national character set.
  
  Available since PHP 7.2.0


id: PDO::SQLITE_DETERMINISTIC
type: constant
doc:
<comment>Description:</comment>
  Specifies that a function created with <strong>PDO::sqliteCreateFunction()</strong> is deterministic, i.e. it
  always returns the same result given the same inputs within a single SQL statement. (Available as
  of PHP 7.1.4.)


id: PDO::SQLSRV_ATTR_DIRECT_QUERY
type: constant
doc:
<comment>Description:</comment>
  Indicates that a query should be executed directly, without being prepared.  This constant can be
  passed to PDO::setAttribute, and PDO::prepare. For more  information, see  Direct and Prepared
  Statement Execution.


id: PDO::SQLSRV_ATTR_QUERY_TIMEOUT
type: constant
doc:
<comment>Description:</comment>
  A non-negative integer representing the timeout period, in seconds. Zero (0)  is the default and
  means no timeout. This constant can be passed to  PDOStatement::setAttribute, PDO::setAttribute,
  and PDO::prepare.


id: PDO::SQLSRV_ENCODING_BINARY
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved as a raw byte stream to/from the server  without performing
  encoding or translation. This constant can be passed to  PDOStatement::setAttribute, PDO::prepare,
  PDOStatement::bindColumn, and  PDOStatement::bindParam.


id: PDO::SQLSRV_ENCODING_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved to/from the server according to  PDO::SQLSRV_ENCODING_SYSTEM
  if specified during connection. The connection's  encoding is used if specified in a prepare
  statement. This constant can be  passed to PDOStatement::setAttribute, PDO::setAttribute,
  PDO::prepare,  PDOStatement::bindColumn, and PDOStatement::bindParam.


id: PDO::SQLSRV_ENCODING_SYSTEM
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved to/from the server as 8-bit characters  as specified in the
  code page of the Windows locale that is set on the system.  Any multi-byte characters or
  characters that do not map into this code page  are substituted with a single byte question mark
  (?) character. This constant  can be passed to PDOStatement::setAttribute, PDO::setAttribute,
  PDO::prepare,  PDOStatement::bindColumn, and PDOStatement::bindParam.


id: PDO::SQLSRV_ENCODING_UTF8
type: constant
doc:
<comment>Description:</comment>
  Specifies that data is sent/retrieved to/from the server in UTF-8 encoding.  This is the default
  encoding. This constant can be passed to  PDOStatement::setAttribute, PDO::setAttribute,
  PDO::prepare,  PDOStatement::bindColumn, and PDOStatement::bindParam.


id: PDO::SQLSRV_TXN_READ_COMMITTED
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Read Committed.


id: PDO::SQLSRV_TXN_READ_UNCOMMITTED
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Read Uncommitted.


id: PDO::SQLSRV_TXN_REPEATABLE_READ
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Repeateable Read.


id: PDO::SQLSRV_TXN_SERIALIZABLE
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to  Serializable.


id: PDO::SQLSRV_TXN_SNAPSHOT
type: constant
doc:
<comment>Description:</comment>
  This constant is an acceptable value for the SQLSRV DSN key TransactionIsolation.  This constant
  sets the transaction isolation level for the connection to Snapshot.


id: PDO::__construct
type: function
doc:
<comment>Description:</comment>
  Creates a PDO instance representing a connection to a database
    
  
  Creates a PDO instance to represent a connection to the requested database.

<comment>Param:</comment>
  <info>string</info>  <strong>$dsn</strong>  The Data Source Name, or DSN, contains the information required to connect to the
                database.
                
                In general, a DSN consists of the PDO driver name, followed by a colon, followed by
                the PDO driver-specific connection syntax. Further information is available from the
                PDO driver-specific documentation.
                
                The <strong>$dsn</strong> parameter supports three different methods of specifying the arguments
                required to create a database connection:
                
                Driver invocation<strong>$dsn</strong> contains the full DSN. URI invocation<strong>$dsn</strong> consists of uri:
                followed by a URI that defines the location of a file containing the DSN string. The
                URI can specify a local file or a remote URL.
                uri:file:///path/to/dsnfileAliasing<strong>$dsn</strong> consists of a name  <strong>$name</strong> that maps to
                pdo.dsn.<strong>$name</strong> in php.ini defining the DSN string.  The alias must be defined in
                php.ini, and not .htaccess or httpd.conf
                
                <strong>$dsn</strong> contains the full DSN.
                
                <strong>$dsn</strong> consists of uri: followed by a URI that defines the location of a file
                containing the DSN string. The URI can specify a local file or a remote URL.
                
                uri:file:///path/to/dsnfile
                
                <strong>$dsn</strong> consists of a name  <strong>$name</strong> that maps to  pdo.dsn.<strong>$name</strong> in php.ini defining the
                DSN string.
                
                The alias must be defined in php.ini, and not .htaccess or httpd.conf
  <info>string</info>  <strong>$dsn</strong>  <strong>$dsn</strong> contains the full DSN.
  <info>string</info>  <strong>$dsn</strong>  <strong>$dsn</strong> consists of uri: followed by a URI that defines the location of a file
                containing the DSN string. The URI can specify a local file or a remote URL.
                
                uri:file:///path/to/dsnfile
  <info>string</info>  <strong>$dsn</strong>  <strong>$dsn</strong> consists of a name  <strong>$name</strong> that maps to  pdo.dsn.<strong>$name</strong> in php.ini defining the
                DSN string.
                
                The alias must be defined in php.ini, and not .htaccess or httpd.conf

<comment>Return:</comment>
  <info>unknown</info>  Returns a PDO object on success.


id: PDO::beginTransaction
type: function
doc:
<comment>Description:</comment>
  Initiates a transaction
    
  
  Turns off autocommit mode.  While autocommit mode is turned off, changes made to the database via
  the PDO object instance are not committed until you end the transaction by calling <strong>PDO::commit()</strong>.
  Calling <strong>PDO::rollBack()</strong> will roll back all changes to the database and return the connection to
  autocommit mode.
  
  Some databases, including MySQL, automatically issue an implicit COMMIT when a database definition
  language (DDL) statement such as DROP TABLE or CREATE TABLE is issued within a transaction. The
  implicit COMMIT will prevent you from rolling back any other changes within the transaction
  boundary.

<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>PDO::commit()</strong>
   * <strong>PDO::rollBack()</strong>
   * Transactions and auto-commit


id: PDO::commit
type: function
doc:
<comment>Description:</comment>
  Commits a transaction
    
  
  Commits a transaction, returning the database connection to autocommit mode until the next call to
  <strong>PDO::beginTransaction()</strong> starts a new transaction.

<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>PDO::beginTransaction()</strong>
   * <strong>PDO::rollBack()</strong>
   * Transactions and auto-commit


id: PDO::cubrid_schema
type: function
doc:
<comment>Description:</comment>
  Get the requested schema information
  
  This function is used to get the requested schema information from database. You have to designate
  <strong>$table_name</strong>, if you want to get information on certain table, <strong>$col_name</strong>, if you want to get
  information on certain column (can be used only with PDO::CUBRID_SCH_COL_PRIVILEGE).
  
  The result of this 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
  NameValuePDO::CUBRID_SCH_TABLE1NAME2TYPE0:system table 1:view
  2:tablePDO::CUBRID_SCH_VIEW1NAME2TYPE1:viewPDO::CUBRID_SCH_QUERY_SPEC1QUERY_SPECPDO::CUBRID_SCH_ATTRIBUTE
  / PDO::CUBRID_SCH_TABLE_ATTRIBUTE1ATTR_NAME2DOMAIN3SCALE4PRECISION5INDEXED1:indexed6NOT NULL1:not
  null7SHARED1:shared8UNIQUE1:unique9DEFAULT10ATTR_ORDERbase:111CLASS_NAME12SOURCE_CLASS13IS_KEY1:keyPDO::CUBRID_SCH_METHOD
  /
  PDO::CUBRID_SCH_TABLE_METHOD1NAME2RET_DOMAIN3ARG_DOMAINPDO::CUBRID_SCH_METHOD_FILE1METHOD_FILEPDO::CUBRID_SCH_SUPER_TABLE
  / PDO::CUBRID_SCH_DIRECT_SUPER_TABLE / PDO::CUBRID_SCH_SUB_TABLE1CLASS_NAME2TYPE0:system table
  1:view 2:tablePDO::CUBRID_SCH_CONSTRAINT1TYPE0:unique 1:index 2:reverse unique 3:reverse
  index2NAME3ATTR_NAME4NUM_PAGES5NUM_KEYS6PRIMARY_KEY1:primary
  key7KEY_ORDERbase:1PDO::CUBRID_SCH_TRIGGER1NAME2STATUS3EVENT4TARGET_CLASS5TARGET_ATTR6ACTION_TIME7ACTION8PRIORITY9CONDITION_TIME10CONDITIONPDO::CUBRID_SCH_TABLE_PRIVILEGE
  / PDO::CUBRID_SCH_COL_PRIVILEGE1CLASS_NAME /
  ATTR_NAME2PRIVILEGE3GRANTABLEPDO::CUBRID_SCH_PRIMARY_KEY1CLASS_NAME2ATTR_NAME3KEY_SEQbase:14KEY_NAMEPDO::CUBRID_SCH_IMPORTED_KEYS
  / PDO::CUBRID_SCH_EXPORTED_KEYS /
  PDO::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>int   </info>  <strong>$schema_type</strong>  Schema type that you want to know.
  <info>string</info>  <strong>$table_name </strong>  Table you want to know the schema of.
  <info>string</info>  <strong>$col_name   </strong>  Column you want to know the schema of.

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


id: PDO::errorCode
type: function
doc:
<comment>Description:</comment>
  Fetch the SQLSTATE associated with the last operation on the database handle

<comment>Return:</comment>
  <info>string</info>  Returns an SQLSTATE, a five characters alphanumeric identifier defined in the ANSI SQL-92
          standard.  Briefly, an SQLSTATE consists of a two characters class value followed by a
          three characters subclass value. A class value of 01 indicates a warning and is
          accompanied by a return code of SQL_SUCCESS_WITH_INFO. Class values other than '01',
          except for the class 'IM', indicate an error.  The class 'IM' is specific to warnings and
          errors that derive from the implementation of PDO (or perhaps ODBC, if you're using the
          ODBC driver) itself.  The subclass value '000' in any class indicates that there is no
          subclass for that SQLSTATE.
          
          <strong>PDO::errorCode()</strong> only retrieves error codes for operations performed directly on the
          database handle. If you create a PDOStatement object through <strong>PDO::prepare()</strong> or
          <strong>PDO::query()</strong> and invoke an error on the statement handle, <strong>PDO::errorCode()</strong> will not
          reflect that error. You must call <strong>PDOStatement::errorCode()</strong> to return the error code for
          an operation performed on a particular statement handle.
          
          Returns <info>null</info> if no operation has been run on the database handle.

<comment>See Also:</comment>
   * <strong>PDO::errorInfo()</strong>
   * <strong>PDOStatement::errorCode()</strong>
   * <strong>PDOStatement::errorInfo()</strong>


id: PDO::errorInfo
type: function
doc:
<comment>Description:</comment>
  Fetch extended error information associated with the last operation on the database handle

<comment>Return:</comment>
  <info>array</info>  <strong>PDO::errorInfo()</strong> returns an array of error information about the last operation performed
         by this database handle. The array consists of at least the following fields:
         ElementInformation0SQLSTATE error code (a five characters alphanumeric identifier defined
         in the ANSI SQL standard).1Driver-specific error code.2Driver-specific error message.
         
         If the SQLSTATE error code is not set or there is no driver-specific error, the elements
         following element 0 will be set to <info>null</info>.
         
         <strong>PDO::errorInfo()</strong> only retrieves error information for operations performed directly on the
         database handle. If you create a PDOStatement object through <strong>PDO::prepare()</strong> or <strong>PDO::query()</strong>
         and invoke an error on the statement handle, <strong>PDO::errorInfo()</strong> will not reflect the error
         from the statement handle. You must call <strong>PDOStatement::errorInfo()</strong> to return the error
         information for an operation performed on a particular statement handle.

<comment>See Also:</comment>
   * <strong>PDO::errorCode()</strong>
   * <strong>PDOStatement::errorCode()</strong>
   * <strong>PDOStatement::errorInfo()</strong>


id: PDO::exec
type: function
doc:
<comment>Description:</comment>
  Execute an SQL statement and return the number of affected rows
    
  
  <strong>PDO::exec()</strong> executes an SQL statement in a single function call, returning the number of rows
  affected by the statement.
  
  <strong>PDO::exec()</strong> does not return results from a SELECT statement. For a SELECT statement that you only
  need to issue once during your program, consider issuing <strong>PDO::query()</strong>. For a statement that you
  need to issue multiple times, prepare  a PDOStatement object with <strong>PDO::prepare()</strong> and issue the
  statement with <strong>PDOStatement::execute()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$statement</strong>  The SQL statement to prepare and execute.
                      
                      Data inside the query should be properly escaped.

<comment>Return:</comment>
  <info>int</info>  <strong>PDO::exec()</strong> returns the number of rows that were modified or deleted by the SQL statement you
       issued. If no rows were affected,  <strong>PDO::exec()</strong> returns <return>0</return>.
       
       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.
       
       The following example incorrectly relies on the return value of <strong>PDO::exec()</strong>, wherein a
       statement that affected 0 rows results in a call to <strong>die()</strong>: exec() or
       die(print_r($db->errorInfo(), true)); // incorrect
       ?>
       ]]>

<comment>See Also:</comment>
   * <strong>PDO::prepare()</strong>
   * <strong>PDO::query()</strong>
   * <strong>PDOStatement::execute()</strong>


id: PDO::getAttribute
type: function
doc:
<comment>Description:</comment>
  Retrieve a database connection attribute
    
  
  This function returns the value of a database connection attribute. To retrieve PDOStatement
  attributes, refer to <strong>PDOStatement::getAttribute()</strong>.
  
  Note that some database/driver combinations may not support all of the database connection
  attributes.

<comment>Param:</comment>
  <info>int</info>  <strong>$attribute</strong>  One of the <return>PDO::ATTR_*</return> constants. The constants that apply to database
                   connections are as follows:
                   <return>PDO::ATTR_AUTOCOMMIT</return><return>PDO::ATTR_CASE</return><return>PDO::ATTR_CLIENT_VERSION</return><return>PDO::ATTR_CONNECTION_STATUS</return><return>PDO::ATTR_DRIVER_NAME</return><return>PDO::ATTR_ERRMODE</return><return>PDO::ATTR_ORACLE_NULLS</return><return>PDO::ATTR_PERSISTENT</return><return>PDO::ATTR_PREFETCH</return><return>PDO::ATTR_SERVER_INFO</return><return>PDO::ATTR_SERVER_VERSION</return><return>PDO::ATTR_TIMEOUT</return>

<comment>Return:</comment>
  <info>mixed</info>  A successful call returns the value of the requested PDO attribute. An unsuccessful call
         returns <return>null</return>.

<comment>See Also:</comment>
   * <strong>PDO::setAttribute()</strong>
   * <strong>PDOStatement::getAttribute()</strong>
   * <strong>PDOStatement::setAttribute()</strong>


id: PDO::getAvailableDrivers
type: function
doc:
<comment>Description:</comment>
  Return an array of available PDO drivers
    
  
  This function returns all currently available PDO drivers which can be used in <strong>$DSN</strong> parameter of
  <strong>PDO::__construct()</strong>.

<comment>Return:</comment>
  <info>array</info>  <strong>PDO::getAvailableDrivers()</strong> returns an array of PDO driver names. If no drivers are
         available, it returns an empty array.


id: PDO::inTransaction
type: function
doc:
<comment>Description:</comment>
  Checks if inside a transaction
    
  
  Checks if a transaction is currently active within the driver. This method only works for database
  drivers that support transactions.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if a transaction is currently active, and <info>false</info> if not.


id: PDO::lastInsertId
type: function
doc:
<comment>Description:</comment>
  Returns the ID of the last inserted row or sequence value
    
  
  Returns the ID of the last inserted row, or the last value from a sequence object, depending on
  the underlying driver. For example, PDO_PGSQL requires you to specify the name of a sequence
  object for the <strong>$name</strong> parameter.
  
  This method may not return a meaningful or consistent result across different PDO drivers, because
  the underlying database may not even support the notion of auto-increment fields or sequences.

<comment>Param:</comment>
  <info>string</info>  <strong>$name</strong>  Name of the sequence object from which the ID should be returned.

<comment>Return:</comment>
  <info>string</info>  If a sequence name was not specified for the <strong>$name</strong> parameter, <strong>PDO::lastInsertId()</strong> returns
          a string representing the row ID of the last row that was inserted into the database.
          
          If a sequence name was specified for the <strong>$name</strong> parameter, <strong>PDO::lastInsertId()</strong> returns a
          string representing the last value retrieved from the specified sequence object.
          
          If the PDO driver does not support this capability, <strong>PDO::lastInsertId()</strong> triggers an <return>IM001</return>
          SQLSTATE.


id: PDO::pgsqlCopyFromArray
type: function
doc:
<comment>Description:</comment>
  Copy data from PHP array into table
  
  Copies data from <strong>$rows</strong> array to table <strong>$table_name</strong> using <strong>$delimiter</strong> as fields delimiter and <strong>$fields</strong>
  list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>array </info>  <strong>$rows      </strong>  Array of strings with fields separated by <strong>$delimiter</strong>
  <info>string</info>  <strong>$delimiter </strong>  Delimiter used in <strong>$rows</strong> array
  <info>string</info>  <strong>$null_as   </strong>  How to interpret null values
  <info>string</info>  <strong>$fields    </strong>  List of fields to insert

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success, sau <info>false</info> în cazul eșecului.


id: PDO::pgsqlCopyFromFile
type: function
doc:
<comment>Description:</comment>
  Copy data from file into table
  
  Copies data from file specified by <strong>$filename</strong> into table <strong>$table_name</strong> using <strong>$delimiter</strong> as fields
  delimiter and <strong>$fields</strong> list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>string</info>  <strong>$filename  </strong>  Filename containing data to import
  <info>string</info>  <strong>$delimiter </strong>  Delimiter used in file specified by <strong>$filename</strong>
  <info>string</info>  <strong>$null_as   </strong>  How to interpret null values
  <info>string</info>  <strong>$fields    </strong>  List of fields to insert

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success, sau <info>false</info> în cazul eșecului.


id: PDO::pgsqlCopyToArray
type: function
doc:
<comment>Description:</comment>
  Copy data from database table into PHP array
  
  Copies data from <strong>$table</strong> into array using <strong>$delimiter</strong> as fields delimiter and <strong>$fields</strong> list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>string</info>  <strong>$delimiter </strong>  Delimiter used in rows
  <info>string</info>  <strong>$null_as   </strong>  How to interpret null values
  <info>string</info>  <strong>$fields    </strong>  List of fields to export

<comment>Return:</comment>
  <info>arrayfalse</info>  Returns an array of rows, sau <info>false</info> în cazul eșecului.


id: PDO::pgsqlCopyToFile
type: function
doc:
<comment>Description:</comment>
  Copy data from table into file
  
  Copies data from table into file specified by <strong>$filename</strong> using <strong>$delimiter</strong> as fields delimiter and
  <strong>$fields</strong> list

<comment>Param:</comment>
  <info>string</info>  <strong>$table_name</strong>  String containing table name
  <info>string</info>  <strong>$filename  </strong>  Filename to export data
  <info>string</info>  <strong>$delimiter </strong>  Delimiter used in file specified by <strong>$filename</strong>
  <info>string</info>  <strong>$null_as   </strong>  How to interpret null values
  <info>string</info>  <strong>$fields    </strong>  List of fields to insert

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> on success, sau <info>false</info> în cazul eșecului.


id: PDO::pgsqlGetNotify
type: function
doc:
<comment>Description:</comment>
  Get asynchronous notification
  
  Returns a result set representing a pending asynchronous notification.

<comment>Param:</comment>
  <info>int</info>  <strong>$result_type</strong>  The format the result set should be returned as, represented as a <info>PDO::FETCH_*</info>
                     constant.
  <info>int</info>  <strong>$ms_timeout </strong>  The length of time to wait for a response, in milliseconds.

<comment>Return:</comment>
  <info>array</info>  If one or more notifications is pending, returns a single row, with fields <return>message</return> and <return>pid</return>,
         otherwise returns <info>false</info>.


id: PDO::pgsqlGetPid
type: function
doc:
<comment>Description:</comment>
  Get the server PID
  
  Returns the server's PID.

<comment>Return:</comment>
  <info>int</info>  The server's PID.


id: PDO::pgsqlLOBCreate
type: function
doc:
<comment>Description:</comment>
  Creates a new large object
  
  <strong>PDO::pgsqlLOBCreate()</strong> creates a large object and returns the OID of that object.  You may then
  open a stream on the object using <strong>PDO::pgsqlLOBOpen()</strong> to read or write data to it.  The OID can be
  stored in columns of type OID and be used to reference the large object, without causing the row
  to grow arbitrarily large. The large object will continue to live in the database until it is
  removed by calling <strong>PDO::pgsqlLOBUnlink()</strong>.
  
  Large objects can be up to 2GB in size, but are cumbersome to use; you need to ensure that
  <strong>PDO::pgsqlLOBUnlink()</strong> is called prior to deleting the last row that references its OID from your
  database. In addition, large objects have no access controls.  As an alternative, try the bytea
  column type; recent versions of PostgreSQL allow bytea columns of up to 1GB in size and
  transparently manage the storage for optimal row size.
  
  This function must be called within a transaction.

<comment>Return:</comment>
  <info>string</info>  Returns the OID of the newly created large object on success, or <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>PDO::pgsqlLOBOpen()</strong>
   * <strong>PDO::pgsqlLOBUnlink()</strong>
   * <strong>pg_lo_create()</strong>


id: PDO::pgsqlLOBOpen
type: function
doc:
<comment>Description:</comment>
  Opens an existing large object stream
  
  <strong>PDO::pgsqlLOBOpen()</strong> opens a stream to access the data referenced by <strong>$oid</strong>.  If <strong>$mode</strong> is <return>r</return>, the
  stream is opened for reading, if <strong>$mode</strong> is <return>w</return>, then the stream will be opened for writing.  You can
  use all the usual filesystem functions, such as <strong>fread()</strong>, <strong>fwrite()</strong> and <strong>fgets()</strong> to manipulate the
  contents of the stream.
  
  This function, and all manipulations of the large object, must be called and carried out within a
  transaction.

<comment>Param:</comment>
  <info>string</info>  <strong>$oid </strong>  A large object identifier.
  <info>string</info>  <strong>$mode</strong>  If mode is <return>r</return>, open the stream for reading. If mode is <return>w</return>, open the stream for
                 writing.

<comment>Return:</comment>
  <info>resourcefalse</info>  Returns a stream resource on success sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>PDO::pgsqlLOBCreate()</strong>
   * <strong>PDO::pgsqlLOBUnlink()</strong>
   * <strong>pg_lo_open()</strong>


id: PDO::pgsqlLOBUnlink
type: function
doc:
<comment>Description:</comment>
  Deletes the large object
  
  Deletes a large object from the database identified by OID.
  
  This function must be called within a transaction.

<comment>Param:</comment>
  <info>string</info>  <strong>$oid</strong>  A large object identifier

<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>PDO::pgsqlLOBOpen()</strong>
   * <strong>PDO::pgsqlLOBCreate()</strong>


id: PDO::prepare
type: function
doc:
<comment>Description:</comment>
  Prepares a statement for execution and returns a statement object
    
  
  Prepares an SQL statement to be executed by the <strong>PDOStatement::execute()</strong> method. The statement
  template can contain zero or more named (:name) or question mark (?) parameter markers for which
  real values will be substituted when the statement is executed. Both named and question mark
  parameter markers cannot be used within the same statement template; only one or the other
  parameter style. Use these parameters to bind any user-input, do not include the user-input
  directly in the query.
  
  You must include a unique parameter marker for each value you wish to pass in to the statement
  when you call <strong>PDOStatement::execute()</strong>. You cannot use a named parameter marker of the same name
  more than once in a prepared statement, unless emulation mode is on.
  
  Parameter markers can represent a complete data literal only. Neither part of literal, nor
  keyword, nor identifier, nor whatever arbitrary query  part can be bound using parameters. For
  example, you cannot bind multiple values  to a single parameter in the IN() clause of an SQL
  statement.
  
  Calling <strong>PDO::prepare()</strong> and <strong>PDOStatement::execute()</strong> for statements that will be issued multiple
  times with different parameter values optimizes the performance of your application by allowing
  the driver to negotiate client and/or server side caching of the query plan and meta information.
  Also, calling <strong>PDO::prepare()</strong> and <strong>PDOStatement::execute()</strong> helps to prevent SQL injection attacks by
  eliminating the need to manually quote and escape the parameters.
  
  PDO will emulate prepared statements/bound parameters for drivers that do not natively support
  them, and can also rewrite named or question mark style parameter markers to something more
  appropriate, if the driver supports one style but not the other.
  
  As of PHP 5.3.0, the parser used for emulated prepared statements and for rewriting named or
  question mark style parameters supports the non standard backslash escapes for single- and double
  quotes. That means that terminating quotes immediately preceeded by a backslash are not recognized
  as such, which may result in wrong detection of parameters causing the prepared statement to fail
  when it is executed. A work-around is to not use emulated prepares for such SQL queries, and to
  avoid rewriting of parameters by using a parameter style which is natively supported by the
  driver.

<comment>Param:</comment>
  <info>string</info>  <strong>$statement     </strong>  This must be a valid SQL statement template for the target database
                           server.
  <info>array </info>  <strong>$driver_options</strong>  This array holds one or more key=&gt;value pairs to set attribute values
                           for the PDOStatement object that this method returns. You would most
                           commonly use this to set the <return>PDO::ATTR_CURSOR</return> value to <return>PDO::CURSOR_SCROLL</return>
                           to request a scrollable cursor. Some drivers have driver-specific options
                           that may be set at prepare-time.

<comment>Return:</comment>
  <info>PDOStatement</info>  If the database server successfully prepares the statement, <strong>PDO::prepare()</strong> returns a
                <class>PDOStatement</class> object. If the database server cannot successfully prepare the
                statement, <strong>PDO::prepare()</strong> returns <info>false</info> or emits <class>PDOException</class> (depending on error
                handling).
                
                Emulated prepared statements does not communicate with the database server so
                <strong>PDO::prepare()</strong> does not check the statement.

<comment>See Also:</comment>
   * <strong>PDO::exec()</strong>
   * <strong>PDO::query()</strong>
   * <strong>PDOStatement::execute()</strong>


id: PDO::query
type: function
doc:
<comment>Description:</comment>
  Executes an SQL statement, returning a result set as a PDOStatement object
    
  
  <strong>PDO::query()</strong> executes an SQL statement in a single function call, returning the result set (if
  any) returned by the statement as a PDOStatement object.
  
  For a query that you need to issue multiple times, you will realize better performance if you
  prepare a PDOStatement object using <strong>PDO::prepare()</strong> and issue the statement with multiple calls to
  <strong>PDOStatement::execute()</strong>.
  
  If you do not fetch all of the data in a result set before issuing your next call to <strong>PDO::query()</strong>,
  your call may fail. Call <strong>PDOStatement::closeCursor()</strong> to release the database resources associated
  with the PDOStatement object before issuing your next call to <strong>PDO::query()</strong>.
  
  If more than one argument is passed to this function, the remaining arguments will be treated as
  though you called <strong>PDOStatement::setFetchMode()</strong> on the resultant statement object.

<comment>Param:</comment>
  <info>string</info>  <strong>$statement</strong>  The SQL statement to prepare and execute.
                      
                      Data inside the query should be properly escaped.

<comment>Return:</comment>
  <info>PDOStatement</info>  <strong>PDO::query()</strong> returns a PDOStatement object, or <info>false</info> on failure.

<comment>See Also:</comment>
   * <strong>PDO::exec()</strong>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::execute()</strong>


id: PDO::quote
type: function
doc:
<comment>Description:</comment>
  Quotes a string for use in a query
    
  
  <strong>PDO::quote()</strong> places quotes around the input string (if required) and escapes special characters
  within the input string, using a quoting style appropriate to the underlying driver.
  
  If you are using this function to build SQL statements, you are strongly recommended to use
  <strong>PDO::prepare()</strong> to prepare SQL statements with bound parameters instead of using <strong>PDO::quote()</strong> to
  interpolate user input into an SQL statement.  Prepared statements with bound parameters are not
  only more portable, more convenient, immune to SQL injection, but are often much faster to execute
  than interpolated queries, as both the server and client side can cache a compiled form of the
  query.
  
  Not all PDO drivers implement this method (notably PDO_ODBC).  Consider using prepared statements
  instead.
  
  The character set must be set either on the server level, or within the database connection itself
  (depending on the driver) for it to affect PDO::quote. See the driver-specific documentation for
  more information.

<comment>Param:</comment>
  <info>string</info>  <strong>$string        </strong>  The string to be quoted.
  <info>int   </info>  <strong>$parameter_type</strong>  Provides a data type hint for drivers that have alternate quoting styles.

<comment>Return:</comment>
  <info>string</info>  Returns a quoted string that is theoretically safe to pass into an SQL statement.  Returns
          <info>false</info> if the driver does not support quoting in this way.

<comment>See Also:</comment>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::execute()</strong>


id: PDO::rollBack
type: function
doc:
<comment>Description:</comment>
  Rolls back a transaction
    
  
  Rolls back the current transaction, as initiated by <strong>PDO::beginTransaction()</strong>.
  
  If the database was set to autocommit mode, this function will restore autocommit mode after it
  has rolled back the transaction.
  
  Some databases, including MySQL, automatically issue an implicit COMMIT when a database definition
  language (DDL) statement such as DROP TABLE or CREATE TABLE is issued within a transaction. The
  implicit COMMIT will prevent you from rolling back any other changes within the transaction
  boundary.

<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>PDO::beginTransaction()</strong>
   * <strong>PDO::commit()</strong>
   * Transactions and auto-commit


id: PDO::setAttribute
type: function
doc:
<comment>Description:</comment>
  Set an attribute
    
  
  Sets an attribute on the database handle. Some of the available generic attributes are listed
  below; some drivers may make use of additional driver specific attributes. <return>PDO::ATTR_CASE</return>: Force
  column names to a specific case. <return>PDO::CASE_LOWER</return>: Force column names to lower case.
  <return>PDO::CASE_NATURAL</return>: Leave column names as returned by the database driver. <return>PDO::CASE_UPPER</return>: Force
  column names to upper case. <return>PDO::ATTR_ERRMODE</return>: Error reporting. <return>PDO::ERRMODE_SILENT</return>: Just set
  error codes.<return>PDO::ERRMODE_WARNING</return>: Raise <info>E_WARNING</info>.<return>PDO::ERRMODE_EXCEPTION</return>: Throw
  exceptions.<return>PDO::ATTR_ORACLE_NULLS</return> (available with all drivers, not just Oracle): Conversion of
  NULL and empty strings. <return>PDO::NULL_NATURAL</return>: No conversion.<return>PDO::NULL_EMPTY_STRING</return>: Empty string is
  converted to <info>null</info>.<return>PDO::NULL_TO_STRING</return>: NULL is converted to an empty string.
  <return>PDO::ATTR_STRINGIFY_FETCHES</return>: Convert numeric values to strings when fetching. Requires <info>bool</info>.
  <return>PDO::ATTR_STATEMENT_CLASS</return>: Set user-supplied statement class derived from PDOStatement. Cannot be
  used with persistent PDO instances. Requires <return>array(string classname, array(mixed
  constructor_args))</return>. <return>PDO::ATTR_TIMEOUT</return>: Specifies the timeout duration in seconds.  Not all drivers
  support this option, and its meaning may differ from driver to driver.  For example, sqlite will
  wait for up to this time value before giving up on obtaining an writable lock, but other drivers
  may interpret this as a connect or a read timeout interval. Requires <info>int</info>. <return>PDO::ATTR_AUTOCOMMIT</return>
  (available in OCI, Firebird and MySQL): Whether to autocommit every single statement.
  <return>PDO::ATTR_EMULATE_PREPARES</return> Enables or disables emulation of prepared statements.  Some drivers do
  not support native prepared statements or have limited support for them. Use this setting to force
  PDO to either always emulate prepared  statements (if <info>true</info> and emulated prepares are supported by
  the driver), or to try to use native prepared statements (if  <info>false</info>).  It will always fall back to
  emulating the prepared statement if the driver cannot successfully prepare the current query.
  Requires <info>bool</info>. <return>PDO::MYSQL_ATTR_USE_BUFFERED_QUERY</return> (available in MySQL): Use buffered queries.
  <return>PDO::ATTR_DEFAULT_FETCH_MODE</return>: Set default fetch mode. Description of modes is available in
  <strong>PDOStatement::fetch()</strong> documentation.
  
  <return>PDO::ATTR_CASE</return>: Force column names to a specific case. <return>PDO::CASE_LOWER</return>: Force column names to
  lower case. <return>PDO::CASE_NATURAL</return>: Leave column names as returned by the database driver.
  <return>PDO::CASE_UPPER</return>: Force column names to upper case.
  
  <return>PDO::CASE_LOWER</return>: Force column names to lower case.
  
  <return>PDO::CASE_NATURAL</return>: Leave column names as returned by the database driver.
  
  <return>PDO::CASE_UPPER</return>: Force column names to upper case.
  
  <return>PDO::ATTR_ERRMODE</return>: Error reporting. <return>PDO::ERRMODE_SILENT</return>: Just set error
  codes.<return>PDO::ERRMODE_WARNING</return>: Raise <info>E_WARNING</info>.<return>PDO::ERRMODE_EXCEPTION</return>: Throw exceptions.
  
  <return>PDO::ERRMODE_SILENT</return>: Just set error codes.
  
  <return>PDO::ERRMODE_WARNING</return>: Raise <info>E_WARNING</info>.
  
  <return>PDO::ERRMODE_EXCEPTION</return>: Throw exceptions.
  
  <return>PDO::ATTR_ORACLE_NULLS</return> (available with all drivers, not just Oracle): Conversion of NULL and empty
  strings. <return>PDO::NULL_NATURAL</return>: No conversion.<return>PDO::NULL_EMPTY_STRING</return>: Empty string is converted to
  <info>null</info>.<return>PDO::NULL_TO_STRING</return>: NULL is converted to an empty string.
  
  <return>PDO::NULL_NATURAL</return>: No conversion.
  
  <return>PDO::NULL_EMPTY_STRING</return>: Empty string is converted to <info>null</info>.
  
  <return>PDO::NULL_TO_STRING</return>: NULL is converted to an empty string.
  
  <return>PDO::ATTR_STRINGIFY_FETCHES</return>: Convert numeric values to strings when fetching. Requires <info>bool</info>.
  
  <return>PDO::ATTR_STATEMENT_CLASS</return>: Set user-supplied statement class derived from PDOStatement. Cannot be
  used with persistent PDO instances. Requires <return>array(string classname, array(mixed
  constructor_args))</return>.
  
  <return>PDO::ATTR_TIMEOUT</return>: Specifies the timeout duration in seconds.  Not all drivers support this
  option, and its meaning may differ from driver to driver.  For example, sqlite will wait for up to
  this time value before giving up on obtaining an writable lock, but other drivers may interpret
  this as a connect or a read timeout interval. Requires <info>int</info>.
  
  <return>PDO::ATTR_AUTOCOMMIT</return> (available in OCI, Firebird and MySQL): Whether to autocommit every single
  statement.
  
  <return>PDO::ATTR_EMULATE_PREPARES</return> Enables or disables emulation of prepared statements.  Some drivers do
  not support native prepared statements or have limited support for them. Use this setting to force
  PDO to either always emulate prepared  statements (if <info>true</info> and emulated prepares are supported by
  the driver), or to try to use native prepared statements (if  <info>false</info>).  It will always fall back to
  emulating the prepared statement if the driver cannot successfully prepare the current query.
  Requires <info>bool</info>.
  
  <return>PDO::MYSQL_ATTR_USE_BUFFERED_QUERY</return> (available in MySQL): Use buffered queries.
  
  <return>PDO::ATTR_DEFAULT_FETCH_MODE</return>: Set default fetch mode. Description of modes is available in
  <strong>PDOStatement::fetch()</strong> documentation.

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


id: PDO::sqliteCreateAggregate
type: function
doc:
<comment>Description:</comment>
  Registers an aggregating User Defined Function for use in SQL statements
    
  
  Această funcție este EXPERIMENTALĂ.
  Comportamentul acestei funcții, denumirea sa și orice alte aspecte documentate
  în privința acestei funcții pot să fie modificate fără preaviz într-o versiune
  viitoare a PHP. Utilizați această funcție la propriul risc.
  
  This method is similar to  except that it registers functions that can be used to calculate a
  result aggregated across all the rows of a query.
  
  The key difference between this method and  is that two functions are required to manage the
  aggregate.

<comment>Param:</comment>
  <info>string  </info>  <strong>$function_name</strong>  The name of the function used in SQL statements.
  <info>callable</info>  <strong>$step_func    </strong>  Callback function called for each row of the result set. Your PHP
                            function should accumulate the result and store it in the aggregation
                            context.
                            
                            This function need to be defined as:
                            <info>mixed</info>step<info>mixed</info><strong>$context</strong><info>int</info><strong>$rownumber</strong><info>mixed</info><strong>$value</strong><info>mixed</info><strong>$values</strong> <strong>$context</strong><info>null</info>
                            for the first row; on subsequent rows it will have the value that was
                            previously returned from the step function; you should use this to
                            maintain the aggregate state. <strong>$rownumber</strong> The current row number. <strong>$value</strong>
                            The first argument passed to the aggregate. <strong>$values</strong> Further arguments
                            passed to the aggregate.  The return value of this function will be used
                            as the <strong>$context</strong> argument in the next call of the step or finalize
                            functions.
                            
                            <info>null</info> for the first row; on subsequent rows it will have the value that
                            was previously returned from the step function; you should use this to
                            maintain the aggregate state.
                            
                            The current row number.
                            
                            The first argument passed to the aggregate.
                            
                            Further arguments passed to the aggregate.
  <info>mixed   </info>  <strong>$context      </strong>  <info>null</info> for the first row; on subsequent rows it will have the value that
                            was previously returned from the step function; you should use this to
                            maintain the aggregate state.
  <info>int     </info>  <strong>$rownumber    </strong>  The current row number.
  <info>mixed   </info>  <strong>$value        </strong>  The first argument passed to the aggregate.
  <info>mixed   </info>  <strong>$values       </strong>  Further arguments passed to the aggregate.
  <info>callable</info>  <strong>$finalize_func</strong>  Callback function to aggregate the "stepped" data from each row.  Once
                            all the rows have been processed, this function will be called and it
                            should then take the data from the aggregation context and return the
                            result. This callback function should return a type understood by SQLite
                            (i.e. scalar type).
                            
                            This function need to be defined as: <info>mixed</info>fini<info>mixed</info><strong>$context</strong><info>int</info><strong>$rowcount</strong>
                            <strong>$context</strong> Holds the return value from the very last call to the step
                            function. <strong>$rowcount</strong> Holds the number of rows over which the aggregate
                            was performed.  The return value of this function will be used as the
                            return value for the aggregate.
                            
                            Holds the return value from the very last call to the step function.
                            
                            Holds the number of rows over which the aggregate was performed.
  <info>mixed   </info>  <strong>$context      </strong>  Holds the return value from the very last call to the step function.
  <info>int     </info>  <strong>$rowcount     </strong>  Holds the number of rows over which the aggregate was performed.
  <info>int     </info>  <strong>$num_args     </strong>  Hint to the SQLite parser if the callback function accepts a
                            predetermined number of arguments.

<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>sqlite_create_function()</strong>
   * <strong>sqlite_create_aggregate()</strong>


id: PDO::sqliteCreateCollation
type: function
doc:
<comment>Description:</comment>
  Registers a User Defined Function for use as a collating function in SQL statements
    
  
  Această funcție este EXPERIMENTALĂ.
  Comportamentul acestei funcții, denumirea sa și orice alte aspecte documentate
  în privința acestei funcții pot să fie modificate fără preaviz într-o versiune
  viitoare a PHP. Utilizați această funcție la propriul risc.

<comment>Param:</comment>
  <info>string  </info>  <strong>$name    </strong>  Name of the SQL collating function to be created or redefined.
  <info>callable</info>  <strong>$callback</strong>  The name of a PHP function or user-defined function to apply as a callback,
                       defining the behavior of the collation. It should accept two strings and
                       return as strcmp() does, i.e. it should return -1, 1, or 0 if the first
                       string sorts before, sorts after, or is equal to the second.
                       
                       This function need to be defined as: <info>int</info>collation<info>string</info><strong>$string1</strong><info>string</info><strong>$string2</strong>

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


id: PDO::sqliteCreateFunction
type: function
doc:
<comment>Description:</comment>
  Registers a User Defined Function for use in SQL statements
    
  
  Această funcție este EXPERIMENTALĂ.
  Comportamentul acestei funcții, denumirea sa și orice alte aspecte documentate
  în privința acestei funcții pot să fie modificate fără preaviz într-o versiune
  viitoare a PHP. Utilizați această funcție la propriul risc.
  
  This method allows you to register a PHP function with SQLite as an  UDF (User Defined Function),
  so that it can be called from within your SQL statements.
  
  The UDF can be used in any SQL statement that can call functions, such as SELECT and UPDATE
  statements and also in triggers.

<comment>Param:</comment>
  <info>string  </info>  <strong>$function_name</strong>  The name of the function used in SQL statements.
  <info>callable</info>  <strong>$callback     </strong>  Callback function to handle the defined SQL function.
                            
                            Callback functions should return a type understood by SQLite (i.e.
                            scalar type).
                            
                            This function need to be defined as:
                            <info>mixed</info>callback<info>mixed</info><strong>$value</strong><info>mixed</info><strong>$values</strong> <strong>$value</strong> The first argument passed to
                            the SQL function. <strong>$values</strong> Further arguments passed to the SQL function.
                            
                            The first argument passed to the SQL function.
                            
                            Further arguments passed to the SQL function.
  <info>mixed   </info>  <strong>$value        </strong>  The first argument passed to the SQL function.
  <info>mixed   </info>  <strong>$values       </strong>  Further arguments passed to the SQL function.
  <info>int     </info>  <strong>$num_args     </strong>  The number of arguments that the SQL function takes. If this parameter
                            is <return>-1</return>, then the SQL function may take any number of arguments.
  <info>int     </info>  <strong>$flags        </strong>  A bitwise conjunction of flags. Currently, only
                            <info>PDO::SQLITE_DETERMINISTIC</info> is supported, which specifies that the
                            function always returns the same result given the same inputs within a
                            single SQL 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>sqlite_create_function()</strong>
   * <strong>sqlite_create_aggregate()</strong>


id: PDOStatement
type: class
doc:
<comment>Description:</comment>
  Represents a prepared statement and, after the statement is executed, an  associated result set.


id: PDOStatement::bindColumn
type: function
doc:
<comment>Description:</comment>
  Bind a column to a PHP variable
    
  
  <strong>PDOStatement::bindColumn()</strong> arranges to have a particular variable bound to a given column in the
  result-set from a query.  Each call to <strong>PDOStatement::fetch()</strong> or <strong>PDOStatement::fetchAll()</strong> will
  update all the variables that are bound to columns.
  
  Since information about the columns is not always available to PDO until the statement is
  executed, portable applications should call this function after <strong>PDOStatement::execute()</strong>.
  
  However, to be able to bind a LOB column as a stream when using the PgSQL driver, applications
  should call this method before calling <strong>PDOStatement::execute()</strong>, otherwise the large object OID
  will be returned as an integer.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$column    </strong>  Number of the column (1-indexed) or name of the column in the result set. If
                      using the column name, be aware that the name should match the case of the
                      column, as returned by the driver.
  <info>mixed</info>  <strong>$param     </strong>  Name of the PHP variable to which the column will be bound.
  <info>int  </info>  <strong>$type      </strong>  Data type of the parameter, specified by the <return>PDO::PARAM_*</return> constants.
  <info>int  </info>  <strong>$maxlen    </strong>  A hint for pre-allocation.
  <info>mixed</info>  <strong>$driverdata</strong>  Optional parameter(s) for the driver.

<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>PDOStatement::execute()</strong>
   * <strong>PDOStatement::fetch()</strong>
   * <strong>PDOStatement::fetchAll()</strong>
   * <strong>PDOStatement::fetchColumn()</strong>


id: PDOStatement::bindParam
type: function
doc:
<comment>Description:</comment>
  Binds a parameter to the specified variable name
    
  
  Binds a PHP variable to a corresponding named or question mark placeholder in the SQL statement
  that was used to prepare the statement.  Unlike <strong>PDOStatement::bindValue()</strong>, the variable is bound
  as a reference and will only be evaluated at the time that <strong>PDOStatement::execute()</strong> is called.
  
  Most parameters are input parameters, that is, parameters that are used in a read-only fashion to
  build up the query (but may nonetheless be cast according to <strong>$data_type</strong>).  Some drivers support
  the invocation of stored procedures that return data as output parameters, and some also as
  input/output parameters that both send in data and are updated to receive it.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$parameter     </strong>  Parameter identifier. For a prepared statement using named placeholders,
                          this will be a parameter name of the form :name. For a prepared statement
                          using question mark placeholders, this will be the 1-indexed position of
                          the parameter.
  <info>mixed</info>  <strong>$variable      </strong>  Name of the PHP variable to bind to the SQL statement parameter.
  <info>int  </info>  <strong>$data_type     </strong>  Explicit data type for the parameter using the <return>PDO::PARAM_*</return> constants. To
                          return an INOUT parameter from a stored procedure,  use the bitwise OR
                          operator to set the PDO::PARAM_INPUT_OUTPUT bits for the <strong>$data_type</strong>
                          parameter.
  <info>int  </info>  <strong>$length        </strong>  Length of the data type. To indicate that a parameter is an OUT parameter
                          from a stored procedure, you must explicitly set the length.
  <info>mixed</info>  <strong>$driver_options</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>PDO::prepare()</strong>
   * <strong>PDOStatement::execute()</strong>
   * <strong>PDOStatement::bindValue()</strong>


id: PDOStatement::bindValue
type: function
doc:
<comment>Description:</comment>
  Binds a value to a parameter
    
  
  Binds a value to a corresponding named or question mark placeholder in the SQL statement that was
  used to prepare the statement.

<comment>Param:</comment>
  <info>mixed</info>  <strong>$parameter</strong>  Parameter identifier. For a prepared statement using named placeholders, this
                     will be a parameter name of the form :name. For a prepared statement using
                     question mark placeholders, this will be the 1-indexed position of the
                     parameter.
  <info>mixed</info>  <strong>$value    </strong>  The value to bind to the parameter.
  <info>int  </info>  <strong>$data_type</strong>  Explicit data type for the parameter using the <return>PDO::PARAM_*</return> constants.

<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>PDO::prepare()</strong>
   * <strong>PDOStatement::execute()</strong>
   * <strong>PDOStatement::bindParam()</strong>


id: PDOStatement::closeCursor
type: function
doc:
<comment>Description:</comment>
  Closes the cursor, enabling the statement to be executed again
    
  
  <strong>PDOStatement::closeCursor()</strong> frees up the connection to the server so that other SQL statements may
  be issued, but leaves the statement in a state that enables it to be executed again.
  
  This method is useful for database drivers that do not support executing a PDOStatement object
  when a previously executed PDOStatement object still has unfetched rows. If your database driver
  suffers from this limitation, the problem may manifest itself in an out-of-sequence error.
  
  <strong>PDOStatement::closeCursor()</strong> is implemented either as an optional driver specific method (allowing
  for maximum efficiency), or as the generic PDO fallback if no driver specific function is
  installed. The PDO generic fallback is semantically the same as writing the following code in your
  PHP script: fetch()) ; if (!$stmt->nextRowset()) break;
  } while (true);
  ?>
  ]]>

<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>PDOStatement::execute()</strong>


id: PDOStatement::columnCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of columns in the result set
    
  
  Use <strong>PDOStatement::columnCount()</strong> to return the number of columns in the result set represented by
  the PDOStatement object.
  
  If the PDOStatement object was returned from <strong>PDO::query()</strong>, the column count is immediately
  available.
  
  If the PDOStatement object was returned from <strong>PDO::prepare()</strong>, an accurate column count will not be
  available until you invoke <strong>PDOStatement::execute()</strong>.

<comment>Return:</comment>
  <info>int</info>  Returns the number of columns in the result set represented by the PDOStatement object, even
       if the result set is empty. If there is no result set, <strong>PDOStatement::columnCount()</strong> returns <return>0</return>.

<comment>See Also:</comment>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::execute()</strong>
   * <strong>PDOStatement::rowCount()</strong>


id: PDOStatement::debugDumpParams
type: function
doc:
<comment>Description:</comment>
  Dump an SQL prepared command
    
  
  Dumps the information contained by a prepared statement directly on the output. It will provide
  the <return>SQL</return> query in use, the  number of parameters used (<return>Params</return>), the list of parameters with their
  key name or position, their name, their position in the query (if this is supported by the PDO
  driver, otherwise, it will be -1), type (<return>param_type</return>) as an integer, and a boolean value <return>is_param</return>.
  
  This is a debug function, which dumps the data directly to the normal output.  
  La fel ca și orice program/script ce afișează rezultatele direct în browser,
  funcțiile de control al ieșirilor pot fi
  utilizate pentru a capta ieșirea acestei funcții și de a o salva într-un
  <info>string</info> (spre exemplu).
  
  La fel ca și orice program/script ce afișează rezultatele direct în browser,
  funcțiile de control al ieșirilor pot fi
  utilizate pentru a capta ieșirea acestei funcții și de a o salva într-un
  <info>string</info> (spre exemplu).
  
  This will only dump the parameters in the statement at the moment of the dump. Extra parameters
  are not stored in the statement, and not displayed.

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

<comment>See Also:</comment>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::bindParam()</strong>
   * <strong>PDOStatement::bindValue()</strong>


id: PDOStatement::errorCode
type: function
doc:
<comment>Description:</comment>
  Fetch the SQLSTATE associated with the last operation on the statement handle

<comment>Return:</comment>
  <info>string</info>  Identical to <strong>PDO::errorCode()</strong>, except that  <strong>PDOStatement::errorCode()</strong> only retrieves error
          codes for operations performed with PDOStatement objects.

<comment>See Also:</comment>
   * <strong>PDO::errorCode()</strong>
   * <strong>PDO::errorInfo()</strong>
   * <strong>PDOStatement::errorInfo()</strong>


id: PDOStatement::errorInfo
type: function
doc:
<comment>Description:</comment>
  Fetch extended error information associated with the last operation on the statement handle

<comment>Return:</comment>
  <info>array</info>  <strong>PDOStatement::errorInfo()</strong> returns an array of error information about the last operation
         performed by this statement handle. The array consists of at least the following fields:
         ElementInformation0SQLSTATE error code (a five characters alphanumeric identifier defined
         in the ANSI SQL standard).1Driver specific error code.2Driver specific error message.

<comment>See Also:</comment>
   * <strong>PDO::errorCode()</strong>
   * <strong>PDO::errorInfo()</strong>
   * <strong>PDOStatement::errorCode()</strong>


id: PDOStatement::execute
type: function
doc:
<comment>Description:</comment>
  Executes a prepared statement
    
  
  Execute the prepared statement. If the prepared statement included parameter markers, either:
  <strong>PDOStatement::bindParam()</strong> and/or <strong>PDOStatement::bindValue()</strong> has to be called to bind either
  variables or values (respectively) to the parameter markers. Bound variables pass their value as
  input and receive the output value, if any, of their associated parameter markersor an array of
  input-only parameter values has to be passed
  
  <strong>PDOStatement::bindParam()</strong> and/or <strong>PDOStatement::bindValue()</strong> has to be called to bind either
  variables or values (respectively) to the parameter markers. Bound variables pass their value as
  input and receive the output value, if any, of their associated parameter markers
  
  or an array of input-only parameter values has to be passed

<comment>Param:</comment>
  <info>array</info>  <strong>$input_parameters</strong>  An array of values with as many elements as there are bound parameters
                            in the SQL statement being executed. All values are treated as
                            <info>PDO::PARAM_STR</info>.
                            
                            Multiple values cannot be bound to a single parameter; for example, it
                            is not allowed to bind two values to a single named parameter in an IN()
                            clause.
                            
                            Binding more values than specified is not possible; if more keys exist
                            in  <strong>$input_parameters</strong> than in the SQL specified  in the PDO::prepare,
                            then the statement will  fail and an error is emitted.

<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>PDO::prepare()</strong>
   * <strong>PDOStatement::bindParam()</strong>
   * <strong>PDOStatement::fetch()</strong>
   * <strong>PDOStatement::fetchAll()</strong>
   * <strong>PDOStatement::fetchColumn()</strong>


id: PDOStatement::fetch
type: function
doc:
<comment>Description:</comment>
  Fetches the next row from a result set
    
  
  Fetches a row from a result set associated with a PDOStatement object. The <strong>$fetch_style</strong> parameter
  determines how PDO returns the row.

<comment>Param:</comment>
  <info>int</info>  <strong>$fetch_style       </strong>  Controls how the next row will be returned to the caller. This value
                            must be one of the <return>PDO::FETCH_*</return> constants, defaulting to value of
                            <return>PDO::ATTR_DEFAULT_FETCH_MODE</return> (which defaults to <return>PDO::FETCH_BOTH</return>).
                            <return>PDO::FETCH_ASSOC</return>: returns an array indexed by column name as returned in
                            your result set <return>PDO::FETCH_BOTH</return> (default): returns an array indexed by
                            both column name and 0-indexed column number as returned in your result
                            set <return>PDO::FETCH_BOUND</return>: returns <info>true</info> and assigns the values of the columns
                            in your result set to the PHP variables to which they were bound with
                            the <strong>PDOStatement::bindColumn()</strong> method <return>PDO::FETCH_CLASS</return>: returns a new
                            instance of the requested class, mapping the columns of the result set
                            to named properties in the class, and calling the constructor
                            afterwards, unless <return>PDO::FETCH_PROPS_LATE</return> is also given. If <strong>$fetch_style</strong>
                            includes PDO::FETCH_CLASSTYPE (e.g. <return>PDO::FETCH_CLASS |
                            PDO::FETCH_CLASSTYPE</return>) then the name of the class is determined from a
                            value of the first column. <return>PDO::FETCH_INTO</return>: updates an existing instance
                            of the requested class, mapping the columns of the result set to named
                            properties in the class <return>PDO::FETCH_LAZY</return>: combines <return>PDO::FETCH_BOTH</return> and
                            <return>PDO::FETCH_OBJ</return>, creating the object variable names as they are accessed
                            <return>PDO::FETCH_NAMED</return>: returns an array with the same form as
                            <return>PDO::FETCH_ASSOC</return>, except that if there are multiple columns with the
                            same name, the value referred to by that key will be an array of all the
                            values in the row that had that column name <return>PDO::FETCH_NUM</return>: returns an
                            array indexed by column number as returned in your result set, starting
                            at column 0 <return>PDO::FETCH_OBJ</return>: returns an anonymous object with property
                            names that correspond to the column names returned in your result set
                            <return>PDO::FETCH_PROPS_LATE</return>: when used with <return>PDO::FETCH_CLASS</return>, the constructor
                            of the class is called before the properties are assigned from the
                            respective column values.
                            
                            <return>PDO::FETCH_ASSOC</return>: returns an array indexed by column name as returned in
                            your result set
                            
                            <return>PDO::FETCH_BOTH</return> (default): returns an array indexed by both column name
                            and 0-indexed column number as returned in your result set
                            
                            <return>PDO::FETCH_BOUND</return>: returns <info>true</info> and assigns the values of the columns in
                            your result set to the PHP variables to which they were bound with the
                            <strong>PDOStatement::bindColumn()</strong> method
                            
                            <return>PDO::FETCH_CLASS</return>: returns a new instance of the requested class, mapping
                            the columns of the result set to named properties in the class, and
                            calling the constructor afterwards, unless <return>PDO::FETCH_PROPS_LATE</return> is also
                            given. If <strong>$fetch_style</strong> includes PDO::FETCH_CLASSTYPE (e.g.
                            <return>PDO::FETCH_CLASS | PDO::FETCH_CLASSTYPE</return>) then the name of the class is
                            determined from a value of the first column.
                            
                            <return>PDO::FETCH_INTO</return>: updates an existing instance of the requested class,
                            mapping the columns of the result set to named properties in the class
                            
                            <return>PDO::FETCH_LAZY</return>: combines <return>PDO::FETCH_BOTH</return> and <return>PDO::FETCH_OBJ</return>, creating
                            the object variable names as they are accessed
                            
                            <return>PDO::FETCH_NAMED</return>: returns an array with the same form as
                            <return>PDO::FETCH_ASSOC</return>, except that if there are multiple columns with the
                            same name, the value referred to by that key will be an array of all the
                            values in the row that had that column name
                            
                            <return>PDO::FETCH_NUM</return>: returns an array indexed by column number as returned in
                            your result set, starting at column 0
                            
                            <return>PDO::FETCH_OBJ</return>: returns an anonymous object with property names that
                            correspond to the column names returned in your result set
                            
                            <return>PDO::FETCH_PROPS_LATE</return>: when used with <return>PDO::FETCH_CLASS</return>, the constructor
                            of the class is called before the properties are assigned from the
                            respective column values.
  <info>int</info>  <strong>$cursor_orientation</strong>  For a PDOStatement object representing a scrollable cursor, this value
                            determines which row will be returned to the caller. This value must be
                            one of the <return>PDO::FETCH_ORI_*</return> constants, defaulting to
                            <return>PDO::FETCH_ORI_NEXT</return>. To request a scrollable cursor for your
                            PDOStatement object, you must set the <return>PDO::ATTR_CURSOR</return> attribute to
                            <return>PDO::CURSOR_SCROLL</return> when you prepare the SQL statement with
                            <strong>PDO::prepare()</strong>.
  <info>   </info>  <strong>$offset            </strong>  For a PDOStatement object representing a scrollable cursor for which the
                            <return>cursor_orientation</return> parameter is set to <return>PDO::FETCH_ORI_ABS</return>, this value
                            specifies the absolute number of the row in the result set that shall be
                            fetched.
                            
                            For a PDOStatement object representing a scrollable cursor for which the
                            <return>cursor_orientation</return> parameter is set to <return>PDO::FETCH_ORI_REL</return>, this value
                            specifies the row to fetch relative to the cursor position before
                            <strong>PDOStatement::fetch()</strong> was called.

<comment>Return:</comment>
  <info>mixed</info>  The return value of this function on success depends on the fetch type. In all cases, <info>false</info>
         is returned on failure.

<comment>See Also:</comment>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::execute()</strong>
   * <strong>PDOStatement::fetchAll()</strong>
   * <strong>PDOStatement::fetchColumn()</strong>
   * <strong>PDOStatement::fetchObject()</strong>
   * <strong>PDOStatement::setFetchMode()</strong>


id: PDOStatement::fetchAll
type: function
doc:
<comment>Description:</comment>
  Returns an array containing all of the result set rows

<comment>Param:</comment>
  <info>int  </info>  <strong>$fetch_style   </strong>  Controls the contents of the returned array as documented in
                          <strong>PDOStatement::fetch()</strong>. Defaults to value of <info>PDO::ATTR_DEFAULT_FETCH_MODE</info>
                          (which defaults to <info>PDO::FETCH_BOTH</info>)
                          
                          To return an array consisting of all values of a single column from the
                          result set, specify <info>PDO::FETCH_COLUMN</info>. You can specify which column you
                          want with the <strong>$fetch_argument</strong> parameter.
                          
                          To fetch only the unique values of a single column from the result set,
                          bitwise-OR <info>PDO::FETCH_COLUMN</info> with <info>PDO::FETCH_UNIQUE</info>.
                          
                          To return an associative array grouped by the values of a specified
                          column, bitwise-OR <info>PDO::FETCH_COLUMN</info> with <info>PDO::FETCH_GROUP</info>.
  <info>mixed</info>  <strong>$fetch_argument</strong>  This argument has a different meaning depending on the value of  the
                          <strong>$fetch_style</strong> parameter: <info>PDO::FETCH_COLUMN</info>: Returns the indicated 0-indexed
                          column. <info>PDO::FETCH_CLASS</info>: Returns instances of the specified class,
                          mapping the columns of each row to named properties in the class.
                          <info>PDO::FETCH_FUNC</info>: Returns the results of calling the specified function,
                          using each row's columns as parameters in the call.
                          
                          <info>PDO::FETCH_COLUMN</info>: Returns the indicated 0-indexed  column.
                          
                          <info>PDO::FETCH_CLASS</info>: Returns instances of the specified class, mapping the
                          columns of each row to named properties in the class.
                          
                          <info>PDO::FETCH_FUNC</info>: Returns the results of calling the specified function,
                          using each row's columns as parameters in the call.
  <info>array</info>  <strong>$ctor_args     </strong>  Arguments of custom class constructor when the <strong>$fetch_style</strong>  parameter is
                          <info>PDO::FETCH_CLASS</info>.

<comment>Return:</comment>
  <info>array</info>  <strong>PDOStatement::fetchAll()</strong> returns an array containing all of the remaining rows in the
         result set. The array represents each row as either an array of column values or an object
         with properties corresponding to each column name. An empty array is returned if there are
         zero results to fetch, or <info>false</info> on failure.
         
         Using this method to fetch large result sets will result in a heavy demand on system and
         possibly network resources. Rather than retrieving all of the data and manipulating it in
         PHP, consider using the database server to manipulate the result sets. For example, use the
         WHERE and ORDER BY clauses in SQL to restrict results before retrieving and processing them
         with PHP.

<comment>See Also:</comment>
   * <strong>PDO::query()</strong>
   * <strong>PDOStatement::fetch()</strong>
   * <strong>PDOStatement::fetchColumn()</strong>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::setFetchMode()</strong>


id: PDOStatement::fetchColumn
type: function
doc:
<comment>Description:</comment>
  Returns a single column from the next row of a result set
    
  
  Returns a single column from the next row of a result set or <info>false</info> if there are no more rows.
  
  <strong>PDOStatement::fetchColumn()</strong> should not be used to retrieve boolean columns, as it is impossible to
  distinguish a value of <info>false</info> from there being no more rows to retrieve. Use <strong>PDOStatement::fetch()</strong>
  instead.

<comment>Param:</comment>
  <info>int</info>  <strong>$column_number</strong>  0-indexed number of the column you wish to retrieve from the row. If no value
                       is supplied, <strong>PDOStatement::fetchColumn()</strong> fetches the first column.

<comment>Return:</comment>
  <info>mixed</info>  <strong>PDOStatement::fetchColumn()</strong> returns a single column from the next row of a result set or
         <info>false</info> if there are no more rows.
         
         There is no way to return another column from the same row if you use
         <strong>PDOStatement::fetchColumn()</strong> to retrieve data.

<comment>See Also:</comment>
   * <strong>PDO::query()</strong>
   * <strong>PDOStatement::fetch()</strong>
   * <strong>PDOStatement::fetchAll()</strong>
   * <strong>PDO::prepare()</strong>
   * <strong>PDOStatement::setFetchMode()</strong>


id: PDOStatement::fetchObject
type: function
doc:
<comment>Description:</comment>
  Fetches the next row and returns it as an object
  
  Fetches the next row and returns it as an object. This function is an alternative to
  <strong>PDOStatement::fetch()</strong> with <info>PDO::FETCH_CLASS</info> or <info>PDO::FETCH_OBJ</info> style.
  
  When an object is fetched, its properties are assigned from respective column values, and
  afterwards its constructor is invoked.

<comment>Param:</comment>
  <info>string</info>  <strong>$class_name</strong>  Name of the created class.
  <info>array </info>  <strong>$ctor_args </strong>  Elements of this array are passed to the constructor.

<comment>Return:</comment>
  <info>objectfalse</info>  Returns an instance of the required class with property names that correspond to the
               column names  sau <info>false</info> în cazul eșecului.

<comment>See Also:</comment>
   * <strong>PDOStatement::fetch()</strong>


id: PDOStatement::getAttribute
type: function
doc:
<comment>Description:</comment>
  Retrieve a statement attribute
    
  
  Gets an attribute of the statement. Currently, no generic attributes exist but only driver
  specific: <return>PDO::ATTR_CURSOR_NAME</return> (Firebird and ODBC specific): Get the name of cursor for <return>UPDATE
  ... WHERE CURRENT OF</return>.
  
  <return>PDO::ATTR_CURSOR_NAME</return> (Firebird and ODBC specific): Get the name of cursor for <return>UPDATE ... WHERE
  CURRENT OF</return>.

<comment>Return:</comment>
  <info>mixed</info>  Returns the attribute value.

<comment>See Also:</comment>
   * <strong>PDO::getAttribute()</strong>
   * <strong>PDO::setAttribute()</strong>
   * <strong>PDOStatement::setAttribute()</strong>


id: PDOStatement::getColumnMeta
type: function
doc:
<comment>Description:</comment>
  Returns metadata for a column in a result set
    
  
  Retrieves the metadata for a 0-indexed column in a result set as an associative array.
  
  Not all PDO drivers support <strong>PDOStatement::getColumnMeta()</strong>.
  
  The following drivers support this method:
  
  PDO_DBLIB
  
  PDO_MYSQL
  
  PDO_PGSQL
  
  PDO_SQLITE

<comment>Param:</comment>
  <info>int</info>  <strong>$column</strong>  The 0-indexed column in the result set.

<comment>Return:</comment>
  <info>array</info>  Returns an associative array containing the following values representing the metadata for
         a single column:
         
         Returns <info>false</info> if the requested column does not exist in the result set, or if no result set
         exists.

<comment>See Also:</comment>
   * <strong>PDOStatement::columnCount()</strong>
   * <strong>PDOStatement::rowCount()</strong>


id: PDOStatement::nextRowset
type: function
doc:
<comment>Description:</comment>
  Advances to the next rowset in a multi-rowset statement handle
    
  
  Some database servers support stored procedures that return more than one rowset (also known as a
  result set). <strong>PDOStatement::nextRowset()</strong> enables you to access the second and subsequent rowsets
  associated with a PDOStatement object. Each rowset can have a different set of columns from the
  preceding rowset.

<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>PDOStatement::columnCount()</strong>
   * <strong>PDOStatement::execute()</strong>
   * <strong>PDOStatement::getColumnMeta()</strong>
   * <strong>PDO::query()</strong>


id: PDOStatement::rowCount
type: function
doc:
<comment>Description:</comment>
  Returns the number of rows affected by the last SQL statement
    
  
  <strong>PDOStatement::rowCount()</strong> returns the number of rows affected by the last DELETE, INSERT, or UPDATE
  statement executed by the corresponding <return>PDOStatement</return> object.
  
  If the last SQL statement executed by the associated  <return>PDOStatement</return> was a SELECT statement, some
  databases may return the number of rows returned by that statement. However, this behaviour is not
  guaranteed for all databases and should not be relied on for portable applications.
  
  This method returns "0" (zero) with the SQLite driver at all times, and with the PostgreSQL driver
  only when setting the <info>PDO::ATTR_CURSOR</info> statement attribute to <info>PDO::CURSOR_SCROLL</info>.

<comment>Return:</comment>
  <info>int</info>  Returns the number of rows.

<comment>See Also:</comment>
   * <strong>PDOStatement::columnCount()</strong>
   * <strong>PDOStatement::fetchColumn()</strong>
   * <strong>PDO::query()</strong>


id: PDOStatement::setAttribute
type: function
doc:
<comment>Description:</comment>
  Set a statement attribute
    
  
  Sets an attribute on the statement. Currently, no generic attributes are set but only driver
  specific: <return>PDO::ATTR_CURSOR_NAME</return> (Firebird and ODBC specific): Set the name of cursor for <return>UPDATE
  ... WHERE CURRENT OF</return>.
  
  <return>PDO::ATTR_CURSOR_NAME</return> (Firebird and ODBC specific): Set the name of cursor for <return>UPDATE ... WHERE
  CURRENT OF</return>.

<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>PDO::getAttribute()</strong>
   * <strong>PDO::setAttribute()</strong>
   * <strong>PDOStatement::getAttribute()</strong>


id: PDOStatement::setFetchMode
type: function
doc:
<comment>Description:</comment>
  Set the default fetch mode for this statement

<comment>Param:</comment>
  <info>int   </info>  <strong>$mode     </strong>  The fetch mode must be one of the <return>PDO::FETCH_*</return> constants.
  <info>int   </info>  <strong>$colno    </strong>  Column number.
  <info>string</info>  <strong>$classname</strong>  Class name.
  <info>array </info>  <strong>$ctorargs </strong>  Constructor arguments.
  <info>object</info>  <strong>$object   </strong>  Object.

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


id: PGSQL_ASSOC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_fetch_array()</strong>. Return an associative array of field names and values.


id: PGSQL_BAD_RESPONSE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. The server's response  was not understood.


id: PGSQL_BOTH
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_fetch_array()</strong>. Return an array of field values that is both numerically indexed (by
  field number) and associated (by field name).


id: PGSQL_COMMAND_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Successful completion of a  command returning no data.


id: PGSQL_CONNECTION_BAD
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connection_status()</strong> indicating that the database connection is in an invalid state.


id: PGSQL_CONNECTION_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connection_status()</strong> indicating that the database connection is in a valid state.


id: PGSQL_CONNECT_ASYNC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_connect()</strong> to create an asynchronous connection. Added in PHP 5.6.0.


id: PGSQL_CONNECT_FORCE_NEW
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_connect()</strong> to force the creation of a new connection, rather than re-using an existing
  identical connection.


id: PGSQL_CONV_FORCE_NULL
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_convert()</strong>. Use SQL <return>NULL</return> in place of an empty <info>string</info>.


id: PGSQL_CONV_IGNORE_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_convert()</strong>. Ignore default values in the table during conversion.


id: PGSQL_CONV_IGNORE_NOT_NULL
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_convert()</strong>. Ignore conversion of <info>null</info> into SQL <return>NOT NULL</return> columns.


id: PGSQL_COPY_IN
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Copy In (to server) data  transfer started.


id: PGSQL_COPY_OUT
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Copy Out (from server) data  transfer started.


id: PGSQL_DIAG_CONTEXT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. An indication of the context in which the error occurred.
  Presently  this includes a call stack traceback of active procedural language  functions and
  internally-generated queries. The trace is one entry  per line, most recent first.


id: PGSQL_DIAG_INTERNAL_POSITION
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. This is defined the same as the <info>PG_DIAG_STATEMENT_POSITION</info>
  field, but  it is used when the cursor position refers to an internally generated  command rather
  than the one submitted by the client. The  <info>PG_DIAG_INTERNAL_QUERY</info> field will always appear when
  this  field appears.


id: PGSQL_DIAG_INTERNAL_QUERY
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The text of a failed internally-generated command. This could
  be, for example, a  SQL query issued by a PL/pgSQL function.


id: PGSQL_DIAG_MESSAGE_DETAIL
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. Detail: an optional secondary error message carrying more
  detail about the problem. May run to multiple lines.


id: PGSQL_DIAG_MESSAGE_HINT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. Hint: an optional suggestion what to do about the problem. This
  is intended to differ from detail in that it offers advice (potentially inappropriate) rather than
  hard facts. May run to multiple lines.


id: PGSQL_DIAG_MESSAGE_PRIMARY
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The primary human-readable error message (typically one line).
  Always present.


id: PGSQL_DIAG_SEVERITY
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The severity; the field contents are <return>ERROR</return>,  <return>FATAL</return>, or <return>PANIC</return>
  (in an error message), or  <return>WARNING</return>, <return>NOTICE</return>, <return>DEBUG</return>,  <return>INFO</return>, or <return>LOG</return> (in a notice message), or a
  localized  translation of one of these. Always present.


id: PGSQL_DIAG_SEVERITY_NONLOCALIZED
type: constant
doc:
<comment>Description:</comment>
  The severity; the field contents are ERROR, FATAL, or PANIC (in an error message), or WARNING,
  NOTICE, DEBUG, INFO, or LOG (in a notice message). This is identical to the PG_DIAG_SEVERITY field
  except that the contents are never localized. This is present only in versions 9.6 and later / PHP
  7.3.0 and later.


id: PGSQL_DIAG_SOURCE_FILE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The file name of the PostgreSQL source-code location where the
  error  was reported.


id: PGSQL_DIAG_SOURCE_FUNCTION
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The name of the PostgreSQL source-code function reporting the
  error.


id: PGSQL_DIAG_SOURCE_LINE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The line number of the PostgreSQL source-code location where
  the  error was reported.


id: PGSQL_DIAG_SQLSTATE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. The SQLSTATE code for the error. The SQLSTATE code identifies
  the type of error  that has occurred; it can be used by front-end applications to perform specific
  operations (such as error handling) in response to a particular database error.  This field is not
  localizable, and is always present.


id: PGSQL_DIAG_STATEMENT_POSITION
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_error_field()</strong>. A string containing a decimal integer indicating an error
  cursor position as an index into the original  statement string. The first character has index 1,
  and positions are measured in characters not bytes.


id: PGSQL_DML_ASYNC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Execute asynchronous query by
  these functions.


id: PGSQL_DML_ESCAPE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Apply escape to all parameters
  instead of calling <strong>pg_convert()</strong> internally. This option omits meta data look up. Query could be as
  fast as <strong>pg_query()</strong> and <strong>pg_send_query()</strong>. Available since PHP 5.6.0.


id: PGSQL_DML_EXEC
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Execute query by these functions.


id: PGSQL_DML_NO_CONV
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. All parameters passed as is.
  Manual escape is required if parameters contain user supplied data. Use <strong>pg_escape_string()</strong> for it.


id: PGSQL_DML_STRING
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_insert()</strong>, <strong>pg_select()</strong>, <strong>pg_update()</strong> and <strong>pg_delete()</strong>. Return executed query string.


id: PGSQL_EMPTY_QUERY
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. The string sent to the server was empty.


id: PGSQL_ERRORS_DEFAULT
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_set_error_verbosity()</strong>. The default mode produces messages that include the above
  plus any detail, hint, or context fields (these may span  multiple lines).


id: PGSQL_ERRORS_TERSE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_set_error_verbosity()</strong>. Specified that returned messages include severity, primary
  text,  and position only; this will normally fit on a single line.


id: PGSQL_ERRORS_VERBOSE
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_set_error_verbosity()</strong>. The verbose mode includes all available fields.


id: PGSQL_FATAL_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. A fatal error  occurred.


id: PGSQL_NONFATAL_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. A nonfatal error  (a notice or warning) occurred.


id: PGSQL_NOTICE_ALL
type: constant
doc:
<comment>Description:</comment>
  Used by <strong>pg_last_notice()</strong>. Available since PHP 7.1.0.


id: PGSQL_NUM
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_fetch_array()</strong>. Return a numerically indexed array of field numbers and values.


id: PGSQL_POLLING_ACTIVE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is currently active. Available since
  PHP 5.6.0.


id: PGSQL_POLLING_FAILED
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection attempt failed. Available since PHP
  5.6.0.


id: PGSQL_POLLING_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is ready to be used. Available since
  PHP 5.6.0.


id: PGSQL_POLLING_READING
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is waiting for the PostgreSQL socket
  to be readable. Available since PHP 5.6.0.


id: PGSQL_POLLING_WRITING
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_connect_poll()</strong> to indicate that the connection is waiting for the PostgreSQL socket
  to be writable. Available since PHP 5.6.0.


id: PGSQL_SEEK_CUR
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_lo_seek()</strong>. Seek operation is to begin from the current position.


id: PGSQL_SEEK_END
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_lo_seek()</strong>. Seek operation is to begin from the end of the object.


id: PGSQL_SEEK_SET
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_lo_seek()</strong>. Seek operation is to begin from the start of the object.


id: PGSQL_STATUS_LONG
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_status()</strong>.  Indicates that numerical result code is desired.


id: PGSQL_STATUS_STRING
type: constant
doc:
<comment>Description:</comment>
  Passed to <strong>pg_result_status()</strong>.  Indicates that textual result command tag is desired.


id: PGSQL_TRANSACTION_ACTIVE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. A command is in progress on the connection.  A query has been
  sent via the connection and not yet completed.


id: PGSQL_TRANSACTION_IDLE
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. Connection is currently idle, not in a transaction.


id: PGSQL_TRANSACTION_INERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. The connection is idle, in a failed transaction block.


id: PGSQL_TRANSACTION_INTRANS
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. The connection is idle, in a transaction block.


id: PGSQL_TRANSACTION_UNKNOWN
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_transaction_status()</strong>. The connection is bad.


id: PGSQL_TUPLES_OK
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>pg_result_status()</strong>. Successful completion of a command  returning data (such as a
  <return>SELECT</return> or <return>SHOW</return>).


id: PHP_BINARY
type: constant
doc:
<comment>Description:</comment>
  Specifică calea către binarul PHP la executarea scriptului. Disponibilă începând cu PHP 5.4.


id: PHP_EOL
type: constant
doc:
<comment>Description:</comment>
  Simbolul corect pentru 'End Of Line' (sfârșit de linie) pentru această platformă. Disponibilă
  începând cu PHP 5.0.2.


id: PHP_EXTRA_VERSION
type: constant
doc:
<comment>Description:</comment>
  Versiunea "extra" curentă a PHP ca șir de caractere (de ex. '-extra' pentru versiunea
  "5.2.7-extra"). Deseori utilizată de distribuitori pentru a indica versiunea pachetului.
  Disponibilă începând cu PHP 5.2.7.


id: PHP_FD_SETSIZE
type: constant
doc:
<comment>Description:</comment>
  Numărul maxim al descriptorilor de fișiere pentru anumite apeluri de sistem. Disponibilă începând
  cu PHP 7.1.0.


id: PHP_FLOAT_DIG
type: constant
doc:
<comment>Description:</comment>
  Numărul de zecimale care pot fi rotunjite în float și înapoi fără a pierde din precizie.
  Disponibilă începând cu PHP 7.2.0.


id: PHP_FLOAT_EPSILON
type: constant
doc:
<comment>Description:</comment>
  Cel mai mic număr real pozitiv reprezentabil x, astfel încât <return>x + 1.0 != 1.0</return>. Disponibilă începând
  cu PHP 7.2.0.


id: PHP_FLOAT_MAX
type: constant
doc:
<comment>Description:</comment>
  Cel mai mare număr real reprezentabil. Disponibilă începând cu PHP 7.2.0.


id: PHP_FLOAT_MIN
type: constant
doc:
<comment>Description:</comment>
  Cel mai mic număr real pozitiv reprezentabil. Dacă aveți nevoie de de cel mai mic număr real
  negativ reprezentabil, utilizați <return>- PHP_FLOAT_MAX</return>. Disponibilă începând cu PHP 7.2.0.


id: PHP_INT_MAX
type: constant
doc:
<comment>Description:</comment>
  Cea mai mare valoare întreagă susținută în această asamblare a PHP. De regulă int(2147483647) pe
  sisteme de 32 biți și int(9223372036854775807) pe sisteme de 64 biți. Disponibilă începând cu PHP
  5.0.5.


id: PHP_INT_MIN
type: constant
doc:
<comment>Description:</comment>
  Cea mai mică valoare întreagă susținută în această asamblare a PHP. De regulă int(-2147483648) pe
  sisteme de 32 biți și int(-9223372036854775808) pe sisteme de 64 biți. Disponibilă începând cu PHP
  7.0.0. De obicei PHP_INT_MIN === ~PHP_INT_MAX.


id: PHP_INT_SIZE
type: constant
doc:
<comment>Description:</comment>
  Dimensiunea în octeți a unui întreg în această asamblare a PHP. Disponibilă începând cu PHP 5.0.5.


id: PHP_MAJOR_VERSION
type: constant
doc:
<comment>Description:</comment>
  Versiunea "majoră" curentă a PHP ca număr întreg (de ex. int(5) pentru versiunea "5.2.7-extra").
  Disponibilă începând cu PHP 5.2.7.


id: PHP_MANDIR
type: constant
doc:
<comment>Description:</comment>
  Specifică unde au fost instalate paginile de manual. Disponibilă începând cu PHP 5.3.7.


id: PHP_MAXPATHLEN
type: constant
doc:
<comment>Description:</comment>
  Lungimea maximă a numelor de fișiere (inclusiv calea) susținută de această asamblare a PHP.
  Disponibilă începând cu PHP 5.3.0.


id: PHP_MINOR_VERSION
type: constant
doc:
<comment>Description:</comment>
  Versiunea "minoră" curentă a PHP ca număr întreg (de ex. int(2) pentru versiunea "5.2.7-extra").
  Disponibilă începând cu PHP 5.2.7.


id: PHP_OS_FAMILY
type: constant
doc:
<comment>Description:</comment>
  Familia sistemului de operare pentru care PHP a fost compilat. Poate fi una din <return>'Windows'</return>, <return>'BSD'</return>,
  <return>'Darwin'</return>, <return>'Solaris'</return>, <return>'Linux'</return> or <return>'Unknown'</return>. Disponibilă începând cu PHP 7.2.0.


id: PHP_OUTPUT_HANDLER_CLEAN
type: constant
doc:
<comment>Description:</comment>
  Indică că zona-tampon de ieșire a fost curățită.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_OUTPUT_HANDLER_CLEANABLE
type: constant
doc:
<comment>Description:</comment>
  Controlează dacă o zonă-tampon de ieșire creată cu <strong>ob_start()</strong> poate fi curățată.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_OUTPUT_HANDLER_CONT
type: constant
doc:
<comment>Description:</comment>
  Indică că zona-tampon a fost descărcată, dar buferizarea ieșirilor va continua.
  
  Începând cu PHP 5.4 aceasta este un pseudonim pentru <info>PHP_OUTPUT_HANDLER_WRITE</info>.


id: PHP_OUTPUT_HANDLER_END
type: constant
doc:
<comment>Description:</comment>
  Indică că buferizarea ieșirilor s-a încheiat.
  
  Începând cu PHP 5.4 aceasta este un pseudonim pentru <info>PHP_OUTPUT_HANDLER_FINAL</info>.


id: PHP_OUTPUT_HANDLER_FINAL
type: constant
doc:
<comment>Description:</comment>
  Indică că aceasta este ultima operațiune de buferizarea a ieșirilor.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_OUTPUT_HANDLER_FLUSH
type: constant
doc:
<comment>Description:</comment>
  Indică că zona-tampon a fost descărcată.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_OUTPUT_HANDLER_FLUSHABLE
type: constant
doc:
<comment>Description:</comment>
  Controlează dacă o zonă-tampon de ieșire creată cu <strong>ob_start()</strong> poate fi descărcată.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_OUTPUT_HANDLER_REMOVABLE
type: constant
doc:
<comment>Description:</comment>
  Controlează dacă o zonă-tampon de ieșire creată cu <strong>ob_start()</strong> poate fi eliminată înainte de
  sfârșitul scriptului.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_OUTPUT_HANDLER_STDFLAGS
type: constant
doc:
<comment>Description:</comment>
  Setul implicit de fanioane a zonei-tampon de ieșire; în prezent echivalentă cu
  <info>PHP_OUTPUT_HANDLER_CLEANABLE</info> | <info>PHP_OUTPUT_HANDLER_FLUSHABLE</info> | <info>PHP_OUTPUT_HANDLER_REMOVABLE</info>.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_OUTPUT_HANDLER_WRITE
type: constant
doc:
<comment>Description:</comment>
  Indică că zona-tampon a ieșirilor a fost descărcată și au fost afișate date.
  
  Disponibilă începând cu PHP 5.4.


id: PHP_PREFIX
type: constant
doc:
<comment>Description:</comment>
  Valoarea ce a fost stabilită pentru "--prefix" la etapa de configurare.


id: PHP_QUERY_RFC1738
type: constant
doc:
<comment>Description:</comment>
  Encoding is performed per RFC 1738 and the <return>application/x-www-form-urlencoded</return> media type, which
  implies that spaces are encoded as plus (<return>+</return>) signs.


id: PHP_QUERY_RFC3986
type: constant
doc:
<comment>Description:</comment>
  Encoding is performed according to RFC 3986, and spaces will be percent encoded (<return>%20</return>).


id: PHP_RELEASE_VERSION
type: constant
doc:
<comment>Description:</comment>
  Versiunea "release" curentă a PHP ca număr întreg (de ex. int(7) pentru versiunea "5.2.7-extra").
  Disponibilă începând cu PHP 5.2.7.


id: PHP_SAPI
type: constant
doc:
<comment>Description:</comment>
  API al serverului pentru această asamblare a PHP. A se vedea și <strong>php_sapi_name()</strong>.


id: PHP_SESSION_ACTIVE
type: constant
doc:
<comment>Description:</comment>
  Since PHP 5.4.0. Return value of <strong>session_status()</strong> if sessions are enabled, and a session exists.


id: PHP_SESSION_DISABLED
type: constant
doc:
<comment>Description:</comment>
  Since PHP 5.4.0. Return value of <strong>session_status()</strong> if sessions are disabled.


id: PHP_SESSION_NONE
type: constant
doc:
<comment>Description:</comment>
  Since PHP 5.4.0. Return value of <strong>session_status()</strong> if sessions are enabled, but no session exists.


id: PHP_SHLIB_SUFFIX
type: constant
doc:
<comment>Description:</comment>
  Sufixul bibliotecilor partajate pe platforma respectivă, cum ar fi "so" (pentru majoritatea
  sistemelor Unix) sau "dll" (pentru Windows).


id: PHP_URL_FRAGMENT
type: constant
doc:
<comment>Description:</comment>
  Outputs the fragment (string after the hashmark #) of the URL parsed.


id: PHP_VERSION
type: constant
doc:
<comment>Description:</comment>
  Versiunea curentă a PHP ca șir de caractere în notarea "major.minor.release[extra]".


id: PHP_VERSION_ID
type: constant
doc:
<comment>Description:</comment>
  Versiunea curentă a PHP ca număr întreg, utilă pentru compararea versiunilor (de ex. int(50207)
  pentru versiunea "5.2.7-extra"). Disponibilă începând cu PHP 5.2.7.


id: PHP_WINDOWS_EVENT_CTRL_BREAK
type: constant
doc:
<comment>Description:</comment>
  Un eveniment <return>CTRL+BREAK</return> în Windows. Disponibil începând cu PHP 7.4.0 (doar în Windows).


id: PHP_WINDOWS_EVENT_CTRL_C
type: constant
doc:
<comment>Description:</comment>
  Un eveniment <return>CTRL+C</return> în Windows. Disponibil începând cu PHP 7.4.0 (doar în Windows).


id: PHP_WINDOWS_NT_SERVER
type: constant
doc:
<comment>Description:</comment>
  This is a server system (eg. Server 2008/2003/2000), note that if this is a  domain controller its
  reported as <info>PHP_WINDOWS_NT_DOMAIN_CONTROLLER</info>.


id: PHP_WINDOWS_VERSION_BUILD
type: constant
doc:
<comment>Description:</comment>
  The Windows build number (for example, Windows Vista with SP1 applied is build 6001)


id: PHP_WINDOWS_VERSION_MAJOR
type: constant
doc:
<comment>Description:</comment>
  The major version of Windows, this can be either <return>4</return> (NT4/Me/98/95),  <return>5</return> (XP/2003 R2/2003/2000) or <return>6</return>
  (Vista/2008/7/8/8.1).


id: PHP_WINDOWS_VERSION_MINOR
type: constant
doc:
<comment>Description:</comment>
  The minor version of Windows, this can be either <return>0</return> (Vista/2008/2000/NT4/95),  <return>1</return> (XP), <return>2</return> (2003
  R2/2003/XP x64), <return>10</return> (98)  or <return>90</return> (ME).


id: PHP_WINDOWS_VERSION_PLATFORM
type: constant
doc:
<comment>Description:</comment>
  The platform that PHP currently is running on, this value is <return>2</return> on Windows  Vista/XP/2000/NT4,
  Server 2008/2003 and on Windows ME/98/95 this value is <return>1</return>.


id: PHP_WINDOWS_VERSION_PRODUCTTYPE
type: constant
doc:
<comment>Description:</comment>
  This contains the value used to determine the <return>PHP_WINDOWS_NT_*</return> constants. This value may be one of
  the <return>PHP_WINDOWS_NT_*</return> constants  indicating the platform type.


id: PHP_WINDOWS_VERSION_SP_MAJOR
type: constant
doc:
<comment>Description:</comment>
  The major version of the service pack installed, this value is <return>0</return>  if no service pack is installed.
  For example, Windows XP with service pack 3 installed  will make this value <return>3</return>.


id: PHP_WINDOWS_VERSION_SP_MINOR
type: constant
doc:
<comment>Description:</comment>
  The minor version of the service pack installed, this value is <return>0</return>  if no service pack is installed.


id: PHP_WINDOWS_VERSION_SUITEMASK
type: constant
doc:
<comment>Description:</comment>
  The suitemask is a bitmask that can tell if various features of Windows is installed,  see the
  table below for possible bitfield values.


id: PKCS7_BINARY
type: constant
doc:
<comment>Description:</comment>
  Normally the input message is converted to "canonical" format which is effectively using <return>CR</return> and <return>LF</return>
  as end of line: as required by the S/MIME specification.  When this option is present, no
  translation occurs. This is useful when handling binary data which may not be in MIME format.


id: PKCS7_DETACHED
type: constant
doc:
<comment>Description:</comment>
  When signing a message, use cleartext signing with the MIME type <return>"multipart/signed"</return>. This is the
  default if you do not specify any <strong>$flags</strong> to <strong>openssl_pkcs7_sign()</strong>. If you turn this option off, the
  message will be signed using opaque signing, which is more resistant to translation by mail relays
  but cannot be read by mail agents that do not support S/MIME.


id: PKCS7_NOATTR
type: constant
doc:
<comment>Description:</comment>
  Normally when a message is signed, a set of attributes are included which include the signing time
  and the supported symmetric algorithms.  With this option they are not included.


id: PKCS7_NOCERTS
type: constant
doc:
<comment>Description:</comment>
  When signing a message the signer's certificate is normally included - with this option it is
  excluded.  This will reduce the size of the signed message but the verifier must have a copy of
  the signers certificate available locally (passed using the <strong>$extracerts</strong> to <strong>openssl_pkcs7_verify()</strong>
  for example).


id: PKCS7_NOCHAIN
type: constant
doc:
<comment>Description:</comment>
  Do not chain verification of signers certificates: that is don't use the certificates in the
  signed message as untrusted CAs.


id: PKCS7_NOINTERN
type: constant
doc:
<comment>Description:</comment>
  When verifying a message, certificates (if any) included in the message are normally searched for
  the signing certificate. With this option only the certificates specified in the <strong>$extracerts</strong>
  parameter of <strong>openssl_pkcs7_verify()</strong> are used.  The supplied certificates can still be used as
  untrusted CAs however.


id: PKCS7_TEXT
type: constant
doc:
<comment>Description:</comment>
  Adds text/plain content type headers to encrypted/signed message. If decrypting or verifying, it
  strips those headers from the output - if the decrypted or verified message is not of MIME type
  text/plain then an error will occur.


id: PNG_ALL_FILTERS
type: constant
doc:
<comment>Description:</comment>
  Un filtru special PNG folosit de funcția <strong>imagepng()</strong>.


id: POSIX_RLIMIT_AS
type: constant
doc:
<comment>Description:</comment>
  The maximum size of the process's address space in bytes. See also PHP's memory_limit
  configuration directive.


id: POSIX_RLIMIT_CORE
type: constant
doc:
<comment>Description:</comment>
  The maximum size of a core file. If the limit is set to 0, no core file will be generated.


id: POSIX_RLIMIT_CPU
type: constant
doc:
<comment>Description:</comment>
  The maximum amount of CPU time that the process can use, in seconds. When the soft limit is hit, a
  <return>SIGXCPU</return> signal will be sent, which can be caught with <strong>pcntl_signal()</strong>. Depending on the operating
  system, additional <return>SIGXCPU</return> signals may be sent each second until the hard limit is hit, at which
  point an uncatchable <return>SIGKILL</return> signal is sent.
  
  See also <strong>set_time_limit()</strong>.


id: POSIX_RLIMIT_DATA
type: constant
doc:
<comment>Description:</comment>
  The maximum size of the process's data segment, in bytes. It is extremely unlikely that this will
  have any effect on the execution of PHP unless an extension is in use that calls <strong>brk()</strong> or <strong>sbrk()</strong>.


id: POSIX_RLIMIT_LOCKS
type: constant
doc:
<comment>Description:</comment>
  The maximum number of locks that the process can create. This is only supported on extremely old
  Linux kernels.


id: POSIX_RLIMIT_MSGQUEUE
type: constant
doc:
<comment>Description:</comment>
  The maximum number of bytes that can be allocated for POSIX message queues. PHP does not ship with
  support for POSIX message queues, so this limit will not have any effect unless you are using an
  extension that implements that support.


id: POSIX_RLIMIT_NICE
type: constant
doc:
<comment>Description:</comment>
  The maximum value to which the process can be reniced to. The value that will be used will be <return>20 -
  limit</return>, as resource limit values cannot be negative.


id: POSIX_RLIMIT_NOFILE
type: constant
doc:
<comment>Description:</comment>
  A value one greater than the maximum file descriptor number that can be opened by this process.


id: POSIX_RLIMIT_NPROC
type: constant
doc:
<comment>Description:</comment>
  The maximum number of processes (and/or threads, on some operating systems) that can be created
  for the real user ID of the process.


id: POSIX_RLIMIT_RTPRIO
type: constant
doc:
<comment>Description:</comment>
  The maximum real time priority that can be set via the <strong>sched_setscheduler()</strong> and <strong>sched_setparam()</strong>
  system calls.


id: POSIX_RLIMIT_RTTIME
type: constant
doc:
<comment>Description:</comment>
  The maximum amount of CPU time, in microseconds, that the process can consume without making a
  blocking system call if it is using real time scheduling.


id: POSIX_RLIMIT_SIGPENDING
type: constant
doc:
<comment>Description:</comment>
  The maximum number of signals that can be queued for the real user ID of the process.


id: PREG_BACKTRACK_LIMIT_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>preg_last_error()</strong> if backtrack limit was exhausted.
  
  5.2.0


id: PREG_BAD_UTF8_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>preg_last_error()</strong> if the last error was caused by malformed UTF-8 data (only when
  running a regex in UTF-8 mode).
  
  5.2.0


id: PREG_BAD_UTF8_OFFSET_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>preg_last_error()</strong> if the offset didn't correspond to the begin of a valid UTF-8 code
  point (only when running a regex in UTF-8 mode).
  
  5.3.0


id: PREG_INTERNAL_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>preg_last_error()</strong> if there was an internal PCRE error.
  
  5.2.0


id: PREG_JIT_STACKLIMIT_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>preg_last_error()</strong> if the last PCRE function failed due to limited JIT stack space.
  
  7.0.0


id: PREG_NO_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>preg_last_error()</strong> if there were no errors.
  
  5.2.0


id: PREG_PATTERN_ORDER
type: constant
doc:
<comment>Description:</comment>
  Orders results so that $matches[0] is an array of full pattern matches, $matches[1] is an array of
  strings matched by the first parenthesized subpattern, and so on. This flag is only used with
  <strong>preg_match_all()</strong>.


id: PREG_RECURSION_LIMIT_ERROR
type: constant
doc:
<comment>Description:</comment>
  Returned by <strong>preg_last_error()</strong> if recursion limit was exhausted.
  
  5.2.0


id: PREG_SET_ORDER
type: constant
doc:
<comment>Description:</comment>
  Orders results so that $matches[0] is an array of first set of matches, $matches[1] is an array of
  second set of matches, and so on. This flag is only used with <strong>preg_match_all()</strong>.


id: PREG_SPLIT_DELIM_CAPTURE
type: constant
doc:
<comment>Description:</comment>
  This flag tells <strong>preg_split()</strong> to capture parenthesized expression in the delimiter pattern as well.


id: PREG_SPLIT_NO_EMPTY
type: constant
doc:
<comment>Description:</comment>
  This flag tells <strong>preg_split()</strong> to return only non-empty pieces.


id: PREG_SPLIT_OFFSET_CAPTURE
type: constant
doc:
<comment>Description:</comment>
  If this flag is set, for every occurring match the appendant string offset will also be returned.
  Note that this changes the return values in an array where every element is an array consisting of
  the matched string at offset 0 and its string offset within subject at offset 1. This flag is only
  used for <strong>preg_split()</strong>.


id: PREG_UNMATCHED_AS_NULL
type: constant
doc:
<comment>Description:</comment>
  This flag tells <strong>preg_match()</strong> and <strong>preg_match_all()</strong> to include unmatched subpatterns in $matches as
  <info>null</info> values. Without this flag, unmatched subpatterns are reported as empty strings, as if they
  were empty matches. Setting this flag allows to distinguish between these two cases.
  
  7.2.0


id: PSFS_ERR_FATAL
type: constant
doc:
<comment>Description:</comment>
  <return>Return Code</return> indicating that the userspace filter encountered an unrecoverable error (i.e. Invalid
  data received).


id: PSFS_FEED_ME
type: constant
doc:
<comment>Description:</comment>
  <return>Return Code</return> indicating that the userspace filter did not return buckets in <strong>$out</strong> (i.e. No data
  available).


id: PSFS_PASS_ON
type: constant
doc:
<comment>Description:</comment>
  <return>Return Code</return> indicating that the userspace filter returned buckets in <strong>$out</strong>.


id: PTHREADS_ALLOW_HEADERS
type: constant
doc:
<comment>Description:</comment>
  Allow new Threads to send headers to standard output (normally prohibited)


id: PTHREADS_INHERIT_ALL
type: constant
doc:
<comment>Description:</comment>
  The default options for all Threads, causes pthreads to copy the environment when new Threads are
  started


id: ParentIterator
type: class
doc:
<comment>Description:</comment>
  This extended <class>FilterIterator</class> allows a recursive iteration using <class>RecursiveIteratorIterator</class> that
  only shows those elements which have children.


id: ParentIterator::__construct
type: function
doc:
<comment>Description:</comment>
  Constructs a ParentIterator
  
  Constructs a <class>ParentIterator</class> on an iterator.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Param:</comment>
  <info>RecursiveIterator</info>  <strong>$iterator</strong>  The iterator being constructed upon.

<comment>Return:</comment>
  <info>unknown</info>  The <class>ParentIterator</class>.


id: ParentIterator::accept
type: function
doc:
<comment>Description:</comment>
  Determines acceptability
  
  Determines if the current element has children.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the current element is acceptable, otherwise <info>false</info>.

<comment>See Also:</comment>
   * ParentIterator::hasChildren
   * FilterIterator::accept


id: ParentIterator::getChildren
type: function
doc:
<comment>Description:</comment>
  Return the inner iterator's children contained in a ParentIterator
  
  Get the inner iterator's children contained in a ParentIterator.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>ParentIterator</info>  An <info>object</info>.


id: ParentIterator::hasChildren
type: function
doc:
<comment>Description:</comment>
  Check whether the inner iterator's current element has children
  
  Check whether the inner iterator's current element has children.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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


id: ParentIterator::next
type: function
doc:
<comment>Description:</comment>
  Move the iterator forward
  
  Moves the iterator forward.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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


id: ParentIterator::rewind
type: function
doc:
<comment>Description:</comment>
  Rewind the iterator
  
  Rewinds the iterator.
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

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


id: Parle\ErrorInfo
type: class
doc:
<comment>Description:</comment>
  The class represents detailed error information as supplied by Parle\Parser::errorInfo


id: Parle\INTERNAL_UTF32
type: constant
doc:
<comment>Description:</comment>
  Flag whether the internal UTF-32 support is compiled in. Available since parle 0.7.2.


id: Parle\Lexer
type: class
doc:
<comment>Description:</comment>
  Single state lexer class. Lexemes can be defined on the fly. If the particular lexer instance is
  meant to be used with <class>Parle\Parser</class>, the token IDs need to be taken from there. Otherwise,
  arbitrary token IDs can be supplied. This lexer can give a certain performance advantage over
  <class>Parle\RLexer</class>, if no multiple states are required. Note, that <class>Parle\RParser</class> is not compatible with
  this lexer.


id: Parle\Lexer::advance
type: function
doc:
<comment>Description:</comment>
  Process next lexer rule
  
  Processes the next rule and prepares the resulting token data.

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


id: Parle\Lexer::build
type: function
doc:
<comment>Description:</comment>
  Finalize the lexer rule set
  
  Rules, previously added with Parle\Lexer::push are finalized. This method call has to be done
  after all the necessary rules was pushed. The rule set becomes read only. The lexing can begin.

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


id: Parle\Lexer::callout
type: function
doc:
<comment>Description:</comment>
  Define token callback
  
  Define a callback to be invoked once lexer encounters a particular token.

<comment>Param:</comment>
  <info>int     </info>  <strong>$id      </strong>  Token id.
  <info>callable</info>  <strong>$callback</strong>  Callable to be invoked. The callable doesn't receive any arguments and its
                       return value is ignored.

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


id: Parle\Lexer::consume
type: function
doc:
<comment>Description:</comment>
  Pass the data for processing
  
  Consume the data for lexing.

<comment>Param:</comment>
  <info>string</info>  <strong>$data</strong>  Data to be lexed.

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


id: Parle\Lexer::dump
type: function
doc:
<comment>Description:</comment>
  Dump the state machine
  
  Dump the current state machine to stdout.

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


id: Parle\Lexer::getToken
type: function
doc:
<comment>Description:</comment>
  Retrieve the current token
  
  Retrieve the current token.

<comment>Return:</comment>
  <info>Parle\Token</info>  Returns an instance of <class>Parle\Token</class>.


id: Parle\Lexer::insertMacro
type: function
doc:
<comment>Description:</comment>
  Insert regex macro
  
  Insert a regex macro, that can be later used as a shortcut and included in other regular
  expressions.

<comment>Param:</comment>
  <info>string</info>  <strong>$name </strong>  Name of the macros.
  <info>string</info>  <strong>$regex</strong>  Regular expression.

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


id: Parle\Lexer::push
type: function
doc:
<comment>Description:</comment>
  Add a lexer rule
  
  Push a pattern for lexeme recognition.

<comment>Param:</comment>
  <info>string</info>  <strong>$regex</strong>  Regular expression used for token matching.
  <info>int   </info>  <strong>$id   </strong>  Token id. If the lexer instance is meant to be used standalone, this can be an
                  arbitrary number. If the lexer instance is going to be passed to the parser, it
                  has to be an id returned by Parle\Parser::tokenid.

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


id: Parle\Lexer::reset
type: function
doc:
<comment>Description:</comment>
  Reset lexer
  
  Reset lexing optionally supplying the desired offset.

<comment>Param:</comment>
  <info>int</info>  <strong>$pos</strong>  Reset position.

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


id: Parle\Parser
type: class
doc:
<comment>Description:</comment>
  Parser class. Rules can be defined on the fly. Once finalized, a <class>Parle\Lexer</class> instance is required
  to deliver the token stream.


id: Parle\Parser::advance
type: function
doc:
<comment>Description:</comment>
  Process next parser rule
  
  Process next parser rule.

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


id: Parle\Parser::build
type: function
doc:
<comment>Description:</comment>
  Finalize the grammar rules
  
  Any tokens and grammar rules previously added are finalized. The rule set becomes readonly and the
  parser is ready to start.

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


id: Parle\Parser::consume
type: function
doc:
<comment>Description:</comment>
  Consume the data for processing
  
  Consume the data for parsing.

<comment>Param:</comment>
  <info>string     </info>  <strong>$data </strong>  Data to be parsed.
  <info>Parle\Lexer</info>  <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular
                       grammar.

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


id: Parle\Parser::dump
type: function
doc:
<comment>Description:</comment>
  Dump the grammar
  
  Dump the current grammar to stdout.

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


id: Parle\Parser::errorInfo
type: function
doc:
<comment>Description:</comment>
  Retrieve the error information
  
  Retrieve the error information in case Parle\Parser::action returned the error action.

<comment>Return:</comment>
  <info>Parle\ErrorInfo</info>  Returns an instance of <class>Parle\ErrorInfo</class>.


id: Parle\Parser::left
type: function
doc:
<comment>Description:</comment>
  Declare a token with left-associativity
  
  Declare a terminal with left associativity.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

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


id: Parle\Parser::nonassoc
type: function
doc:
<comment>Description:</comment>
  Declare a token with no associativity
  
  Declare a terminal, that cannot appear more than once in the row.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

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


id: Parle\Parser::precedence
type: function
doc:
<comment>Description:</comment>
  Declare a precedence rule
  
  Declares a precedence rule for a fictitious terminal symbol. This rule can be later used in the
  specific grammar rules.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

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


id: Parle\Parser::push
type: function
doc:
<comment>Description:</comment>
  Add a grammar rule
  
  Push a grammar rule. The production id returned can be used later in the parsing process to
  identify the rule matched.

<comment>Param:</comment>
  <info>string</info>  <strong>$name</strong>  Rule name.
  <info>string</info>  <strong>$rule</strong>  The rule to be added. The syntax is Bison compatible.

<comment>Return:</comment>
  <info>int</info>  Returns <info>int</info> representing the rule index.


id: Parle\Parser::reset
type: function
doc:
<comment>Description:</comment>
  Reset parser state
  
  Reset parser state using the given token id.

<comment>Param:</comment>
  <info>int</info>  <strong>$tokenId</strong>  Token id.

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


id: Parle\Parser::right
type: function
doc:
<comment>Description:</comment>
  Declare a token with right-associativity
  
  Declare a terminal with right associativity.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

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


id: Parle\Parser::sigil
type: function
doc:
<comment>Description:</comment>
  Retrieve a matching part of a rule
  
  Retrieve a part of the match by a rule. This method is equivalent to the pseudo variable
  functionality in Bison.

<comment>Param:</comment>
  <info>int</info>  <strong>$idx</strong>  Match index, zero based.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> with the matched part.


id: Parle\Parser::token
type: function
doc:
<comment>Description:</comment>
  Declare a token
  
  Declare a terminal to be used in the grammar.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

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


id: Parle\Parser::tokenId
type: function
doc:
<comment>Description:</comment>
  Get token id
  
  Retrieve the id of the named token.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Name of the token as used in Parle\Parser::token.

<comment>Return:</comment>
  <info>int</info>  Returns <info>int</info> representing the token id.


id: Parle\Parser::trace
type: function
doc:
<comment>Description:</comment>
  Trace the parser operation
  
  Retrieve the current parser operation description. This can be especially useful for studying the
  parser and to optimize the grammar.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> with the trace information.


id: Parle\Parser::validate
type: function
doc:
<comment>Description:</comment>
  Validate input
  
  Validate an input string. The string is parsed internally, thus this method is useful for the
  quick input validation.

<comment>Param:</comment>
  <info>string     </info>  <strong>$data </strong>  String to be validated.
  <info>Parle\Lexer</info>  <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular
                       grammar.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>bool</info> witnessing whether the input chimes or not with the defined rules.


id: Parle\RLexer
type: class
doc:
<comment>Description:</comment>
  Multistate lexer class. Lexemes can be defined on the fly. If the particular lexer instance is
  meant to be used with <class>Parle\RParser</class>, the token IDs need to be taken from there. Otherwise,
  arbitrary token IDs can be supplied. Note, that <class>Parle\Parser</class> is not compatible with this lexer.


id: Parle\RLexer::build
type: function
doc:
<comment>Description:</comment>
  Finalize the lexer rule set
  
  Rules, previously added with Parle\RLexer::push are finalized. This method call has to be done
  after all the necessary rules was pushed. The rule set becomes read only. The lexing can begin.

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


id: Parle\RLexer::getToken
type: function
doc:
<comment>Description:</comment>
  Retrieve the current token
  
  Retrive the current token.

<comment>Return:</comment>
  <info>Parle\Token</info>  Returns an instance of <class>Parle\Token</class>.


id: Parle\RLexer::push
type: function
doc:
<comment>Description:</comment>
  Add a lexer rule
  
  Push a pattern for lexeme recognition.
  
  A 'start state' and 'exit state' can be specified by using a suitable signature.

<comment>Param:</comment>
  <info>string</info>  <strong>$regex   </strong>  Regular expression used for token matching.
  <info>int   </info>  <strong>$id      </strong>  Token id. If the lexer instance is meant to be used standalone, this can be an
                     arbitrary number. If the lexer instance is going to be passed to the parser, it
                     has to be an id returned by Parle\RParser::tokenid.
  <info>string</info>  <strong>$state   </strong>  State name. If '*' is used as start state, then the rule is applied to all
                     lexer states.
  <info>string</info>  <strong>$newState</strong>  New state name, after the rule was applied.
                     
                     If '.' is specified as the exit state, then the lexer state is unchanged when
                     that rule matches. An exit state with '&gt;' before the name means push. Use
                     the signature without id for either continuation or to start matching, when a
                     continuation or recursion is required.
                     
                     If '\<' is specified as exit state, it means pop. In that case, the signature containing the id can be used to identify the match. Note that even in the case an id is specified, the rule will finish first when all the previous pushes popped.

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


id: Parle\RLexer::pushState
type: function
doc:
<comment>Description:</comment>
  Push a new start state
  
  This lexer type can have more than one state machine. This allows you to lex different tokens
  depending on context, thus allowing simple parsing to take place. Once a state pushed, it can be
  used with a suitable Parle\RLexer::push signature variant.

<comment>Param:</comment>
  <info>string</info>  <strong>$state</strong>  Name of the state.

<comment>Return:</comment>
  <info>int</info>  


id: Parle\RParser
type: class
doc:
<comment>Description:</comment>
  Parser class. Rules can be defined on the fly. Once finalized, a <class>Parle\RLexer</class> instance is required
  to deliver the token stream.


id: Parle\RParser::advance
type: function
doc:
<comment>Description:</comment>
  Process next parser rule
  
  Prosess next parser rule.

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


id: Parle\RParser::consume
type: function
doc:
<comment>Description:</comment>
  Consume the data for processing
  
  Consume the data for parsing.

<comment>Param:</comment>
  <info>string</info>  <strong>$data </strong>  Data to be parsed.
  <info>      </info>  <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular grammar.

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


id: Parle\RParser::errorInfo
type: function
doc:
<comment>Description:</comment>
  Retrieve the error information
  
  Retrieve the error information in case Parle\RParser::action returned the error action.

<comment>Return:</comment>
  <info>Parle\ErrorInfo</info>  Returns an instance of <class>Parle\ErrorInfo</class>.


id: Parle\RParser::precedence
type: function
doc:
<comment>Description:</comment>
  Declare a precedence rule
  
  Declares a precedence rule for a fictious terminal symbol. This rule can be later used in the
  specific grammar rules.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Token name.

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


id: Parle\RParser::tokenId
type: function
doc:
<comment>Description:</comment>
  Get token id
  
  Retrieve the id of the named token.

<comment>Param:</comment>
  <info>string</info>  <strong>$tok</strong>  Name of the token as used in Parle\RParser::token.

<comment>Return:</comment>
  <info>int</info>  Returns <info>int</info> representing the token id.


id: Parle\RParser::trace
type: function
doc:
<comment>Description:</comment>
  Trace the parser operation
  
  Retrieve the current parser operation description. This can be especially useful to study the
  parser and to optimize the grammar.

<comment>Return:</comment>
  <info>string</info>  Returns a <info>string</info> with the trace information.


id: Parle\RParser::validate
type: function
doc:
<comment>Description:</comment>
  Validate input
  
  Validate an input string. The string is parsed internally, thus this method is useful for the
  quick input validation.

<comment>Param:</comment>
  <info>string      </info>  <strong>$data </strong>  String to be validated.
  <info>Parle\RLexer</info>  <strong>$lexer</strong>  A lexer object containing the lexing rules prepared for the particular
                        grammar.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>bool</info> whitnessing whether the input chimes or not with the defined rules.


id: Parle\Stack
type: class
doc:
<comment>Description:</comment>
  <class>Parle\Stack</class> is a LIFO stack. The elements are inserted and removed only from one end.


id: Parle\Stack::pop
type: function
doc:
<comment>Description:</comment>
  Pop an item from the stack

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


id: Parle\Stack::push
type: function
doc:
<comment>Description:</comment>
  Push an item into the stack

<comment>Param:</comment>
  <info>mixed</info>  <strong>$item</strong>  Variable to be pushed.

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


id: Parle\Token
type: class
doc:
<comment>Description:</comment>
  This class represents a token. Lexer returns instances of this class.


id: Phar
type: class
doc:
<comment>Description:</comment>
  The Phar class provides a high-level interface to accessing and creating phar archives.


id: Phar::COMPRESSED
type: constant
doc:
<comment>Description:</comment>
  0x0000F000
  
  bitmask that can be used with file flags to determine if any compression is present


id: Phar::OPENSSL
type: constant
doc:
<comment>Description:</comment>
  signature with OpenSSL public/private key pair.  This is a true, asymmetric key signature.


id: Phar::PHP
type: constant
doc:
<comment>Description:</comment>
  used to instruct the mimeoverrides parameter of <strong>Phar::webPhar()</strong> that the extension should be
  parsed as a PHP file


id: Phar::PHPS
type: constant
doc:
<comment>Description:</comment>
  used to instruct the mimeoverrides parameter of <strong>Phar::webPhar()</strong> that the extension should be
  parsed as a PHP source file through <strong>highlight_file()</strong>


id: Phar::__construct
type: function
doc:
<comment>Description:</comment>
  Construct a Phar archive object

<comment>Param:</comment>
  <info>string</info>  <strong>$fname</strong>  Path to an existing Phar archive or to-be-created archive. The file name's
                  extension must contain .phar.
  <info>int   </info>  <strong>$flags</strong>  Flags to pass to parent class <class>RecursiveDirectoryIterator</class>.
  <info>string</info>  <strong>$alias</strong>  Alias with which this Phar archive should be referred to in calls to stream
                  functionality.


id: Phar::addEmptyDir
type: function
doc:
<comment>Description:</comment>
  Add an empty directory to the phar archive
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  With this method, an empty directory is created with path <return>dirname</return>. This method is similar to
  <strong>ZipArchive::addEmptyDir()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$dirname</strong>  The name of the empty directory to create in the phar archive

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>PharData::addEmptyDir()</strong>
   * <strong>Phar::addFile()</strong>
   * <strong>Phar::addFromString()</strong>


id: Phar::addFile
type: function
doc:
<comment>Description:</comment>
  Add a file from the filesystem to the phar archive
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  With this method, any file or URL can be added to the phar archive.  If the optional second
  parameter <return>localname</return> is specified, the file will be stored in the archive with that name, otherwise
  the <return>file</return> parameter is used as the path to store within the archive.  URLs must have a localname or
  an exception is thrown. This method is similar to <strong>ZipArchive::addFile()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$file     </strong>  Full or relative path to a file on disk to be added to the phar archive.
  <info>string</info>  <strong>$localname</strong>  Path that the file will be stored in the archive.

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>Phar::offsetSet()</strong>
   * <strong>PharData::addFile()</strong>
   * <strong>Phar::addFromString()</strong>
   * <strong>Phar::addEmptyDir()</strong>


id: Phar::addFromString
type: function
doc:
<comment>Description:</comment>
  Add a file from a string to the phar archive
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  With this method, any string can be added to the phar archive. The file will be stored in the
  archive with <return>localname</return> as its path.  This method is similar to <strong>ZipArchive::addFromString()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$localname</strong>  Path that the file will be stored in the archive.
  <info>string</info>  <strong>$contents </strong>  The file contents to store

<comment>Return:</comment>
  <info>void</info>  no return value, exception is thrown on failure.

<comment>See Also:</comment>
   * <strong>Phar::offsetSet()</strong>
   * <strong>PharData::addFromString()</strong>
   * <strong>Phar::addFile()</strong>
   * <strong>Phar::addEmptyDir()</strong>


id: Phar::apiVersion
type: function
doc:
<comment>Description:</comment>
  Returns the api version
  
  Return the API version of the phar file format that will be used when creating phars.  The Phar
  extension supports reading API version 1.0.0 or newer.  API version 1.1.0 is required for SHA-256
  and SHA-512 hash, and API version 1.1.1 is required to store empty directories.

<comment>Return:</comment>
  <info>string</info>  The API version string as in <return>"1.0.0"</return>.


id: Phar::buildFromDirectory
type: function
doc:
<comment>Description:</comment>
  Construct a phar archive from the files within a directory
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  Populate a phar archive from directory contents.  The optional second parameter is a regular
  expression (pcre) that is used to exclude files. Any filename that matches the regular expression
  will be included, all others will be excluded.  For more fine-grained control, use
  <strong>Phar::buildFromIterator()</strong>.

<comment>Param:</comment>
  <info>string</info>  <strong>$base_dir</strong>  The full or relative path to the directory that contains all files to add to
                     the archive.
  <info>string</info>  <strong>$regex   </strong>  An optional pcre regular expression that is used to filter the list of files.
                     Only file paths matching the regular expression will be included in the
                     archive.

<comment>Return:</comment>
  <info>array</info>  <strong>Phar::buildFromDirectory()</strong> returns an associative array mapping internal path of file to
         the full path of the file on the filesystem.

<comment>See Also:</comment>
   * <strong>Phar::buildFromIterator()</strong>


id: Phar::buildFromIterator
type: function
doc:
<comment>Description:</comment>
  Construct a phar archive from an iterator
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  Populate a phar archive from an iterator.  Two styles of iterators are supported, iterators that
  map the filename within the phar to the name of a file on disk, and iterators like
  DirectoryIterator that return SplFileInfo objects.  For iterators that return SplFileInfo objects,
  the second parameter is required.

<comment>Param:</comment>
  <info>Iterator</info>  <strong>$iter          </strong>  Any iterator that either associatively maps phar file to location or
                             returns SplFileInfo objects
  <info>string  </info>  <strong>$base_directory</strong>  For iterators that return SplFileInfo objects, the portion of each
                             file's full path to remove when adding to the phar archive

<comment>Return:</comment>
  <info>array</info>  <strong>Phar::buildFromIterator()</strong> returns an associative array mapping internal path of file to the
         full path of the file on the filesystem.

<comment>See Also:</comment>
   * <strong>Phar::buildFromDirectory()</strong>


id: Phar::canCompress
type: function
doc:
<comment>Description:</comment>
  Returns whether phar extension supports compression using either zlib or bzip2
  
  This should be used to test whether compression is possible prior to loading a phar archive
  containing compressed files.

<comment>Param:</comment>
  <info>int</info>  <strong>$type</strong>  Either <return>Phar::GZ</return> or <return>Phar::BZ2</return> can be used to test whether compression is possible with
              a specific compression algorithm (zlib or bzip2).

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if compression/decompression is available, <info>false</info> if not.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>Phar::convertToData()</strong>


id: Phar::canWrite
type: function
doc:
<comment>Description:</comment>
  Returns whether phar extension supports writing and creating phars
  
  This static method determines whether write access has been disabled in the system php.ini via the
  phar.readonly ini variable.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if write access is enabled, <info>false</info> if it is disabled.

<comment>See Also:</comment>
   * phar.readonly
   * <strong>Phar::isWritable()</strong>


id: Phar::compress
type: function
doc:
<comment>Description:</comment>
  Compresses the entire Phar archive using Gzip or Bzip2 compression
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  For tar-based and phar-based phar archives, this method compresses the entire archive using gzip
  compression or bzip2 compression.  The resulting file can be processed with the gunzip
  command/bunzip command, or accessed directly and transparently with the Phar extension.
  
  For Zip-based phar archives, this method fails with an exception. The zlib extension must be
  enabled to compress with gzip compression, the bzip2 extension must be enabled in order to
  compress with bzip2 compression. As with all functionality that modifies the contents of a phar,
  the phar.readonly INI variable must be off in order to succeed.
  
  In addition, this method automatically renames the archive, appending <return>.gz</return>, <return>.bz2</return> or removing the
  extension if passed <return>Phar::NONE</return> to remove compression.  Alternatively, a file extension may be
  specified with the second parameter.

<comment>Param:</comment>
  <info>int   </info>  <strong>$compression</strong>  Compression must be one of <return>Phar::GZ</return>, <return>Phar::BZ2</return> to add compression, or
                        <return>Phar::NONE</return> to remove compression.
  <info>string</info>  <strong>$extension  </strong>  By default, the extension is <return>.phar.gz</return> or <return>.phar.bz2</return> for compressing phar
                        archives, and <return>.phar.tar.gz</return> or <return>.phar.tar.bz2</return> for compressing tar archives.
                        For decompressing, the default file extensions are <return>.phar</return> and <return>.phar.tar</return>.

<comment>Return:</comment>
  <info>Phar</info>  Returns a <class>Phar</class> object.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>


id: Phar::compressFiles
type: function
doc:
<comment>Description:</comment>
  Compresses all files in the current Phar archive
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  For tar-based phar archives, this method throws a <class>BadMethodCallException</class>, as compression of
  individual files within a tar archive is not supported by the file format.  Use <strong>Phar::compress()</strong>
  to compress an entire tar-based phar archive.
  
  For Zip-based and phar-based phar archives, this method compresses all files in the Phar archive
  using the specified compression. The zlib  or bzip2 extensions must be enabled to take advantage
  of this feature.  In addition, if any files are already compressed using bzip2/zlib compression,
  the respective extension must be enabled in order to decompress the files prior to re-compressing.
  As with all functionality that modifies the contents of a phar, the phar.readonly INI variable
  must be off in order to succeed.

<comment>Param:</comment>
  <info>int</info>  <strong>$compression</strong>  Compression must be one of <return>Phar::GZ</return>, <return>Phar::BZ2</return> to add compression, or
                     <return>Phar::NONE</return> to remove compression.

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

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>


id: Phar::convertToData
type: function
doc:
<comment>Description:</comment>
  Convert a phar archive to a non-executable tar or zip file
  
  This method is used to convert an executable phar archive to either a tar or zip file.  To make
  the tar or zip non-executable, the phar stub and phar alias files are removed from the newly
  created archive.
  
  If no changes are specified, this method throws a <class>BadMethodCallException</class> if the archive is in phar
  file format.  For archives in tar or zip file format, this method converts the archive to a
  non-executable archive.
  
  If successful, the method creates a new archive on disk and returns a <class>PharData</class> object.  The old
  archive is not removed from disk, and should be done manually after the process has finished.

<comment>Param:</comment>
  <info>int   </info>  <strong>$format     </strong>  This should be one of <return>Phar::TAR</return> or <return>Phar::ZIP</return>.  If set to <info>null</info>, the existing
                        file format will be preserved.
  <info>int   </info>  <strong>$compression</strong>  This should be one of <return>Phar::NONE</return> for no whole-archive compression, <return>Phar::GZ</return>
                        for zlib-based compression, and <return>Phar::BZ2</return> for bzip-based compression.
  <info>string</info>  <strong>$extension  </strong>  This parameter is used to override the default file extension for a
                        converted archive.  Note that <return>.phar</return> cannot be used anywhere in the filename
                        for a non-executable tar or zip archive.
                        
                        If converting to a tar-based phar archive, the default extensions are <return>.tar</return>,
                        <return>.tar.gz</return>, and <return>.tar.bz2</return> depending on specified compression. For zip-based
                        archives, the default extension is <return>.zip</return>.

<comment>Return:</comment>
  <info>PharData</info>  The method returns a <class>PharData</class> object on success and throws an exception on failure.

<comment>See Also:</comment>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>PharData::convertToExecutable()</strong>
   * <strong>PharData::convertToData()</strong>


id: Phar::convertToExecutable
type: function
doc:
<comment>Description:</comment>
  Convert a phar archive to another executable phar archive file format
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  This method is used to convert a phar archive to another file format.  For instance, it can be
  used to create a tar-based executable phar archive from a zip-based executable phar archive, or
  from an executable phar archive in the phar file format.  In addition, it can be used to apply
  whole-archive compression to a tar or phar-based archive.
  
  If no changes are specified, this method throws a <class>BadMethodCallException</class>.
  
  If successful, the method creates a new archive on disk and returns a <class>Phar</class> object.  The old
  archive is not removed from disk, and should be done manually after the process has finished.

<comment>Param:</comment>
  <info>int   </info>  <strong>$format     </strong>  This should be one of <return>Phar::PHAR</return>, <return>Phar::TAR</return>, or <return>Phar::ZIP</return>.  If set to <info>null</info>,
                        the existing file format will be preserved.
  <info>int   </info>  <strong>$compression</strong>  This should be one of <return>Phar::NONE</return> for no whole-archive compression, <return>Phar::GZ</return>
                        for zlib-based compression, and <return>Phar::BZ2</return> for bzip-based compression.
  <info>string</info>  <strong>$extension  </strong>  This parameter is used to override the default file extension for a
                        converted archive.  Note that all zip- and tar-based phar archives must
                        contain <return>.phar</return> in their file extension in order to be processed as a phar
                        archive.
                        
                        If converting to a phar-based archive, the default extensions are <return>.phar</return>,
                        <return>.phar.gz</return>, or <return>.phar.bz2</return> depending on the specified compression.  For
                        tar-based phar archives, the default extensions are <return>.phar.tar</return>, <return>.phar.tar.gz</return>,
                        and <return>.phar.tar.bz2</return>.  For zip-based phar archives, the default extension is
                        <return>.phar.zip</return>.

<comment>Return:</comment>
  <info>Phar</info>  The method returns a <class>Phar</class> object on success and throws an exception on failure.

<comment>See Also:</comment>
   * <strong>Phar::convertToData()</strong>
   * <strong>PharData::convertToExecutable()</strong>
   * <strong>PharData::convertToData()</strong>


id: Phar::copy
type: function
doc:
<comment>Description:</comment>
  Copy a file internal to the phar archive to another new file within the phar
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  Copy a file internal to the phar archive to another new file within the phar. This is an
  object-oriented alternative to using <strong>copy()</strong> with the phar stream wrapper.

<comment>Param:</comment>
  <info>string</info>  <strong>$oldfile</strong>  
  <info>string</info>  <strong>$newfile</strong>  

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is safer to encase method call in a try/catch block and
        assume success if no exception is thrown.


id: Phar::count
type: function
doc:
<comment>Description:</comment>
  Returns the number of entries (files) in the Phar archive

<comment>Return:</comment>
  <info>int</info>  The number of files contained within this phar, or <return>0</return> (the number zero) if none.


id: Phar::createDefaultStub
type: function
doc:
<comment>Description:</comment>
  Create a phar-file format specific stub
  
  This method is intended for creation of phar-file format-specific stubs, and is not intended for
  use with tar- or zip-based phar archives.
  
  Phar archives contain a bootstrap loader, or <return>stub</return> written in PHP that is executed when the archive
  is executed in PHP either via include:  ]]> or by simple execution:
  
  This method provides a simple and easy method to create a stub that will run a startup file from
  the phar archive.  In addition, different files can be specified for running the phar archive from
  the command line versus through a web server.  The loader stub also calls
  <strong>Phar::interceptFileFuncs()</strong> to allow easy bundling of a PHP application that accesses the file
  system.  If the phar extension is not present, the loader stub will extract the phar archive to a
  temporary directory and then operate on the files.  A shutdown function erases the temporary files
  on exit.

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the contents of a customized bootstrap loader (stub) that
          allows the created Phar archive to work with or without the Phar extension enabled.

<comment>See Also:</comment>
   * <strong>Phar::setStub()</strong>
   * <strong>Phar::getStub()</strong>


id: Phar::decompress
type: function
doc:
<comment>Description:</comment>
  Decompresses the entire Phar archive
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  For tar-based and phar-based phar archives, this method decompresses the entire archive.
  
  For Zip-based phar archives, this method fails with an exception. The zlib extension must be
  enabled to decompress an archive compressed with gzip compression, and the bzip2 extension must be
  enabled in order to decompress an archive compressed with bzip2 compression. As with all
  functionality that modifies the contents of a phar, the phar.readonly INI variable must be off in
  order to succeed.
  
  In addition, this method automatically changes the file extension of the archive, <return>.phar</return> by default
  for phar archives, or <return>.phar.tar</return> for tar-based phar archives. Alternatively, a file extension may
  be specified with the second parameter.

<comment>Param:</comment>
  <info>string</info>  <strong>$extension</strong>  For decompressing, the default file extensions are <return>.phar</return> and <return>.phar.tar</return>. Use
                      this parameter to specify another file extension.  Be aware that all
                      executable phar archives must contain <return>.phar</return> in their filename.

<comment>Return:</comment>
  <info>Phar</info>  A <class>Phar</class> object is returned.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharData::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>


id: Phar::decompressFiles
type: function
doc:
<comment>Description:</comment>
  Decompresses all files in the current Phar archive
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  For tar-based phar archives, this method throws a <class>BadMethodCallException</class>, as compression of
  individual files within a tar archive is not supported by the file format.  Use <strong>Phar::compress()</strong>
  to compress an entire tar-based phar archive.
  
  For Zip-based and phar-based phar archives, this method decompresses all files in the Phar
  archive. The zlib  or bzip2 extensions must be enabled to take advantage of this feature if any
  files are compressed using bzip2/zlib compression. As with all functionality that modifies the
  contents of a phar, the phar.readonly INI variable must be off in order to succeed.

<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>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>


id: Phar::delMetadata
type: function
doc:
<comment>Description:</comment>
  Deletes the global metadata of the phar
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  Deletes the global metadata of the phar

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>Phar::getMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>


id: Phar::delete
type: function
doc:
<comment>Description:</comment>
  Delete a file within a phar archive
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  Delete a file within an archive.  This is the functional equivalent of calling <strong>unlink()</strong> on the
  stream wrapper equivalent, as shown in the example below.

<comment>Param:</comment>
  <info>string</info>  <strong>$entry</strong>  Path within an archive to the file to delete.

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>PharData::delete()</strong>
   * <strong>Phar::unlinkArchive()</strong>


id: Phar::extractTo
type: function
doc:
<comment>Description:</comment>
  Extract the contents of a phar archive to a directory
  
  Extract all files within a phar archive to disk.  Extracted files and directories preserve
  permissions as stored in the archive.  The optional parameters allow optional control over which
  files are extracted, and whether existing files on disk can be overwritten. The second parameter
  <strong>$files</strong> can be either the name of a file or directory to extract, or an array of names of files and
  directories to extract.  By default, this method will not overwrite existing files, the third
  parameter can be set to true to enable overwriting of files. This method is similar to
  <strong>ZipArchive::extractTo()</strong>.

<comment>Param:</comment>
  <info>string         </info>  <strong>$pathto   </strong>  Path to extract the given <strong>$files</strong> to
  <info>stringarraynull</info>  <strong>$files    </strong>  The name of a file or directory to extract, or an array of
                               files/directories to extract, <info>null</info> to skip this param
  <info>bool           </info>  <strong>$overwrite</strong>  Set to <info>true</info> to enable overwriting existing files

<comment>Return:</comment>
  <info>bool</info>  returns <info>true</info> on success, but it is better to check for thrown exception, and assume success
        if none is thrown.

<comment>See Also:</comment>
   * <strong>PharData::extractTo()</strong>


id: Phar::getAlias
type: function
doc:
<comment>Description:</comment>
  Get the alias for Phar
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>string</info>  Returns the alias or <info>null</info> if there's no alias.


id: Phar::getMetadata
type: function
doc:
<comment>Description:</comment>
  Returns phar archive meta-data
  
  Retrieve archive meta-data.  Meta-data can be any PHP variable that can be serialized.

<comment>Return:</comment>
  <info>mixed</info>  any PHP variable that can be serialized and is stored as meta-data for the Phar archive, or
         <info>null</info> if no meta-data is stored.

<comment>See Also:</comment>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::delMetadata()</strong>
   * <strong>Phar::hasMetadata()</strong>


id: Phar::getModified
type: function
doc:
<comment>Description:</comment>
  Return whether phar was modified
  
  This method can be used to determine whether a phar has either had an internal file deleted, or
  contents of a file changed in some way.

<comment>Return:</comment>
  <info>bool</info>  <info>true</info> if the phar has been modified since opened, <info>false</info> if not.


id: Phar::getPath
type: function
doc:
<comment>Description:</comment>
  Get the real path to the Phar archive on disk
  
  Această funcție nu este documentată în prezent; este disponibilă numai
  lista sa de argumente.

<comment>Return:</comment>
  <info>string</info>  


id: Phar::getSignature
type: function
doc:
<comment>Description:</comment>
  Return MD5/SHA1/SHA256/SHA512/OpenSSL signature of a Phar archive
  
  Returns the verification signature of a phar archive in a hexadecimal string.

<comment>Return:</comment>
  <info>array</info>  Array with the opened archive's signature in <return>hash</return> key and <return>MD5</return>, <return>SHA-1</return>, <return>SHA-256</return>, <return>SHA-512</return>, or
         <return>OpenSSL</return> in <return>hash_type</return>.  This signature is a hash calculated on the entire phar's contents,
         and may be used to verify the integrity of the archive. A valid signature is absolutely
         required of all executable phar archives if the phar.require_hash INI variable is set to
         true.


id: Phar::getStub
type: function
doc:
<comment>Description:</comment>
  Return the PHP loader or bootstrap stub of a Phar archive
  
  Phar archives contain a bootstrap loader, or <return>stub</return> written in PHP that is executed when the archive
  is executed in PHP either via include:  ]]> or by simple execution:

<comment>Return:</comment>
  <info>string</info>  Returns a string containing the contents of the bootstrap loader (stub) of the current
          Phar archive.

<comment>See Also:</comment>
   * <strong>Phar::setStub()</strong>
   * <strong>Phar::createDefaultStub()</strong>


id: Phar::getSupportedCompression
type: function
doc:
<comment>Description:</comment>
  Return array of supported compression algorithms

<comment>Return:</comment>
  <info>array</info>  Returns an array containing any of <return>Phar::GZ</return> or <return>Phar::BZ2</return>, depending on the availability of
         the zlib extension or the bz2 extension.

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::isCompressed()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>


id: Phar::getSupportedSignatures
type: function
doc:
<comment>Description:</comment>
  Return array of supported signature types
  
  Return array of supported signature types

<comment>Return:</comment>
  <info>array</info>  Returns an array containing any of <return>MD5</return>, <return>SHA-1</return>, <return>SHA-256</return>, <return>SHA-512</return>, or <return>OpenSSL</return>.

<comment>See Also:</comment>
   * <strong>Phar::getSignature()</strong>
   * <strong>Phar::setSignatureAlgorithm()</strong>


id: Phar::getVersion
type: function
doc:
<comment>Description:</comment>
  Return version info of Phar archive
  
  Returns the API version of an opened Phar archive.

<comment>Return:</comment>
  <info>string</info>  The opened archive's API version.  This is not to be confused with the API version that
          the loaded phar extension will use to create new phars.  Each Phar archive has the API
          version hard-coded into its manifest.  See Phar file format documentation for more
          information.

<comment>See Also:</comment>
   * <strong>Phar::apiVersion()</strong>


id: Phar::hasMetadata
type: function
doc:
<comment>Description:</comment>
  Returns whether phar has global meta-data
  
  Returns whether phar has global meta-data set.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if meta-data has been set, and <info>false</info> if not.

<comment>See Also:</comment>
   * <strong>Phar::getMetadata()</strong>
   * <strong>Phar::setMetadata()</strong>
   * <strong>Phar::delMetadata()</strong>


id: Phar::interceptFileFuncs
type: function
doc:
<comment>Description:</comment>
  Instructs phar to intercept fopen, file_get_contents, opendir, and all of the stat-related
  functions
  
  instructs phar to intercept <strong>fopen()</strong>, <strong>readfile()</strong>, <strong>file_get_contents()</strong>, <strong>opendir()</strong>, and all of the
  stat-related functions.  If any of these functions is called from within a phar archive with a
  relative path, the call is modified to access a file within the phar archive.  Absolute paths are
  assumed to be attempts to load external files from the filesystem.
  
  This function makes it possible to run PHP applications designed to run off of a hard disk as a
  phar application.

<comment>Return:</comment>
  <info>void</info>  


id: Phar::isBuffering
type: function
doc:
<comment>Description:</comment>
  Used to determine whether Phar write operations are being buffered, or are flushing directly to
  disk
  
  This method can be used to determine whether a Phar will save changes to disk immediately, or
  whether a call to <strong>Phar::stopBuffering()</strong> is needed to enable saving changes.
  
  Phar write buffering is per-archive, buffering active for the <return>foo.phar</return> Phar archive does not
  affect changes to the <return>bar.phar</return> Phar archive.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the write operations are being buffer, <info>false</info> otherwise.

<comment>See Also:</comment>
   * <strong>Phar::startBuffering()</strong>
   * <strong>Phar::stopBuffering()</strong>


id: Phar::isCompressed
type: function
doc:
<comment>Description:</comment>
  Returns Phar::GZ or PHAR::BZ2 if the entire phar archive is compressed (.tar.gz/tar.bz and so on)
  
  Această metodă necesită ca parametrul php.ini <return>phar.readonly</return> să fie stabilit în <return>0</return> pentru ca
  obiectele <class>Phar</class> să funcționeze. În caz contrar va fi emisă o excepție <class>PharException</class>.
  
  Returns Phar::GZ or PHAR::BZ2 if the entire phar archive is compressed (.tar.gz/tar.bz and so on).
  Zip-based phar archives cannot be compressed as a file, and so this method will always return
  <info>false</info> if a zip-based phar archive is queried.

<comment>Return:</comment>
  <info>mixed</info>  <return>Phar::GZ</return>, <return>Phar::BZ2</return> or <info>false</info>

<comment>See Also:</comment>
   * <strong>PharFileInfo::getCompressedSize()</strong>
   * <strong>PharFileInfo::isCompressed()</strong>
   * <strong>PharFileInfo::decompress()</strong>
   * <strong>PharFileInfo::compress()</strong>
   * <strong>Phar::decompress()</strong>
   * <strong>Phar::compress()</strong>
   * <strong>Phar::canCompress()</strong>
   * <strong>Phar::compressFiles()</strong>
   * <strong>Phar::decompressFiles()</strong>
   * <strong>Phar::getSupportedCompression()</strong>


id: Phar::isFileFormat
type: function
doc:
<comment>Description:</comment>
  Returns true if the phar archive is based on the tar/phar/zip file format depending on the
  parameter

<comment>Param:</comment>
  <info>int</info>  <strong>$format</strong>  Either <return>Phar::PHAR</return>, <return>Phar::TAR</return>, or <return>Phar::ZIP</return> to test for the format of the archive.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the phar archive matches the file format requested by the parameter

<comment>See Also:</comment>
   * <strong>Phar::convertToExecutable()</strong>
   * <strong>Phar::convertToData()</strong>


id: Phar::isValidPharFilename
type: function
doc:
<comment>Description:</comment>
  Returns whether the given filename is a valid phar filename
  
  Returns whether the given filename is a valid phar filename that will be recognized as a phar
  archive by the phar extension.  This can be used to test a name without having to instantiate a
  phar archive and catch the inevitable Exception that will be thrown if an invalid name is
  specified.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename  </strong>  The name or full path to a phar archive not yet created
  <info>bool  </info>  <strong>$executable</strong>  This parameter determines whether the filename should be treated as a phar
                       executable archive, or a data non-executable archive

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the filename is valid, <info>false</info> if not.


id: Phar::isWritable
type: function
doc:
<comment>Description:</comment>
  Returns true if the phar archive can be modified
  
  This method returns <info>true</info> if <return>phar.readonly</return> is <return>0</return>, and the actual phar archive on disk is not
  read-only.

<comment>Return:</comment>
  <info>bool</info>  Returns <info>true</info> if the phar archive can be modified

<comment>See Also:</comment>
   * <strong>Phar::canWrite()</strong>
   * <strong>PharData::isWritable()</strong>


id: Phar::loadPhar
type: function
doc:
<comment>Description:</comment>
  Loads any phar archive with an alias
  
  This can be used to read the contents of an external Phar archive.  This is most useful for
  assigning an alias to a phar so that subsequent references to the phar can use the shorter alias,
  or for loading Phar archives that only contain data and are not intended for execution/inclusion
  in PHP scripts.

<comment>Param:</comment>
  <info>string</info>  <strong>$filename</strong>  the full or relative path to the phar archive to open
  <info>string</info>  <strong>$alias   </strong>  The alias that may be used to refer to the phar archive.  Note that many phar
                     archives specify an explicit alias inside the phar archive, and a <class>PharException</class>
                     will be thrown if a new alias is specified in this case.

<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>Phar::mapPhar()</strong>


id: Phar::mapPhar
type: function
doc:
<comment>Description:</comment>
  Reads the currently executed file (a phar) and registers its manifest
  
  This static method can only be used inside a Phar archive's loader stub in order to initialize the
  phar when it is directly executed, or when it is included in another script.

<comment>Param:</comment>
  <info>string</info>  <strong>$alias     </strong>  The alias that can be used in <return>phar://</return> URLs to refer to this archive, rather
                       than its full path.
  <info>int   </info>  <strong>$dataoffset</strong>  Unused variable, here for compatibility with PEAR's PHP_Archive.

<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>Phar::loadPhar()</strong>


