PyGreSQL v3.2 doesn't support INT8 types

From: Ricardo Caesar Lenzi <ricardo(at)k1(dot)com(dot)br>
To: pgsql-patches(at)postgresql(dot)org
Cc: darcy(at)druid(dot)net
Subject: PyGreSQL v3.2 doesn't support INT8 types
Date: 2001-10-11 23:44:58
Message-ID: 20011011214458.635eff32.ricardo@k1.com.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : RICARDO CAESAR LENZI
Your email address : RICARDO(at)K1(dot)COM(dot)BR

System Configuration
---------------------
Architecture (example: Intel Pentium) : INTEL PENTIUM

Operating System (example: Linux 2.0.26 ELF) : LINUX 2.2.16

PostgreSQL version (example: PostgreSQL-7.1.1): PostgreSQL-7.2devel

Compiler used (example: gcc 2.95.2) : GCC 2.91.66

Please enter a FULL description of your problem:
------------------------------------------------

Python handle as string all int8 values from postgresql. This could be
view when using the aggregate function count() and function nextval
that returns an int8 value, but in python is represented like string:

>> db.query("select nextval('my_seq')").getresult()
[('2',)]

>> db.query("select count(*) from films").dictresult()
[{'count': '120'}]

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

see previous.

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------

Patch the file src/interfaces/python/pgmodule.c with the
patch file attached in this mail.

Please commit this before the version 7.2.
Thanks and congratulations for the good job,
Ricardo.

Attachment Content-Type Size
pygresql_int8.patch application/octet-stream 576 bytes

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2001-10-12 00:17:00 Re: Efficient slicing/substring of TOAST values (for comment)
Previous Message John Gray 2001-10-11 23:43:46 Re: Efficient slicing/substring of TOAST values (for