well. my first question is: which ERD? ;)) if i reckon well, if you
buy a database
related book, then you will find different ERD notations introduced by
their
authors.
imho, if you really want to use ERD, then just install dia as it
serves as visio-like
application implementing different graphical notations.
and gaphor is about UML not different notations, which is a lot more
than just
graphical notation of a diagram. for example whole metamodel described
in UML
specification, which does not exist for ERD.
as i understand you want ERD for database tables and associations
between them.
that actually can be realized with UML. imho, it is matter of
appropriate profile,
defined stereotypes and notation guideliness (i.e. naming of
associations). also
icons for stereotypes and artifacts could be prepared to make nicer
visualization
of database related UML diagram items.
then, there are several benefits from that:
- we omit effort of ERD maintainance and introduction of another
notation
(imho, there should be one to rule them all, that is UML)
- any code generation gaphor's plugin can generate classes from UML
diagrams,
also those, which are created with some database profile in mind
(see previous
paragraph)
- for SQL schema generation... just create plugin for gaphor which
operates on UML
metamodel
UML can be used for database related diagrams. i do not think we need
to introduce ERD
here. with gaphor
- you can define database UML profile, i.e. stereotypes for every UML
element
(classes, associations, whatever), i.e. "relation" stereotype for a
classes, which are
mapped to SQL table
- associations can have name and direction
- there are artifacts and nodes if you need more deployment-like stuff
- you can create SQL schema generation plugin very easily as there is
nice plugin infrastructure
for sure gaphor is missing few bits
- user defined icons for artifacts and stereotypes (i.e. class items
with stereotype "relation"
could be decorated with some appropriate icon - such behaviour is
even defined
in UML specification)
- loading/saving of profiles; now, you have to define UML profile in
every gaphor file
you have, that has to be improved <- that's the big thing, which i
miss in gapor now :)))
- some nice wiki page about database notation guideliness
i hope that you do not feel discouraged. and if you feel that you can
switch yourself
from ERD to UML and want to contribute missing bits into gaphor
project... then you
are more than welcome. :))
if you need bit more explanation about above, then do not hesistate to
ask questions,
please.
best regards,
wrobell <
wro...@pld-linux.org>