r10841: 16 Nov 2005 Kevin Rosenberg <kevin@rosenberg.net>

[clsql.git] / TODO

diff --git a/TODO b/TODO
index bf7884a19001bb60db9692a1ac6d671d48db124e..4b85e96bb72fbe6c5f49732d197e16d39a48fa50 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,61 +1,24 @@
 TESTS TO ADD
 
-* CACHE-TABLE-QUERIES
-* Test that ":db-kind :key" adds an index for that key. This is complicated by different
-  backends showing autogenerated primary key in different ways.
-* Large object testing
-* Test bigint type
+* Test that ":db-kind :key" adds an index for that key. This is complicated by 
+  different backends showing autogenerated primary key in different ways.
 * :db-constraint tests
-* test *db-auto-sync* 
-* test SELECT caching
-* for-each-row macro
-* universal-time 
-
-COMMONSQL SPEC
-
-* Incompatible 
-
- >> The functional sql interface 
-  
-    SELECT 
-      o keyword arg :refresh should function as advertised 
-
- >> Symbolic SQL syntax 
-
-      o userenv (Oracle specific but deprecated in Oracle 9) 
-
-VARIANCES FROM COMMONSQL
-
-UPDATE-OBJECT-JOINS:
- Rather than simply reading the values for each
- object, to meet CommonSQL spec need to generate a single
- query to read values for all objects, up to max-len count.
-
-COMMIT,ROLLBACK,START-TRANSACTION: 
- When COMMIT or ROLLBACK are called outside of WITH-TRANSACTION, an sql 
- transaction must be explicitly started first with START-TRANSACTION. 
+* Number and Char field types
+* symbol slot
+* generalized-boolean slot
+* tests for db-reader and db-writer
 
 OPTIMIZATIONS
  
-* Revisit result-type list creation,perhaps caching
+* Revisit result-type list creation, perhaps caching
+* Rework LIST-ATTRIBUTE-TYPES and LIST-INDEXES such that they exhibit their 
+  current behaviours using single database queries.  
+* Possible use of cached attribute type information for operations which 
+  insert/update records as mentioned in the CommonSQL user guide. 
+* Extend caching of generated SQL strings to more complex expressions which 
+  are likely to be repeatedly executed many times. 
 
 POSSIBLE EXTENSIONS
 
-* port Oracle backend to UFFI
-* large object support 
+* improve large object api and extend to databases beyond postgresql 
 * add support for prepared statements
-
-
-NOTES ABOUT THE BACKENDS
-
-MYSQL 
-
-drop-index:   requires a table to be specified with the :from keyword parameter
-views:        mysql does not support views  
-queries:      nested subqueries are not supported
-syntax:       doesn't support the sql concatenation operator (||). 
-
-SQLITE 
-
-create-view:  column-list parameter not supported 
-syntax:       doesn't support the sql SUBSTRING operator.