| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Don Baccus <dhogaza(at)pacifier(dot)com> |
| Cc: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com>, The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Beta for 4:30AST ... ? |
| Date: | 2000-02-21 19:27:08 |
| Message-ID: | 23462.951161228@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Don Baccus <dhogaza(at)pacifier(dot)com> writes:
> I was able to fix my views by changing:
> create view foo as select * from bar;
> to:
> ...select * from bar bar;
Hmm, I think I see it.
create view foo as select * from int8_tbl;
$ pg_dump -t foo regression
\connect - postgres
CREATE TABLE "foo" (
"q1" int8,
"q2" int8
);
CREATE RULE "_RETfoo" AS ON SELECT TO foo DO INSTEAD SELECT int8_tbl.q1,
int8_tbl.q2 FROM int8_tbl (q1, q2);
IIRC, Thomas explained that the ANSI syntax says you *must* supply a
table alias if you are going to supply any column aliases in FROM.
The regurgitated rule violates that.
I guess this is another manifestation of the issue about the system
shoving in column "aliases" that the user never typed. pg_dump is
probably repeating what the backend told it. Think we'll have to
leave it unfixed till Thomas gets back.
It's also a reminder that the regress tests don't exercise pg_dump :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Baccus | 2000-02-21 19:28:04 | Re: [HACKERS] Beta for 4:30AST ... ? |
| Previous Message | Bruce Momjian | 2000-02-21 19:19:37 | Re: [HACKERS] Beta for 4:30AST ... ? |