Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can someone phrase a TODO item for me?
It's already done (not committed yet though).
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http:/
On Tue, 23 Apr 2002, Bruce Momjian wrote:
> Can someone phrase a TODO item for me?
How about:
Fix pg_get_viewdef() to output fully nested selects
Regards,
Ian Morgan
--
---
Ian E. MorganVice President & C.O.O. Web
Can someone phrase a TODO item for me?
---
Ian Morgan wrote:
> PostgreSQL 7.2.1's pg_dump prduces bad SQL for VIEW's.
>
> The SQL for CREATE VIEW as output by pg_dump generates an error, because the
> appropriate nesting o
Ian Morgan <[EMAIL PROTECTED]> writes:
> Even if adding ORDER BY to a UNION is really sub-optimal SQL, shouldn't
> pg_dump (and even psql's \d ) produce SQL that actually
> works
I didn't say it wasn't a bug ;-) ... just pointing out that fixing it
doesn't seem very high priority. I'll do someth
Ian Morgan <[EMAIL PROTECTED]> writes:
> The SQL for CREATE VIEW as output by pg_dump generates an error, because the
> appropriate nesting of SELECTs with parentheses is missing:
Hmm. You shouldn't *need* parentheses in most cases ...
> CREATE VIEW "agents" as (
> (
> SELECT DI
PostgreSQL 7.2.1's pg_dump prduces bad SQL for VIEW's.
The SQL for CREATE VIEW as output by pg_dump generates an error, because the
appropriate nesting of SELECTs with parentheses is missing:
ERROR: parser: parse error at or near "SELECT"
Original SQL:
CREATE VIEW "agents" as (
(
