[dbsrgits/SQL-Translator.git] / TODO

*   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. 

*   Add more DBI parsers!  These have the potential to be very
    thorough and far faster than parsing text files with
    Parse::RecDescent.

*   At least allow more pass-through of INSERT, DELETE, and UPDATE
    statements

*   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 it isn't quite usable.

*   Possibly write a basic ANSI-92 SQL parser which could be extended
    when writing other new parsers.

*   Support for precompiled Parse::RecDescent grammars.

*   More code generation producers, such as Java, PHP, and Python.

*   Integrate Module::Pluggable as a replacement for the _list method.
Commit	Line	Data
d3b1f33a	1	* The regular Sybase parser is only just functional. If you are
	2	interested in using Sybase, I would suggest serializing the schema
	3	(via YAML or Storable) using the DBI-Sybase parser and then
	4	manipulating that as you see fit.
12d68885	5
d3b1f33a	6	* Add more DBI parsers! These have the potential to be very
	7	thorough and far faster than parsing text files with
	8	Parse::RecDescent.
13ab1113	9
	10	* At least allow more pass-through of INSERT, DELETE, and UPDATE
	11	statements
	12
	13	* Add INSERT statements for xSV, Excel parsers to automatically
	14	create INSERTs for each row of data in the source file
	15
13ab1113	16	* Somehow merge ClassDBI producer with CGI::FormBuilder or Template
	17	Toolkit and some sort of automated CGI builder to create
	18	view/create/edit/delete forms for objects based on schema defs
	19
	20	* Embetter the Diagram producer to use some real graphing algorithms
	21	to distribute the tables so that the lines don't overlap so badly
	22
	23	* Integrate more with some standard XML schema representations,
d3b1f33a	24	maybe like Torque DB (http://db.apache.org/torque/). We've
4e51265a	25	started messing around with XMI, too, but it isn't quite usable.
e99e9593	26
13ab1113	27	* Possibly write a basic ANSI-92 SQL parser which could be extended
d3b1f33a	28	when writing other new parsers.
dd7ea91d	29
	30	* Support for precompiled Parse::RecDescent grammars.
	31
	32	* More code generation producers, such as Java, PHP, and Python.
	33
	34	* Integrate Module::Pluggable as a replacement for the _list method.