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.
6 * Add more DBI parsers! These have the potential to be very
7 thorough and far faster than parsing text files with
10 * At least allow more pass-through of INSERT, DELETE, and UPDATE
13 * Add INSERT statements for xSV, Excel parsers to automatically
14 create INSERTs for each row of data in the source file
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
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
23 * Integrate more with some standard XML schema representations,
24 maybe like Torque DB (http://db.apache.org/torque/). We've
25 started messing around with XMI, too, but it isn't quite usable.
27 * Possibly write a basic ANSI-92 SQL parser which could be extended
28 when writing other new parsers.
30 * Support for precompiled Parse::RecDescent grammars.
32 * More code generation producers, such as Java, PHP, and Python.
34 * Integrate Module::Pluggable as a replacement for the _list method.