pypgsql-users — Discussion list for the pyPgSQL user community.

Re: [Pypgsql-users] [solve]Attribute error time

[Laurent F. <lfr...@wo...>]

Laurent FRANCOIS wrote:

>Hye,
>
>Here is a very simple py file:
>
>----
>from pyPgSQL import PgSQL
>----
>
>$python testpgsql.py
>
>Traceback (most recent call last):
>   File "testpgsql.py", line 1, in ?
>     from pyPgSQL import PgSQL
>   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 444, in ?
>     from mx import DateTime
>   File "/usr/lib/python2.3/site-packages/mx/DateTime/__init__.py", line
>8, in ?
>     from DateTime import *
>   File "/usr/lib/python2.3/site-packages/mx/DateTime/DateTime.py", line
>9, in ?
>     from mxDateTime import *
>   File
>"/usr/lib/python2.3/site-packages/mx/DateTime/mxDateTime/__init__.py",
>line 20, in ?
>     setnowapi(time.time)
>AttributeError: 'module' object has no attribute 'time'
>
>
>What's going on.
>
There is a time.py of my own.
mv time.py testtime.py

And everything goes right....

[Pypgsql-users] Attribute error time

[Laurent F. <lfr...@wo...>]

Hye,

Here is a very simple py file:

----
from pyPgSQL import PgSQL
----

$python testpgsql.py

Traceback (most recent call last):
   File "testpgsql.py", line 1, in ?
     from pyPgSQL import PgSQL
   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 444, in ?
     from mx import DateTime
   File "/usr/lib/python2.3/site-packages/mx/DateTime/__init__.py", line
8, in ?
     from DateTime import *
   File "/usr/lib/python2.3/site-packages/mx/DateTime/DateTime.py", line
9, in ?
     from mxDateTime import *
   File
"/usr/lib/python2.3/site-packages/mx/DateTime/mxDateTime/__init__.py",
line 20, in ?
     setnowapi(time.time)
AttributeError: 'module' object has no attribute 'time'


What's going on.

I am on Debian etch(=testing) and my pypgsql version is:
python-pgsql:
   Installé : 2.5.1-2
   Candidat : 2.5.1-2
  Table de version :
  *** 2.5.1-2 0

And: python-egenix-mxdatetime
python-egenix-mxdatetime:
   Installé : 2.0.6-4
   Candidat : 2.0.6-4
  Table de version :
  *** 2.0.6-4 0

Thanks for your advise

Re: [Pypgsql-users] PyPgSQL Windows XP Installation

[<gh...@gh...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

T=E4nia Jesini wrote:
> Hi all,
>=20
> I'm trying to install the lib PyPgSQL to access PostGresSQL from Python
> but I didn't get successful.
>=20
> My environment is:
>=20
> - Windows XP
> - PostGresSQL 8.1
> - Python 2.4
> - PyPgSQL 2.5.1
>=20
> What I did up to now:
>=20
> I've tried to install the binary version of PyPgSQL:
>=20
> pyPgSQL-2.5.1.win32-py2.4.exe
> <http://prdownloads.sourceforge.net/pypgsql/pyPgSQL-2.5.1.win32-py2.4.e=
xe?download>
>=20
> I've followed the wizard, that is in fact very simple, and tested on
> Python environment.
>=20
> I got the followin error:
>=20
> -------------------------
> Traceback (most recent call last):
>   File "<interactive input>", line 1, in ?
>   File "C:\Python24\Lib\site-packages\pyPgSQL\PgSQL.py", line 449, in ?
>     from libpq import *
>   File "C:\Python24\Lib\site-packages\pyPgSQL\libpq\__init__.py", line
> 23, in ?
>     from libpq import *
> ImportError: DLL load failed: The specified module could not be found.
> ----------------------------
>=20
> thank you for any help,

You will need to make sure that the PostgreSQL DLLs are found. I have don=
e
this by installing  PostgreSQL for Windows, and then either

a) putting the bin/ directory in the PATH or
b) copying the needed DLLs into the
C:\Python24\Lib\site-packages\pyPgSQL\libpq\ directory.

- -- Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEt/wGdIO4ozGCH14RAk0XAJ9qgq+h2Ap4dve6Xjy+UfdGcQyfLgCfczjW
M8XwSpKvxN4Ymv5tLv60Fhk=3D
=3DDmdh
-----END PGP SIGNATURE-----

[Pypgsql-users] PyPgSQL Windows XP Installation

[<tj...@gm...>]

Hi all,

I'm trying to install the lib PyPgSQL to access PostGresSQL from Python but
I didn't get successful.

