| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | Scott Frankel <frankel(at)circlesfx(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, "PostgreSQL List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: prepared statements |
| Date: | 2010-07-24 11:01:10 |
| Message-ID: | A4064957-9313-4183-84CA-BC9A9BB0E0CF@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 24 Jul 2010, at 1:32, Scott Frankel wrote:
> Works! The bug in my example was not passing the INSERT statement an explicit list of column names, as per any non-prepared insert.
You would have needed it for an unprepared statement just as well in this case. You expect the planner to guess which columns you left out? ;)
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c4ac805286212004583493!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2010-07-24 16:22:02 | Re: Incorrect FTS result with GIN index |
| Previous Message | Alban Hertroys | 2010-07-24 10:57:50 | Re: pg_dump, shemas, backup strategy |