Small. Fast. Reliable.
Choose any three.
*** 8,17 ****
  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 tables etc.) 
! So, what is the most natural way to determine, that Open() created new database instead of opening the existing one?{linebreak}
  A) Use some system API funtion like IsFileExists(DB_filename) before calling sqlite_open(DB_filename)
  -------
! Q) Is it possible to let the programmer choose - commit or rollback the transaction that was begun with BEGIN and some INSERTS/UPDATES, but was not finished due to system hangup or power failure, instead of automatically rollback it on opening the DB??? (assume the transaction journal file integrity is fully correct)
  -------
! Q) Is there a standard way of backing up SQlite databases aside from simply copying the database file to another location?
--- 8,26 ----
  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 
! tables etc.) 
! So, what is the most natural way to determine, that Open() created new database instead of opening the 
! existing one?{linebreak}
  A) Use some system API funtion like IsFileExists(DB_filename) before calling sqlite_open(DB_filename)
  -------
! Q) Is it possible to let the programmer choose - commit or rollback the transaction that was begun with 
! BEGIN and some INSERTS/UPDATES, but was not finished due to system hangup or power failure, 
! instead of automatically rollback it on opening the DB??? (assume the transaction journal file integrity is 
! fully correct)
  -------
! Q) Is there a standard way of backing up SQlite databases aside from simply copying the database file 
! to another location
! ------
! Q) Is it possible to output queries and associated results into an output text file?