Re: filtering after join
От | andrew |
---|---|
Тема | Re: filtering after join |
Дата | |
Msg-id | 29d3b0b90601270117t2a8ec180x469b2a65f6b29a13@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: filtering after join (andrew <andrew.ylzhou@gmail.com>) |
Ответы |
Re: filtering after join
|
Список | pgsql-sql |
I got errors in this query. I have a function complete(record) which takes a generic record type data. But it seems cannot be applied to a sub-select result: backend> explain select * from (select * from Person,Auction where Person.id=Auction.seller) as s where complete(s) QUERY: explain select * from (select * from Person,Auction where Person.id=Auction.seller) as s where complete(s) ERROR: Cannot pass result of sub-select or join s to a function On 1/27/06, andrew <andrew.ylzhou@gmail.com> wrote: > I can see the final plan by using the EXPLAIN command. But I want to > know the procedure of the planner in handling nesting queries. Can you > direct me to the corresponding part of the code and/or the documents? > Thanks. > > On 1/26/06, Peter Eisentraut <peter_e@gmx.net> wrote: > > andrew wrote: > > > How will the query planner do for a nesting query? Treat the > > > subqueries as multiple queries and then link them together? > > > where can I find the information (codes or documents)? > > > > Look at the execution plan using the EXPLAIN command. > > > > -- > > Peter Eisentraut > > http://developer.postgresql.org/~petere/ > > > > > -- > andrew > -- andrew
В списке pgsql-sql по дате отправления: