| From: | Jean-Baptiste Quenot <jbq(at)caraldi(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Fix PL/Python metadata when there is no result |
| Date: | 2012-02-10 16:44:15 |
| Message-ID: | CAK6bCay4yrFJD3po_bCke4ukjjsPLkbf+ad07jZiAU3N6cwUiA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear hackers,
Thanks for the work on PLPython result metadata, it is very useful! I
just came across a crash when trying to access this metadata on the
result of an UPDATE, which obviously cannot return any tuple (unless
you specify a RETURNING clause maybe?).
Please find attached a patch that solves this issue. Instead of a PG
crash, we get the following message:
ERROR: plpy.Error: no result fetched
All the best,
--
Jean-Baptiste Quenot
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-PLPython-metadata-access-when-there-is-no-result.patch | application/octet-stream | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2012-02-10 16:58:17 | Re: psql tab completion for SELECT |
| Previous Message | Robert Haas | 2012-02-10 16:23:50 | Re: psql tab completion for SELECT |