My environment is:

- Windows XP
- PostGresSQL 8.1
- Python 2.4
- PyPgSQL 2.5.1

What I did up to now:

I've tried to install the binary version of PyPgSQL:

pyPgSQL-2.5.1.win32-py2.4.exe<http://prdownloads.sourceforge.net/pypgsql/py=
PgSQL-2.5.1.win32-py2.4.exe?download>

I've followed the wizard, that is in fact very simple, and tested on Python
environment.

I got the followin error:

-------------------------
Traceback (most recent call last):
  File "<interactive input>", line 1, in ?
  File "C:\Python24\Lib\site-packages\pyPgSQL\PgSQL.py", line 449, in ?
    from libpq import *
  File "C:\Python24\Lib\site-packages\pyPgSQL\libpq\__init__.py", line 23,
in ?
    from libpq import *
ImportError: DLL load failed: The specified module could not be found.
----------------------------

thank you for any help,

best regards,

T=E2nia.

[Pypgsql-users] SRPM for pyPgSQL

[Robin B. <rob...@ro...>]

Hi,

I found a source RPM for pyPgSQL on the 'net somewhere and I've updated
it for v2.5.1.

It was built on a CentOS 4.3 box but should build on most recent
Redhat/Fedora platforms.

It's downloadable here:

http://robinbowes.com/download/pyPgSQL/

Hope this is useful for someone.

R.

Re: [Pypgsql-users] SQLSTATE

[Karsten H. <Kar...@gm...>]

On Mon, Jun 26, 2006 at 05:17:15PM +0200, Gerhard Häring wrote:

> > do you see any chance pyPgSQL could provide SQLSTATE in the
> > very near future ?
> 
> Seems doable. As attribute of the exception object or did you have 
> anything else in mind?
Well, for all practical purposes it being an attribute of
the exception would be the proper place to put it IMO. It
might be an idea to perhaps also put it into the string of
the exception itself such as

 "[SQLSTATE:xxxx] OperationalError: ..."

This is similar to how Oracle (and psycopg, currently) does it.

That way, someone coding against DB-API *only* might still
have a chance to get at the value.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Re: [Pypgsql-users] SQLSTATE

[<gh...@gh...>]

Karsten Hilbert wrote:
> Hi Gerhard,
> 
> do you see any chance pyPgSQL could provide SQLSTATE in the
> very near future ?

Seems doable. As attribute of the exception object or did you have 
anything else in mind?

-- Gerhard

[Pypgsql-users] SQLSTATE

[Karsten H. <Kar...@gm...>]

Hi Gerhard,

do you see any chance pyPgSQL could provide SQLSTATE in the
very near future ?

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

Re: [Pypgsql-users] timestamp without time zone in version2.5.1

[Andrew M. <an...@ob...>]

>Thanks, this will be useful for creating date/time related tests.
>
>As far as I can see the INTERVAL stuff is an even bigger mess.

I've been meaning to write (and contribute) a set of "end-to-end" tests
for all the data types to ensure values make the round trip unmollested -
but date/times are the only real problem area I've noticed.

BTW, we run our application with PgSQL.useUTCtimeValue=True (I think
you may have added this option to keep us happy).

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/

Re: [Pypgsql-users] timestamp without time zone in version2.5.1

[<gh...@gh...>]

