> > I have also been eyeing Dia as a platform for a free
> > ER/database-design tool, but I had something in mind more ambitious
> > along the lines of ERwin. It would be nice to design it as a plug-in,
> > but I can see how there could be advantages of taking a seperate
> > development track.
>
> The dia code looks to me sufficiently nice that it would be easier to bolt
> on an extension API than to rewrite the interface engine.
So that means...plug-in? The more I think about it, the more I see how this
would be the better way to go. I just didn't know if it would be possible.
> > I think I would start with support for MySQL and PostgreSQL first.
> > My reasoning is that if you can afford Oracle, you can probably afford
> > Designer 2000, ERwin, Visio, etc.
>
> Probably true. I just happen to have a reasonable subset of Oracle
> reference books, and my printer's a bit short on toner :)
Don't get me wrong, I'd love to support Oracle too. I was just going to start
with the common free ones and then move on to the common commercial ones. My
priorities would probably go: Ingres, MySQL, PostgreSQL, RDB, Oracle.
Andy
