SQLite CVSTrac

*** 3,16 ****
  features that SQLite does not support, you may want to list them
  below.
  ----
  
  *: SQL92 Character sets, collations, coercibility.
  *: Inserting blob using X'AABBCCDD' syntax.
  *: Stored Procedures
  *: Rollup and Cube - _Who can tell me what this means?_
! _::: I don't know much about it myself, but a quick google on the subject gives me... http://
! www.winnetmag.com/SQLServer/Article/ArticleID/5104/5104.html and http://databases.about.com/
! library/weekly/aa070101a.htm
  _::: both of these imply that the CUBE operator causes new rows to be generated to give a wildcard 
  value to non-numeric columns and summing the numeric columns which match those wildcards. The 
  potential for generating a huge amount of data with cube is implicit, I think - hence its name. ROLLUP 
--- 3,22 ----
  features that SQLite does not support, you may want to list them
  below.
  ----
+ *: This is related to using SQLite with are many attached
+ databases. For example, I want create table in the database db1, based
+ on the table in the database db2:
+ create table db2.table1 as select * from db1.table1;
+ It doesn't work. But very often it will need.
+ So, it should looks like a schemas in ORACLE database.
+ 
+ *: Hierarhical Queries. START WITH <conditions> CONNECT BY [PRIOR]<conditions> (ORACLE)
  
  *: SQL92 Character sets, collations, coercibility.
  *: Inserting blob using X'AABBCCDD' syntax.
  *: Stored Procedures
  *: Rollup and Cube - _Who can tell me what this means?_
! _::: I don't know much about it myself, but a quick google on the subject gives me... http://www.winnetmag.com/SQLServer/Article/ArticleID/5104/5104.html and http://databases.about.com/library/weekly/aa070101a.htm
  _::: both of these imply that the CUBE operator causes new rows to be generated to give a wildcard 
  value to non-numeric columns and summing the numeric columns which match those wildcards. The 
  potential for generating a huge amount of data with cube is implicit, I think - hence its name. ROLLUP 
***************
*** 36,47 ****
  would map to databasename.tablename in the current sqlite arrangement.
  *: TRUNCATE (MySQL, Postgresql and Oracle have it... but I dont know if this is a standard command) - 
  _SQLite does this automatically when you do a DELETE
! without a WHERE clause._
  *: ORDER BY myfield ASC NULLS LAST (Oracle)
  *: CREATE TRIGGER [BEFORE | AFTER | INSTEAD OF] (Oracle)
  *: UPDATE with a FROM clause (not sure if this is standard, Sybase and Microsoft have it).
  *: Multi-column IN clause (ie. SELECT * FROM tab WHERE (key1, key2) IN (SELECT...)
! *: CURRENT-Functions like CURRENT_DATE, CURRENT_TIME are missing
  *: INSERTing less values than columns does not fill the missing columns with the default values; if 
  less values than columns in the table are supplied, all columns filled have to be named before the 
  keyword values
--- 42,53 ----
  would map to databasename.tablename in the current sqlite arrangement.
  *: TRUNCATE (MySQL, Postgresql and Oracle have it... but I dont know if this is a standard command) - 
  _SQLite does this automatically when you do a DELETE
! without a WHERE clause. You can use also VACUUM command_
  *: ORDER BY myfield ASC NULLS LAST (Oracle)
  *: CREATE TRIGGER [BEFORE | AFTER | INSTEAD OF] (Oracle)
  *: UPDATE with a FROM clause (not sure if this is standard, Sybase and Microsoft have it).
  *: Multi-column IN clause (ie. SELECT * FROM tab WHERE (key1, key2) IN (SELECT...)
! *: CURRENT-Functions like CURRENT_DATE, CURRENT_TIME are missing _Try "SELECT date('now');" or "SELECT datetime('now','localtime');"_
  *: INSERTing less values than columns does not fill the missing columns with the default values; if 
  less values than columns in the table are supplied, all columns filled have to be named before the 
  keyword values
***************
*** 53,59 ****
  users)
  *: enum column type (mysql does)
  *: join syntax (+) (-) like oracle has  - _SQLite used to have this but it
! was removed because it is not standard SQL._
  *: name columns in views (i.e. CREATE VIEW (foo, bar) AS SELECT qux, quo FROM baz;)
  *:FLOOR and CEILING functions, e.g. "SELECT FLOOR(salary) FROM personnel;"
  *:IF EXISTS function, e.g. "DROP TABLE IF EXISTS temp;"
--- 59,65 ----
  users)
  *: enum column type (mysql does)
  *: join syntax (+) (-) like oracle has  - _SQLite used to have this but it
! was removed because it is not standard SQL._ *RETURN IT BACK AGAIN, PLEASE!!!*
  *: name columns in views (i.e. CREATE VIEW (foo, bar) AS SELECT qux, quo FROM baz;)
  *:FLOOR and CEILING functions, e.g. "SELECT FLOOR(salary) FROM personnel;"
  *:IF EXISTS function, e.g. "DROP TABLE IF EXISTS temp;"

sqlite - Unsupported Sql