Andrew McNamara wrote:
>>> For some reason, when I tried to read timestamp without time zone data,
>>> it is processed as a GMC time + local time zone instead of a local 
> time.
>> Thanks for the report (you're the third one). I'll try to release a fixed
>> version the next few days.
> 
> I started creating some "acceptance tests" for new versions of pyPgSQL to
> be used with our application (www.netepi.org). [...]
> You might be interested in adding an elaborated version of the attached to
> the pyPgSQL unit tests (once they pass!).

Thanks, this will be useful for creating date/time related tests.

As far as I can see the INTERVAL stuff is an even bigger mess.

-- Gerhard

Re: [Pypgsql-users] timestamp without time zone in version2.5.1

[Andrew M. <an...@ob...>]

>> For some reason, when I tried to read timestamp without time zone data,
>> it is processed as a GMC time + local time zone instead of a local 
time.
>
>Thanks for the report (you're the third one). I'll try to release a fixed
>version the next few days.

I started creating some "acceptance tests" for new versions of pyPgSQL to
be used with our application (www.netepi.org). I didn't get very far - the
inconsistencies with the date/time types confounded me utterly (by the way,
psycopg is even worse in this respect). My focus was to get back the same
value on select as I inserted into a table.

You might be interested in adding an elaborated version of the attached to
the pyPgSQL unit tests (once they pass!).

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/

Re: [Pypgsql-users] timestamp without time zone in version2.5.1

[<gh...@gh...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

GUANG WANG wrote:
> Hi,
> 
> I installed the ver 2.5.1 on my box (redhat-release-3WS-7.4, python 2.4.3,
> postgresql8.0.8).
> For some reason, when I tried to read timestamp without time zone data,
> it is processed as a GMC time + local time zone instead of a local time. [...]

Thanks for the report (you're the third one). I'll try to release a fixed
version the next few days.

- -- Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEnFWFdIO4ozGCH14RAv+AAJ9Dhr9yVZfT/2gQgNgQtUiWNKGNJACeNY9N
uP1OMcI81HrfzJPdGjdYeYo=
=tB9z
-----END PGP SIGNATURE-----

[Pypgsql-users] timestamp without time zone in version2.5.1

[GUANG W. <sun...@ho...>]

Hi,

I installed the ver 2.5.1 on my box (redhat-release-3WS-7.4, python 2.4.3,
postgresql8.0.8).
For some reason, when I tried to read timestamp without time zone data,
it is processed as a GMC time + local time zone instead of a local time.

Is it supposed to be so?

--FROM postgres console:
test=# \d timestamptest;
             Table "public.timestamptest"
   Column    |            Type             | Modifiers
-------------+-----------------------------+-----------
withoutzone | timestamp without time zone |
withzone    | timestamp with time zone    |

test=# insert into timestamptest values (now(),now());
INSERT 408307324 1
test=# select * from timestamptest;
        withoutzone         |           withzone
----------------------------+-------------------------------
2006-06-22 17:57:08.280913 | 2006-06-22 17:57:08.280913-04
(1 row)

--FROM API:
>>>from pyPgSQL import PgSQL
>>>pgConn=PgSQL.connect(database='test',host='localhost',user='t',password='t')
>>>pgcursor=pgConn.cursor()
>>>pgcursor.execute("select withoutzone,withzone from timestamptest limit 
>>>1")
>>>res=pgcursor.fetchone()
>>>print "time(without timezone)=%s\ntime(with timezone)=%s." % 
>>>(res[0],res[1])
time(without timezone)=2006-06-22 13:57:08.28
time(with timezone)=2006-06-22 17:57:08.28.

[Pypgsql-users] [ANNOUNCE] pyPgSQL 2.5.1 released

[<gh...@gh...>]

I'll make it quick, but not *so* quick (accidentally sent a message a 
minute ago):

Patch for a security hole in PostgreSQL (CVE-2006-2314): escaping quotes 
with backslashes is insecure.  The change is to escape single quotes 
with another single quote: \' => ''.  Thanks to Martin Pitt for the patch.

Downloads (source, Windows binaries for Python 2.1, 2.2, 2.3, 2.4) at

http://sourceforge.net/project/showfiles.php?group_id=16528&package_id=20458&release_id=423036

Cheers,

-- Gerhard

[Pypgsql-users] [ANNOUNCE] pyPgSQL 2.5.1 released

[<gh...@gh...>]

Downloads

http://sourceforge.net/project/showfiles.php?group_id=16528&package_id=20458&release_id=423036

Re: [Pypgsql-users] [ANNOUNCE] pyPgSQL 2.5 released

[<gh...@gh...>]

Timothy Smith wrote:
> Gerhard Häring wrote:
>> Windows binaries for Python 2.1, 2.2 and 2.3 were uploaded in addition 
>> to the Python 2.4 binaries.
>>
> are the windows binaries linked against ssl?

Unlike previous pyPgSQL releases, this one has dynamically linked 
binaries. That means they are SSL-enabled if your PostgreSQL client 
library installation (libpq.dll) is.

-- Gerhard

Re: [Pypgsql-users] [ANNOUNCE] pyPgSQL 2.5 released

[Timothy S. <ti...@op...>]

Gerhard H=E4ring wrote:
> Windows binaries for Python 2.1, 2.2 and 2.3 were uploaded in addition=20
> to the Python 2.4 binaries.
>
> -- Gerhard
>
>
>
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users
>
>
>  =20
are the windows binaries linked against ssl?

Re: [Pypgsql-users] [ANNOUNCE] pyPgSQL 2.5 released

[<gh...@gh...>]

Windows binaries for Python 2.1, 2.2 and 2.3 were uploaded in addition 
to the Python 2.4 binaries.

-- Gerhard

[Pypgsql-users] [ANNOUNCE] pyPgSQL 2.5 released

[<gh...@gh...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

the last pyPgSQL release was in July 2003. Now, after a much too long time
I went through all items in the bugtracker and created a release.

pyPgSQL is a Python database adapter for PostgreSQL databases. Its homepage
is at http://pypgsql.sf.net/.

Downloads are available here:
http://sourceforge.net/project/showfiles.php?group_id=16528&package_id=20458&release_id=421992

There is a source package and Windows binaries for Python 2.4. The Windows
binaries are dynamically linked this time, so you will need a PostgreSQL
client library installation to make sure the DLLs are found. It's probably
easiest to just include the PostgreSQL bin and lib directory in your PATH.

Attached is a ChangeLog.

- -- Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEgNkXdIO4ozGCH14RAgqlAJ9nNNGM1cTzMK804tV3ItOlDBcuBQCfYvQR
GFaIhZnChH8ORdW7qMHKJMA=
=K3Y4
-----END PGP SIGNATURE-----

Re: [Pypgsql-users] New pyPgSQL release imminent - was Re: SQL injection attack

[Karsten H. <Kar...@gm...>]

On Thu, Jun 01, 2006 at 04:51:22PM +0200, Gerhard Häring wrote:

> Andrew McNamara wrote:
> >Should pyPgSQL attempt to mitigate this, or just count on Postgresql to
> >"fix" it?:  [...]
> 
> The next few days, there will be a pyPgSQL 2.5 release. The Windows 
> binaries will be linked against a client version which includes the 
> security fixes.
Thanks, Gerhard. This shows you are still around taking care
of the most critical things.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

[Pypgsql-users] New pyPgSQL release imminent - was Re: SQL injection attack

[<gh...@gh...>]

Andrew McNamara wrote:
> Should pyPgSQL attempt to mitigate this, or just count on Postgresql to
> "fix" it?:  [...]

The next few days, there will be a pyPgSQL 2.5 release. The Windows 
binaries will be linked against a client version which includes the 
security fixes.

I hope I found all outstanding patches and have them in CVS now. The 
test suite was reduced in complexity so that it now works against Python 
version 2.1 through 2.4 against PostgreSQL 8.1.

-- Gerhard

Re: [Pypgsql-users] SQL injection attack

[Andrew M. <an...@ob...>]

>> Should pyPgSQL attempt to mitigate this, or just count on Postgresql to
>> "fix" it?:
>
>AFAICT they fixed it already but the fix involves client
>code having to be modified, so, yes, pyPgSQL needs to be
>released compiled against an updated libpq to take advantage
>of that fix. Which may still leave some "application" code
>having to be fixed, too.

This is the most detailed information I've found:

    http://www.postgresql.org/docs/techdocs.50

That document seems to suggest two slightly different things - that
they now raise an error on invalid multi-character combinations, and/or
that they don't allow backslash escaping when a potentially unsafe
client_encoding is used.

I haven't been able to trigger the problem via pyPgSQL so far, but I
suspect I'm just doing it wrong. The above document suggests quoting '
by doubling it, rather than using the backslash escape, but I can't see
how this is any better.

I also think their "fix" is server-side, rather than in libpq.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/

Re: [Pypgsql-users] SQL injection attack

[Karsten H. <Kar...@gm...>]

On Wed, May 24, 2006 at 02:21:16PM +1000, Andrew McNamara wrote:

> Should pyPgSQL attempt to mitigate this, or just count on Postgresql to
> "fix" it?:
AFAICT they fixed it already but the fix involves client
code having to be modified, so, yes, pyPgSQL needs to be
released compiled against an updated libpq to take advantage
of that fix. Which may still leave some "application" code
having to be fixed, too.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

[Pypgsql-users] SQL injection attack

[Andrew M. <an...@ob...>]

Should pyPgSQL attempt to mitigate this, or just count on Postgresql to
"fix" it?:

    http://www.postgresql.org/about/news.561
    http://www.newsforge.com/article.pl?sid=06/05/23/2141246

    >>> from pyPgSQL import PgSQL
    >>> PgSQL.PgQuoteString("\xbf\x27")
    "'\xbf\\''"

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/

[Pypgsql-users] Connecting to a remote database

[Imara J. <im...@gm...>]

Hi all,

I am attempting to connect to a database that is on a remote server.

Sample code:

from pyPgSQL import PgSQL

connection =3D PgSQL.connect( host =3D "my-host", database =3D "db", user =
=3D
"user1", password =3D "")

Error: "user "my_login_name_for_machine" does not exist"

Problem is, this user does not have a password.  If I don't include a
password in the connection statement, the error is that a password is
not supplied.  Is there anyway that I can still connect without a
password?

Thanks in advance.