> Frankly, I think I was pretty much where Andy is. I mean, aren't we
> storing 'only position / sizing (in other words UI) details' in the schema
> Storing the database structure in the schema (and not reading it from the
> database) is going to be quite futile for me personally ... you know
> 'managing two schemas' issue.
See this link  where I explain in details the advantage of storing
the diagram metadata in a XML Schema. Briefly:
* model 1 is database-independent so you don't need a database
connection to open and modify the diagram;
* using model 2, you can't differ if an object is part of one diagram or
another one; so you can't have two models in the same database!
IMHO an general ER Tool (I know it involves a complexity) is better than
a database-driven one.
Euler Taveira de Oliveira
In response to
pgadmin-hackers by date
|Next:||From: svn||Date: 2007-04-23 09:01:39|
|Subject: SVN Commit by dpage: r6226 - in trunk/pgadmin3: . pgadmin/schema|
|Previous:||From: Dave Page||Date: 2007-04-22 18:56:28|
|Subject: Re: Google Summer of Code|