| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/Python result object str handler |
| Date: | 2013-01-08 21:25:37 |
| Message-ID: | 50EC8ED1.2060509@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/8/13 11:55 AM, Daniele Varrazzo wrote:
>>> <PLyResult status=5 nrows=2 rows=[{'foo': 1, 'bar': '11'}, {'foo': 2, 'bar': '22'}]>
> This looks more a repr-style format to me (if you implement repr but
> not str, the latter will default to the former).
The repr style was the only guideline I found. There is no guideline
for how str should look like when it's not repr. Do you have a better
suggestion for the output format?
(The reason this is str and not repr is that it doesn't contain other
information such as the tuple descriptor, so str of two different
results could easily be the same.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-01-08 21:30:25 | Re: PATCH: optimized DROP of multiple tables within a transaction |
| Previous Message | Magnus Hagander | 2013-01-08 21:24:28 | Re: PL/Python result object str handler |