Changed term single tags to empty tags to mean <foo/> like tags, it being the correct...

[dbsrgits/SQL-Translator.git] / TODO

diff --git a/TODO b/TODO
index 673fa67..eae2ee8 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,16 +1,40 @@
-Define structure of the data returned by parsers:
-  o Producers need to know what to expect
-  o For testing purposes, we need to know if parsers are returning
-    something reasonable
+*   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.
 
-Modules to be written/finished
-    SQL::Translator::Validator
-    SQL::Translator::Parser::xSV
-    SQL::Translator::Producer::MySQL
-    SQL::Translator::Parser::Excel
+*   Explore some way to pass an open database handle instead of a
+    schema and then query through DBI methods to get the schema
+    definition, somewhat a la SQL::Schema (which only works with
+    Oracle right now)
 
-Should the parsers return an instance instead of a data structure?  It
-would make traversing the data structure easier.
+*   Add "CREATE VIEW" support to existing parsers
 
+*   At least allow more pass-through of INSERT, DELETE, and UPDATE
+    statements
 
-# vim: set sw=2 ts=2 tw=70 fo=trcqo:
+*   Add INSERT statements for xSV, Excel parsers to automatically
+    create INSERTs for each row of data in the source file
+
+*   Fix Sybase parser (which means really figuring out the dump format
+    we want to parse -- Sam, can you recommend something?)
+
+*   Add more parsers (though I need some ideas -- probably at least
+    one for SQLite since we have that producer)
+
+*   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/), add parsers
+    and producers
+
+*   Possibly write a basic ANSI-92 SQL parser which could be extended
+    when writing other new parsers -- can anyone help me nail down a
+    URL that describes in detail that spec?
+
+*   Expand sql_translator.cgi to be a frontend for all producer
+    formats, not just the graphical ones;  also improve the interface