| From: | "Dave Page" <dpage(at)postgresql(dot)org> |
|---|---|
| To: | robins(at)pobox(dot)com |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Google Summer of Code |
| Date: | 2007-04-22 18:56:28 |
| Message-ID: | 200704221956280000@265980200 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
> ------- Original Message -------
> From: Robins <tharakan(at)gmail(dot)com>
> To: pgadmin-hackers(at)postgresql(dot)org
> Sent: 22/04/07, 17:28:25
> Subject: Re: [pgadmin-hackers] Google Summer of Code
>
> 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 ?
It's primarily a design tool, not an auto-doc tool, so you will generate DDL from a completed design. The auto-doc (ie. reverse engineering an existing schema) functionality is expected to be a post-SoC project.
Regards, Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira de Oliveira | 2007-04-23 00:43:55 | Re: Google Summer of Code |
| Previous Message | Robins | 2007-04-22 16:28:25 | Re: Google Summer of Code |