Re: PyGreSQL bug

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Andrew Johnson <ajohnson(at)lynn(dot)ci-n(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: PyGreSQL bug
Date: 2002-04-18 02:12:10
Message-ID: 200204180212.g3I2CBe22595@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


No one has replied, so I worked up a patch that I will apply in a few
days. Let me know if you don't like it.

---------------------------------------------------------------------------

Andrew Johnson wrote:
> Not sure if you're the right person to be talking to here, but the recent
> CVS pacthes to the module belong to you, so here goes.
>
> pgdb.connect() seems to be broken on Python 2.0.1 (which ships with
> Slackware 8), and perhaps on other Pythons, haven't checked. Something in
> the _pg.connect() call isn't working. I think the problem stems from the
> fact that 'host' is a named parameter of both _pg.connect and pgdb.connect,
> and so Python treats it as a variable assignment, not a named parameter.
>
> In any case, rewriting the call without named parameters solved the problem.
>
> Instead of:
>
> cnx = _pg.connect(host = dbhost, dbname = dbbase, port = dbport,
> opt = dbopt, tty = dbtty,
> user = dbuser, passwd = dbpassw
>
> use:
>
> cnx = _pg.connect(dbbase, dbhost, dbport, dbopt,
> dbtty, dbuser, dbpasswd)
>
> --
> Andrew Johnson (ajohnson(at)lynn(dot)ci-n(dot)com)
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

Attachment Content-Type Size
unknown_filename text/plain 1.2 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2002-04-18 02:30:54 Re: Index Scans become Seq Scans after VACUUM ANALYSE
Previous Message Thomas Lockhart 2002-04-18 02:06:45 Re: Index Scans become Seq Scans after VACUUM ANALYSE