On Thu, Feb 10, 2005 at 01:29:42PM -0600, James Thompson wrote:
> Though if IIRC it does round timestamps which can burn a person at times :)
> I don't have a test case to verify if my memory is correct about this though.
Actually, I think it's just that mxDateTime defaults to displaying
times
On Thursday 10 February 2005 10:19 am, you wrote:
> Alex Turner wrote:
> >Can anyone recommend a python interface other than pygresql for
> >postgresql. Yet again they have changed the API (pg.error is now
> >pg.Error), and I can get no information from the mailing list, which
> >seems dead.
>
> P
Alex Turner wrote:
Can anyone recommend a python interface other than pygresql for
postgresql. Yet again they have changed the API (pg.error is now
pg.Error), and I can get no information from the mailing list, which
seems dead.
Pyscopg is very popular. We use it hear at Command Prompt
with gre
On Thu, Feb 10, 2005 at 10:58:05AM -0500, Alex Turner wrote:
> Can anyone recommend a python interface other than pygresql for
> postgresql. Yet again they have changed the API (pg.error is now
> pg.Error), and I can get no information from the mailing list, which
> seems dead.
psycopg is popula
Stephen Robert Norris <[EMAIL PROTECTED]> writes:
> Actually, it's a bug. I spent most of today with a co-worker looking for
> it. There's a Py_DECREF missing in the fetch routine, which makes it
> leak the results of every fetch. Who do I send the (one-line) fix to?
pgsql-patches list.
On Wed, 2001-10-17 at 16:56, Denis Gasparin wrote:
> At 16/10/01 14.00, you wrote:
> >Does the python interface leak memory? We are seeing the process grow
> >with basically every select. Any suggestions on what's going on? There
> >are no cycles, and a trivial program (basically a loop around a s
At 16/10/01 14.00, you wrote:
>Does the python interface leak memory? We are seeing the process grow
>with basically every select. Any suggestions on what's going on? There
>are no cycles, and a trivial program (basically a loop around a select)
>demonstrates the problem.
>
>This is 7.1.2 on RH7.[
Are you disposing the results of each select call? Not being familiar with
Python, as well as not knowing which interface for Python you are using, or
the code used to invoke the selects, I can only surmise that the result data
from each select is being stored in RAM and never garbage collected. A
