Small. Fast. Reliable.
Choose any three.
*** 1,30 ****
  FAQ
  
  Q) Does SQLIte have a sintax equivalent to:
      SHOW TABLES
! Or how do I find out what tables does a SQLite database have?
  
  A) It's not as simple as "show tables", but it does work:
  
    SELECT name FROM sqlite_master WHERE type = "table"
  
! I guess you could create a view to simply frequent querying.
  
  ------
  
! Q) Are there any plans for Concurrent Queryes Improvements on SQLite??? I mean, when i'm hipotetically inserting 100000 records in a table throguht a PHP PDO Query, and i try to access this table for a simply query like (select * from table where id = 1), SQLite returns a message that the table is locked. Are there any research for this? Is there a active project roadmap?
  Thanks!
  
  ------
  
  Q) How many characters can a query have? (TCL: dbHandle eval $Query)
  
! A) The lessor of the amount of available memory and 2147483648 bytes.
  
  ------
  
  Q) How atomic are the SQL statements? Are UPDATE/INSERT/SELECT/DELETE
! atomic(e.g, can you modify multiple cross-dependant rows, under the assumption
  that no one of them could be read by a SELECT thread from another connection)?
  What about nested queries? What about triggers? For example: If a trigger
  renumbers a sequencial integer column on INSERT/DELETE, can it be assumed a
--- 1,32 ----
  FAQ
  
  Q) Does SQLIte have a sintax equivalent to:
+ 
      SHOW TABLES
! 
! Or how do I find out what tables a SQLite database has?
  
  A) It's not as simple as "show tables", but it does work:
  
    SELECT name FROM sqlite_master WHERE type = "table"
  
! I guess you could create a view to simplify frequent querying.
  
  ------
  
! Q) Are there any plans for Concurrent Queryes Improvements on SQLite??? I mean, when i'm hypothetically inserting 100000 records in a table throguh a PHP PDO Query, and I try to access this table for a simpe query like (select * from table where id = 1), SQLite returns a message that the table is locked. Is there any research for this? Is there a active project roadmap?
  Thanks!
  
  ------
  
  Q) How many characters can a query have? (TCL: dbHandle eval $Query)
  
! A) The lesser of the amount of available memory and 2147483648 bytes.
  
  ------
  
  Q) How atomic are the SQL statements? Are UPDATE/INSERT/SELECT/DELETE
! atomic (e.g, can you modify multiple cross-dependant rows, under the assumption
  that no one of them could be read by a SELECT thread from another connection)?
  What about nested queries? What about triggers? For example: If a trigger
  renumbers a sequencial integer column on INSERT/DELETE, can it be assumed a
***************
*** 34,40 ****
  
  ------
  
! Q) Is there an expression(inside SELECT) for checking if a column exists?
  
  ------
  
--- 36,42 ----
  
  ------
  
! Q) Is there an expression (inside SELECT) for checking if a column exists?
  
  ------
  
***************
*** 53,59 ****
  to use it in a browser based applicaiton and possibly call it using
  Javascript/PHP?
  
! 
  
  Q) Is the built-in SQL function list under
  {link:http://www.sqlite.org/lang_expr.html
--- 55,61 ----
  to use it in a browser based applicaiton and possibly call it using
  Javascript/PHP?
  
! ------
  
  Q) Is the built-in SQL function list under
  {link:http://www.sqlite.org/lang_expr.html
***************
*** 74,80 ****
  for SQLite callback functions (for sqlite3_exec function)?{linebreak}
  A) cdecl (caller pushes parameters right to left on stack, caller cleans up)
  -------
! Q) On sqlite3_Open(), when the file with given filename doesn't exists, SQLite
  creates new database. But
  usually, the application needs to do some initialization work to be able to use
  this new database (create
--- 76,82 ----
  for SQLite callback functions (for sqlite3_exec function)?{linebreak}
  A) cdecl (caller pushes parameters right to left on stack, caller cleans up)
  -------
! Q) On sqlite3_Open(), when the file with given filename doesn't exist, SQLite
  creates new database. But
  usually, the application needs to do some initialization work to be able to use
  this new database (create