| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Rod Taylor <rbt(at)rbt(dot)ca> |
| Cc: | Mike Winter <mike(dot)winter(at)frontlogic(dot)com>, <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: "SELECT IN" Still Broken in 7.4b |
| Date: | 2003-08-20 17:41:09 |
| Message-ID: | 20030820103841.Q10580-100000@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
On Wed, 20 Aug 2003, Rod Taylor wrote:
> > Thanks, Stephan. I was really hoping that the IN(valuelist) was going to
> > be changed at the same time, because it really is unusable for anything
> > over a couple of thousand values.
>
> Changed to do what?
One possibility might be to act as if the valuelist was a table and do the
IN as if it were that way, rather than treating it as a set of ORs. That
would be basically like doing the temporary table solution, but without
requiring the user to do it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivek Khera | 2003-08-20 17:53:23 | Re: Buglist |
| Previous Message | Tom Lane | 2003-08-20 17:21:51 | Re: Qualified tables in error messages |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Winter | 2003-08-20 18:51:13 | Re: "SELECT IN" Still Broken in 7.4b |
| Previous Message | Aasmund Midttun Godal | 2003-08-20 17:12:49 | Before/After Trigger User Switching |