1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
<html>
<body>
<h1>tedia2sql TODO list</h1>
<ul>
<li> Add switches for certain SQL constructs like "cascade", plus some
admin switch that turns on/off certain sets of switches.
<li> Add trigger-create for Sybase or other RDBMSs that
don't implicitly create triggers for foreign-key
referential integrity. Priority 3
<li> MySQL and MS-SQL SQL DDL output. For this, I am awaiting some
DBA that uses Dia and MySQL or MS-SQL, nothing really stopping me
from doing it besides that. Priority 2
<li> Modify Dia's UML object definitions to be more SQL-specific and
rename it to ER (delete the existing totally f-----g useless ER object
definitions inside Dia). Priority 3
<li> When UML Class comments are in place (Dia 0.91?) parse this and
create Class comments in the SQL DDL -- if the database doesn't support
comments, create a tedia_comment table for placing comments, and/or
place the comments in the DDL script as, duh, SQL comments. Priority
9 (must wait for Dia 0.91).
</ul>
</body>
</html>
|
