From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Greg Copeland" <greg(at)CopelandConsulting(dot)Net>, "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | <greg(at)turnstep(dot)com>, "PostgresSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: \d type queries - why not views in system catalog?!? |
Date: | 2003-01-13 21:00:44 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8259A94@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Greg Copeland [mailto:greg(at)CopelandConsulting(dot)Net]
> Sent: 13 January 2003 20:56
> To: Robert Treat
> Cc: greg(at)turnstep(dot)com; PostgresSQL Hackers Mailing List
> Subject: Re: [HACKERS] \d type queries - why not views in
> system catalog?!?
>
>
> Oh!
>
> That's an excellent idea. Seemingly addresses the issue and
> has value-add. I'm not aware of any gotchas here. Is there
> something that is being overlooked?
Why use functions instead of views? Most UIs will want to format the
output as they see fit so a recordset would be the appropriate output.
Yes, a function could do this, but surely views would be simpler to
implement and maintain.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Copeland | 2003-01-13 21:42:59 | Re: \d type queries - why not views in system catalog?!? |
Previous Message | Greg Copeland | 2003-01-13 20:56:22 | Re: \d type queries - why not views in system catalog?!? |