SQLite CVSTrac

*** 200,206 ****
        FROM a1, a2
        WHERE a1.a = a2.b(+);
  
! *: Oracle's Named Parameter output syntax.  In Oracle, one can declare parameters and select into them as such
  
  _:Select A1, A2, A3 into (:p1, :p2, :p3) from TableA
  
--- 200,207 ----
        FROM a1, a2
        WHERE a1.a = a2.b(+);
  
! *: Oracle's Named Parameter output syntax.  In Oracle, one can declare parameters and select into them
! as such
  
  _:Select A1, A2, A3 into (:p1, :p2, :p3) from TableA
  
***************
*** 237,243 ****
  INFORMATION_SCHEMA, wich contains info about all databases, tables, columns, index, views, stored
  procedures, etc.
  
! Can someone tell me how to fake describe until something like this is implemented?  Sorry, I'm too dependent on Oracle apparently :(
  
  *:SELECT ... FOR UPDATE OF ... is not supported.  This is understandable considering the mechanics of
  SQLite in that row locking is redundant as the entire database is locked when updating any bit of it.
--- 238,245 ----
  INFORMATION_SCHEMA, wich contains info about all databases, tables, columns, index, views, stored
  procedures, etc.
  
! Can someone tell me how to fake describe until something like this is implemented?  Sorry, I'm too
! dependent on Oracle apparently :(
  
  *:SELECT ... FOR UPDATE OF ... is not supported.  This is understandable considering the mechanics of
  SQLite in that row locking is redundant as the entire database is locked when updating any bit of it.
***************
*** 382,389 ****
  *NOT* free), so if you are looking for something to distribute along with your application, SQLite seem
  to win against 10g, MySQL, Postgree, or whatever (by Makc). - Just to be awkward, what about
  berkelydb etc? And when you say free you mean free of restrictions don't you (rather than Free
! software)?  -- Berkeley DB does
! not include SQL support.
  
  I wonder how useful these "remarks" are...
  
--- 384,396 ----
  *NOT* free), so if you are looking for something to distribute along with your application, SQLite seem
  to win against 10g, MySQL, Postgree, or whatever (by Makc). - Just to be awkward, what about
  berkelydb etc? And when you say free you mean free of restrictions don't you (rather than Free
! software)?  -- Berkeley DB does not include SQL support.
! 
! *: To above paragraph. Sometimes it is better pay few hundreds of bucks (just few hours of
! my work rate) and get much more powerful commercial solution which is royalty free. For example I
! very love Valentina database - www.paradigmasoft.com.  Valentina beats anything in 10-100+ times,
! especially on big dbs . It is not expensive, royalty free. Really full SQL92, yet they have cool Object-
! Relational features.
  
  I wonder how useful these "remarks" are...
  
***************
*** 399,402 ****
    set values [list a b c]
    db eval { SELECT * FROM table WHERE x IN ($values) }
  
! SQLite does its own variable interpolation which avoids the (messy) need to do value quoting/escaping (to protect against SQL injection attacks, etc.) but in the case where it's an "IN ($variable)" clause, it treats $variable as a single value instead of a Tcl list of values.  Or, maybe I'm doing something wrong.  If I am, please let me know: dossy@panoptic.com.
--- 406,412 ----
    set values [list a b c]
    db eval { SELECT * FROM table WHERE x IN ($values) }
  
! SQLite does its own variable interpolation which avoids the (messy) need to do value quoting/escaping
! (to protect against SQL injection attacks, etc.) but in the case where it's an "IN ($variable)" clause, it
! treats $variable as a single value instead of a Tcl list of values.  Or, maybe I'm doing something wrong.
! If I am, please let me know: dossy@panoptic.com.

sqlite - Unsupported Sql