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 * Some way to deeply check to schema objects, e.g., for testing I
7 parse a MySQL schema, translate to Oracle, then parse the created
8 Oracle schema and want to check the two schema objects. I've
9 started a script called "sqlt-diff" to diff two schemas, but it's
10 not included with the 0.03 release. Submit ideas on how this
11 should work and what it should create (e.g., text reports and ALTER
12 statements) to the list.
14 * Add more DBI parsers! These have the potential to be very
15 thorough and far faster than parsing text files with
18 * At least allow more pass-through of INSERT, DELETE, and UPDATE
21 * Add INSERT statements for xSV, Excel parsers to automatically
22 create INSERTs for each row of data in the source file
24 * Somehow merge ClassDBI producer with CGI::FormBuilder or Template
25 Toolkit and some sort of automated CGI builder to create
26 view/create/edit/delete forms for objects based on schema defs
28 * Embetter the Diagram producer to use some real graphing algorithms
29 to distribute the tables so that the lines don't overlap so badly
31 * Integrate more with some standard XML schema representations,
32 maybe like Torque DB (http://db.apache.org/torque/). We've
33 started messing around with XMI, too, but that wasn't quite usable
36 * Possibly write a basic ANSI-92 SQL parser which could be extended
37 when writing other new parsers.
39 * Support for precompiled Parse::RecDescent grammars.
41 * More code generation producers, such as Java, PHP, and Python.
43 * Integrate Module::Pluggable as a replacement for the _list method.