Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
                        POSTGRESQL BUG REPORT TEMPLATE

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()

>> 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,

Attachment: pygresql_int8.patch
Description: application/octet-stream (576 bytes)


pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group