37 lines
1.3 KiB
Plaintext
37 lines
1.3 KiB
Plaintext
From: phd at sun.med.ru (Oleg Broytmann)
|
|
Date: Tue, 13 Apr 1999 16:27:15 GMT
|
|
Subject: bug in PyGreSQL module
|
|
In-Reply-To: <14099.24295.229214.504295@bitdiddle.cnri.reston.va.us>
|
|
References: <14099.24295.229214.504295@bitdiddle.cnri.reston.va.us>
|
|
Message-ID: <Pine.SOL2.3.96.SK.990413202550.14558g-100000@sun.med.ru>
|
|
X-UID: 1642
|
|
|
|
On Tue, 13 Apr 1999, Jeremy Hylton wrote:
|
|
> I found an apparent bug in the Python interface to PostgreSQL. I
|
|
> tried sending a query to the author but haven't heard back, so I'm
|
|
> looking for other users to see if they have run into the problem.
|
|
> I have a table with lots of int fields, some of which of NULL. When I
|
|
> do a Python query, the PyGreSQL module converts the NULL to 0 instead
|
|
> of None, which is the value I expected. Is that a reasonable
|
|
> expectation?
|
|
|
|
I have not noted such problem, I am using PyGres quite happily. Which
|
|
version you are using?
|
|
|
|
> The PyGreSQL module doesn't implement the DB API, but I checked there
|
|
> anyway. Alas, it didn't say anything about how to handle NULL.
|
|
|
|
DB API will be implemented in the upcominh PyGres 3.0.
|
|
|
|
> Jeremy
|
|
|
|
Oleg.
|
|
----
|
|
Oleg Broytmann National Research Surgery Centre http://sun.med.ru/~phd/
|
|
Programmers don't die, they just GOSUB without RETURN.
|
|
|
|
|
|
|
|
|
|
|