_______                           __  __    __    __                 
      \      \    ____   __ __ _______ |__||  |  |  |  |__|  ____    ____  
      /   |   \ _/ __ \ |  |  \\_  __ \|  ||  |  |  |  |  | /  _ \  /    \ 
     /    |    \\  ___/ |  |  / |  | \/|  ||  |__|  |__|  |(  <_> )|   |  \
     \____|__  / \___  >|____/  |__|   |__||____/|____/|__| \____/ |___|  /
    =========\/======\/=================================================\/==
  v0.01 04/JUL/2007 (C) Copyright 2007-2007 Scott D. Yelich SOME RIGHTS RESERVED
 .,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.-*~'`^`'~*-,._.,-*~'`^`'~*-,. 


The software is released under Creative Commons - Attribution 3.0 unported 
see: http://creativecommons.org/licenses/by/3.0/legalcode

See "LICENSE" for text, URL above for latest version.

See "INSTALL" for information on installation (and usage).

See "TODO" for ideas about what could be done in a next version.

api_1 a C++ example based on http://www.sqlite.org/quickstart.html and
uses sqlite3_exec.

api_2 is based on http://www.sqlite.org/quickstart.html, but follows
the 5 steps above.  It uses sqlite3_prepare_v2 and sqlite3_step
instead of sqlite3_get_exec.  Due to the use of sqlite3_exec, a
"callback" routine "process_row" is used to handle each result
returned from the SQL statement.  The callback simply prints out each
value using sqlite3_column_text (regardless of any true type for the
column).

api_3 is similar to api_2 in design, although the SQL is different.
This example demonstrates the use of sqlite3_bind_text to bind a value
to the prepared SQL statement.

Enjoy!

Scott