Skip creating package if no name (must have been an error in the source file

[dbsrgits/SQL-Translator.git] / TODO

diff --git a/TODO b/TODO
index 5d4c976..2cd4486 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,14 +1,37 @@
--   Diagram producer could benefit from some real graphing algorithms to
-    better distribute the boxes.
+*   The regular Sybase parser is only just functional.  If you are
+    interested in using Sybase, I would suggest serializing the schema
+    (via YAML or Storable) using the DBI-Sybase parser and then
+    manipulating that as you see fit. 
 
--   Some way to deeply check to schema objects, e.g., for testing I
+*   Some way to deeply check to schema objects, e.g., for testing I
     parse a MySQL schema, translate to Oracle, then parse the created
-    Oracle schema and want to check the two schema objects.
+    Oracle schema and want to check the two schema objects.  I've
+    started a script called "sqlt-diff" to diff two schemas, but it's 
+    not included with the 0.03 release.  Submit ideas on how this
+    should work and what it should create (e.g., text reports and ALTER 
+    statements) to the list.
 
--   Add parsers and producers for Torque XML/DB schema
-    (http://db.apache.org/torque/)
+*   Add more DBI parsers!  These have the potential to be very
+    thorough and far faster than parsing text files with
+    Parse::RecDescent.
 
--   Allow xSV/Excel parsers to produce INSERT statements of data in source
-    files, properly quoting strings
+*   At least allow more pass-through of INSERT, DELETE, and UPDATE
+    statements
 
--   Allow pass through of INSERT statements (e.g., default data)
+*   Add INSERT statements for xSV, Excel parsers to automatically
+    create INSERTs for each row of data in the source file
+
+*   Somehow merge ClassDBI producer with CGI::FormBuilder or Template
+    Toolkit and some sort of automated CGI builder to create
+    view/create/edit/delete forms for objects based on schema defs
+
+*   Embetter the Diagram producer to use some real graphing algorithms
+    to distribute the tables so that the lines don't overlap so badly
+
+*   Integrate more with some standard XML schema representations,
+    maybe like Torque DB (http://db.apache.org/torque/).  We've
+    started messing around with XMI, too, but that wasn't quite usable
+    for the 0.03 release.
+
+*   Possibly write a basic ANSI-92 SQL parser which could be extended
+    when writing other new parsers.