The arg is called "output_type," not "image_type."

[dbsrgits/SQL-Translator.git] / TODO

diff --git a/TODO b/TODO
index eae2ee8..2aa70a6 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,3 +1,8 @@
+*   The Sybase parser still doesn't work.  It is not included with the
+    distribution but can be found in CVS.  There has been some
+    discussion about reviving this, but no one has had that particular
+    itch to scratch, so it's languished.
+
 *   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.
@@ -15,12 +20,6 @@
 *   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
@@ -29,12 +28,9 @@
     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
+    maybe like Torque DB (http://db.apache.org/torque/)
 
 *   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?
+    when writing other new parsers
 
-*   Expand sql_translator.cgi to be a frontend for all producer
-    formats, not just the graphical ones;  also improve the interface
+*   More parsers, more producers!