sqlite_open(3) [php man page]

SQLITE_OPEN(3)															    SQLITE_OPEN(3)

sqlite_open - Opens an SQLite database and create the database if it does not exist

SYNOPSIS

       resource sqlite_open (string  $filename, [int  $mode = 0666], [string  &$error_message])

DESCRIPTION

       Object oriented style (constructor): SQLiteDatabase::__construct (string  $filename, [int  $mode = 0666], [string  &$error_message])

	Opens an SQLite database or creates the database if it does not exist.

PARAMETERS

	      o $filename
		-  The	filename of the SQLite database. If the file does not exist, SQLite will attempt to create it. PHP must have write permis-
		sions to the file if data is inserted, the database schema is modified or to create the database if it does not exist.

	      o $mode
		- The mode of the file. Intended to be used to open the database in read-only mode. Presently, this parameter is  ignored  by  the
		sqlite library. The default value for mode is the octal value 0666 and this is the recommended value.

	      o $error_message
		-  Passed by reference and is set to hold a descriptive error message explaining why the database could not be opened if there was
		an error.

RETURN VALUES

	Returns a resource (database handle) on success, FALSE on error.

EXAMPLES

       Example #1

	      sqlite_open(3) example

	      <?php
	      if ($db = sqlite_open('mysqlitedb', 0666, $sqliteerror)) {
		  sqlite_query($db, 'CREATE TABLE foo (bar varchar(10))');
		  sqlite_query($db, "INSERT INTO foo VALUES ('fnord')");
		  $result = sqlite_query($db, 'select bar from foo');
		  var_dump(sqlite_fetch_array($result));
	      } else {
		  die($sqliteerror);
	      }
	      ?>

NOTES

       Tip

	       On Unix platforms, SQLite is sensitive to scripts that use the fork() system call. If you do have such a script, it is  recommended
	      that  you  close the handle prior to forking and then re-open it in the child and/or parent. For more information on this issue, see
	      The C language interface to the SQLite library in the section entitled Multi-Threading And SQLite.

       Tip

	       It is not recommended to work with SQLite databases mounted on NFS partitions. Since NFS is notoriously bad when it comes to  lock-
	      ing you may find that you cannot even open the database at all, and if it succeeds, the locking behaviour may be undefined.

       Note

	       Starting  with  SQLite library version 2.8.2, you can specify :memory: as the $filename to create a database that lives only in the
	      memory of the computer. This is useful mostly for temporary processing, as the in-memory database will be destroyed when the process
	      ends.  It  can  also  be	useful when coupled with the ATTACH DATABASE SQL statement to load other databases and move and query data
	      between them.

       Note

	       SQLite is safe mode and open_basedir aware.

SEE ALSO

       sqlite_popen(3), sqlite_close(3), sqlite_factory(3).

PHP Documentation Group 													    SQLITE_OPEN(3)

Check Out this Related Man Page

SQLITE_POPEN(3) 														   SQLITE_POPEN(3)

sqlite_popen - Opens a persistent handle to an SQLite database and create the database if it does not exist

SYNOPSIS

       resource sqlite_popen (string  $filename, [int  $mode = 0666], [string  &$error_message])

DESCRIPTION

	This  function	behaves  identically to sqlite_open(3) except that is uses the persistent resource mechanism of PHP. For information about
       the meaning of the parameters, read the sqlite_open(3) manual page.

       sqlite_popen(3) will first check to see if a persistent handle has already been opened for the given $filename. If it finds one, it returns
       that handle to your script, otherwise it opens a fresh handle to the database.

	The  benefit  of  this	approach is that you don't incur the performance cost of re-reading the database and index schema on each page hit
       served by persistent web server SAPI's (any SAPI except for regular CGI or CLI).

       Note

	       If you use persistent handles and have the database updated by a background process (perhaps via a crontab), and that  process  re-
	      creates  the  database  by  overwriting it (either by unlinking and rebuilding, or moving the updated version to replace the current
	      version), you may experience undefined behaviour when a persistent handle on the old version of the database is recycled.

	       To avoid this situation, have your background processes open the same database file and perform their updates in a transaction.

PARAMETERS

	      o $filename
		- The filename of the SQLite database. If the file does not exist, SQLite will attempt to create it. PHP must have  write  permis-
		sions to the file if data is inserted, the database schema is modified or to create the database if it does not exist.

	      o $mode
		-  The	mode  of the file. Intended to be used to open the database in read-only mode. Presently, this parameter is ignored by the
		sqlite library. The default value for mode is the octal value 0666 and this is the recommended value.

	      o $error_message
		- Passed by reference and is set to hold a descriptive error message explaining why the database could not be opened if there  was
		an error.

RETURN VALUES

	Returns a resource (database handle) on success, FALSE on error.

SEE ALSO

       sqlite_open(3), sqlite_close(3), sqlite_factory(3).

PHP Documentation Group 													   SQLITE_POPEN(3)

Linux and UNIX Man Pages

sqlite_open(3) [php man page]

Check Out this Related Man Page