Re: Google Summer of Code - Mailing list pgadmin-hackers

From Robins
Subject Re: Google Summer of Code
Date
Msg-id 36af4bed0704220928x5c7a284dtbdc22ae76161ba8e@mail.gmail.com
Whole thread Raw
In response to Re: Google Summer of Code  (Andy Burns <fedora@adslpipe.co.uk>)
Responses Re: Google Summer of Code  (Euler Taveira de Oliveira <euler@timbira.com>)
List pgadmin-hackers

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.

Or did I too get it wrong ?

Robins

On 4/22/07, Andy Burns <fedora@adslpipe.co.uk> wrote:
On 22/04/2007 08:46, Giuseppe Sacco wrote:

> I just wonder why you should draft a new XML DTD. I never used XML for
> such data, but probably some specification has already been written.

I got the impression that it wasn't the actual structure of the ER
diagram itself that was going to be stored (on the grounds that will be
gleaned from the database schema itself) but what _will_ be stored
stored is metadata about the diagram, such as positioning and sizing
information for each element, or did I jump to conclusions?



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match



--
Robins

pgadmin-hackers by date:

Previous
From: Andy Burns
Date:
Subject: Re: Google Summer of Code
Next
From: "Dave Page"
Date:
Subject: Re: Google Summer of Code