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

[Pypgsql-users] Re: Silent failure of an INSERT

[Rock H. <ro...@ip...>]

> 
> Sounds like you are missing a commit somewhere.
> 
> Karsten

I never did a BEGIN, so my understanding is that a COMMIT should not be
necessary.

Rock

Re: [Pypgsql-users] Silent failure of an INSERT

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

> I created a Python program that runs an INSERT command via PpyPgSQL. It
> returns a result of NONE and triggers no exception, but no row is added.
> I grab the query that is being run and I run it directly from a Pgsql
> client and it works fine.

Sounds like you are missing a commit somewhere.

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

[Pypgsql-users] Silent failure of an INSERT

[Rock H. <ro...@ip...>]

I created a Python program that runs an INSERT command via PpyPgSQL. It
returns a result of NONE and triggers no exception, but no row is added.
I grab the query that is being run and I run it directly from a Pgsql
client and it works fine.

Thoughts: I am using pyPgSQL-2.4 and built and installed it while we
were using postgress 7.3. Recently we upgraded to postgress 7.4, but I
did not rebuild or reinstall pyPgSQL. My code, which uses tons of
queries, never blinked due to the upgrade.

Perhaps I need to rebuild in order to get INSERT to work. (Another
possibility is that the build was funky and INSERT never did work and I
am only finding that out now.)

Any thoughts on any of this?

Rock

[Pypgsql-users] Weakrefs

[Brian Q. <br...@sw...>]

Is there a rational for the cursors only keeping weakrefs to the 
Connection object? I'm moving from MySQL and have a lot of code that is 
  similar to this:

cursor = connect(...).cursor().
cursor.execute(...)

This doesn't work with PyPgSQL because the cursor object doesn't keep 
the connection object alive.

Cheers,
Brian

[Pypgsql-users] array unicode decode

[Mignon, L. <Mi...@PC...>]

Hy,
When i passed to execute function a list with item(s) of arrray type as
parameter, array conent is not well unicode converted.
To solve this problem I have added the following lines to the
__unicodeConvert function

  def __unicodeConvert(self, obj):
	if type(obj) is StringType:
	    return obj
	elif type(obj) is UnicodeType:
	    return obj.encode(*self.conn.client_encoding)
	elif type(obj) in (ListType, TupleType):
	    converted_obj = []
	    for item in obj:
		if type(item) is UnicodeType:
	
converted_obj.append(item.encode(*self.conn.client_encoding))
		elif type(item) in (ListType,TupleType):
		    converted_obj.append( self.__unicodeConvert(item))
		else:
		    converted_obj.append(item)
	    return converted_obj
	elif type(obj) is DictType:
	    converted_obj = {}
	    for k, v in obj.items():
		if type(v) is UnicodeType:
		    converted_obj[k] = v.encode(*self.conn.client_encoding)
		else:
		    converted_obj[k] = v
	    return converted_obj
	elif isinstance(obj, PgResultSet):
	    obj = copy.copy(obj)
	    for k, v in obj.items():
		if type(v) is UnicodeType:
		    obj[k] = v.encode(*self.conn.client_encoding)
	    return obj
	else:
	    return obj 

Is it the good approach?

An other question, Why must I specify formally the keyword Array in the
query for the field of the array type.
"Insert into my_table (val1, array1) values (%s ARRAY%s)
thanks


Laurent Mignon
Software Engineer
Software AG Belgium
http://www.software-ag.com

Re: [Pypgsql-users] getting fetching messages...

[gerhard q. <gq...@sk...>]

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

Hi Alexander,

~  sorry, you're using the pygresql-Modul, not our pyPgSQL-Modul!

The needed function is getnotify(), which returns a message from your
server! Look in the manuals!

Gerhard
- -------------

Alexander Blüm wrote:
| On Wed, 31 Mar 2004 08:38:31 +0200
| gerhard quell <gq...@sk...> wrote:
|
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Do you mean:
|>
|>~ dbcon.notices() ?
|>
|>Gerhard
|>- ------------
|>Alexander Blüm wrote:
|>| hello,
|>|
|>| I almost pulled out all my hair over this.
|>|
|>| I have a simple INSERT INTO for a couple of values. there is a
|>trigger that
|>| skips the insertion and spits out an INFO line telling me that this
|>record is
|>| already in the table (_if_ it already is, otherwise the trigger
|>returns the
|>| to-be-inserted-row and stays quiet)
|>|
|>| I just want python to get these INFO-lines right after the query:
|>| 'INFO:  record already in table: text7112343o'
|>|
|>| this doesn't work:
|>| ...
|>| dbcon.query("BEGIN")
|>| for bla in dataarray:
|>|   insertstring="INSERT INTO testtable VALUES ('"+bla+"')"
|>|   dbcon.query(insertstring)
|>|   print "### ", dbcon.notifies()
|>| dbcon.query("COMMIT")
|>| ...
|>|
|>| Traceback (most recent call last):
|>|   File "import1.py", line 22, in ?
|>|     print "### ", dbcon.notifies()
|>| AttributeError: notifies
|>|
|>|
|>| ...why...?
|>|
|>| any help's greatly appreciated.
|>| alex.
|>|
|
|
|
| % python import1.py
| INFO:  record already in table: muh
| ###
| Traceback (most recent call last):
|   File "import1.py", line 22, in ?
|     print "### ", dbcon.notices()
| AttributeError: notices
|
|
| cheers,
|   Alex
|
|
| -------------------------------------------------------
| This SF.Net email is sponsored by: IBM Linux Tutorials
| Free Linux tutorial presented by Daniel Robbins, President and CEO of
| GenToo technologies. Learn everything from fundamentals to system
| administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
| _______________________________________________
| Pypgsql-users mailing list
| Pyp...@li...
| https://lists.sourceforge.net/lists/listinfo/pypgsql-users
|

- --
- ------------------------------------------------------ skequell ------
~ Gerhard Quell                       Software & Knowledge Engineering
~ Schützenweg 3      eMail:     gq...@sk...  Fon: 0731-26400651
~ 89275 Elchingen    web  : http://www.skequell.de  Fax: 0731-26400652
- --------------- pgp: 473EC53C  -  http://www.keyserver.net/en---------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAasZnvHbZD0c+xTwRAvWhAJ4u/RfYF8sYB/6cvkOrn4qn4QHazACZAYDn
5w6plDIj65556mNti5FRv38=
=CEeu
-----END PGP SIGNATURE-----

Re: [Pypgsql-users] getting fetching messages...

[Alexander <mai...@gm...>]

On Wed, 31 Mar 2004 08:38:31 +0200
gerhard quell <gq...@sk...> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Do you mean:
>=20
> ~ dbcon.notices() ?
>=20
> Gerhard
> - ------------
> Alexander Bl=FCm wrote:
> | hello,
> |
> | I almost pulled out all my hair over this.
> |
> | I have a simple INSERT INTO for a couple of values. there is a
> trigger that
> | skips the insertion and spits out an INFO line telling me that this
> record is
> | already in the table (_if_ it already is, otherwise the trigger
> returns the
> | to-be-inserted-row and stays quiet)
> |
> | I just want python to get these INFO-lines right after the query:
> | 'INFO:  record already in table: text7112343o'
> |
> | this doesn't work:
> | ...
> | dbcon.query("BEGIN")
> | for bla in dataarray:
> |   insertstring=3D"INSERT INTO testtable VALUES ('"+bla+"')"
> |   dbcon.query(insertstring)
> |   print "### ", dbcon.notifies()
> | dbcon.query("COMMIT")
> | ...
> |
> | Traceback (most recent call last):
> |   File "import1.py", line 22, in ?
> |     print "### ", dbcon.notifies()
> | AttributeError: notifies
> |
> |
> | ...why...?
> |
> | any help's greatly appreciated.
> | alex.
> |


% python import1.py=20
INFO:  record already in table: muh
###=20
Traceback (most recent call last):
  File "import1.py", line 22, in ?
    print "### ", dbcon.notices()
AttributeError: notices


cheers,
  Alex

[Pypgsql-users] getting fetching messages...

[<mai...@gm...>]

hello,

I almost pulled out all my hair over this.

I have a simple INSERT INTO for a couple of values. there is a trigger that
skips the insertion and spits out an INFO line telling me that this record is
already in the table (_if_ it already is, otherwise the trigger returns the
to-be-inserted-row and stays quiet)

I just want python to get these INFO-lines right after the query:
'INFO:  record already in table: text7112343o'

this doesn't work:
...
dbcon.query("BEGIN")
for bla in dataarray:
  insertstring="INSERT INTO testtable VALUES ('"+bla+"')"
  dbcon.query(insertstring)
  print "### ", dbcon.notifies()
dbcon.query("COMMIT")
...

Traceback (most recent call last):
  File "import1.py", line 22, in ?
    print "### ", dbcon.notifies()
AttributeError: notifies


...why...?

any help's greatly appreciated.
alex.

-- 
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz

[Pypgsql-users] Problems with the Zope PyPgSQL adaptor

[charlie c. <ch...@be...>]

Dear list,

I've been looking for a Python driver for PostgreSQL support and it seems 
that PyPgSQL is currently the only one to offer this. The driver seems to 
work fine so I tried the ZopeDA from CVS. This seems to have several 
problems: first of all I was not able to set up a connection using 
standard parameters:
e.g dbname=charlie host=localhost as the connection string
I get an error complaining that the database "dbname=charlie" doesn't 
exist. So I've hard-coded the connection string in db.py. It might be nice 
to know what I'm doing wrong.

The other error is that with or without unicode supports, result sets seem 
to have some kind of memory problem. Testing a single SELECT causing my 
system to run out of memory with Python swelling to well over 150 MB 
(probably more if I had the resources) and pg_ctl crashing at some point 
being unable to allocate heap to the child. I thought this might be 
related to unicode but it isn't.

System: Zope 2.6.2 (binary release, python 2.1, win32-x86), python 2.1.3, 
win32), PostgreSQL 7.4.1 for cygwin.

Any ideas?

Charlie

-- 
Charlie Clark
Helmholtzstr. 20
Düsseldorf
D-40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226

Re: [Pypgsql-users] License and redistribution.

[Mike C. F. <mcf...@ro...>]

What you are seeing there is the "CWI Python License" or the "CWI 
permissions statement and disclaimer", which is the basis on which the 
CNRI and later the PSF Python licences were built.  If you can use 
Python in your app, you can use a piece of software licensed under that 
license, (if only considering the licenses).

HTH,
Mike

Obviously, I'm not a lawyer :) .

jb...@ya... wrote:

>I'm looking at using Twisted for a commercial application, this may
>involve distribution pyPgSQL with our application.  While the license
>looks very BSD like, there is the clause "without fee".
>
>Is the intention here to now allow distribution of pyPgSQL with
>commercial (read, $$)?
>
>There are no issues with Twisted as its LGPL.
>
>Thanks.
>  
>
_______________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://members.rogers.com/mcfletch/

Re: [Pypgsql-users] License and redistribution.

[Billy G. A. <bil...@mu...>]

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

jb...@ya... wrote:
| I'm looking at using Twisted for a commercial application, this may
| involve distribution pyPgSQL with our application.  While the license
| looks very BSD like, there is the clause "without fee".
|
| Is the intention here to now allow distribution of pyPgSQL with
| commercial (read, $$)?
|
No, it just means that you can distribute it without paying a fee to do so.

- --
____       | Billy G. Allie    | Domain....: Bil...@mu...
|  /|      | 7436 Hartwell     | MSN.......: B_G...@em...
|-/-|----- | Dearborn, MI 48126|
|/  |LLIE  | (313) 582-1540    |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFARrRPnmIkMXoVVdURAg8aAJ4pzJinUN82ZbxWs0lyLlrxz/jPlQCbBQXI
YnuRZf1JD8UEb7PG2pEyA8M=
=FAzH
-----END PGP SIGNATURE-----

[Pypgsql-users] License and redistribution.

[<jb...@ya...>]

I'm looking at using Twisted for a commercial application, this may
involve distribution pyPgSQL with our application.  While the license
looks very BSD like, there is the clause "without fee".

Is the intention here to now allow distribution of pyPgSQL with
commercial (read, $$)?

There are no issues with Twisted as its LGPL.

Thanks.

Re: [Pypgsql-users] Installation in README.

[gerhard q. <gq...@sk...>]

Hi,

  look in your postgresql library (typically /usr/local/lib/psql):
#ls libpq*
libpq.a  libpq.so  libpq.so.3  libpq.so.3.0  libpq.so.3.1

Gerhard
-------------
Andrzej Dabrowski wrote:
> Hi!
> 
> I think that in file README.txt in chapter INSTALLATION it should be one 
> point more. I installed pyPgSQL without any problems but when I tried 
> run example script "basic.py"...
> 
> [postgres@localhost python]$ python basic.py
> Traceback (most recent call last):
>   File "./basic.py", line 3, in ?
>     from pyPgSQL import PgSQL
>   File "/usr/lib/python2.2/site-packages/pyPgSQL/PgSQL.py", line 391, in ?
>     from libpq import *
>   File "/usr/lib/python2.2/site-packages/pyPgSQL/libpq/__init__.py", 
> line 23, in ?
>     from libpq import *
> ImportError: libpq.so.3: cannot open shared object file: No such file or 
> directory
> 
> It is a problem and some people had the same one. It is an answer for 
> this problem. In file /etc/ld.so.conf one should write 
> "/usr/local/pgsql/lib/" and run ldconfig.
> 
> I think that it should be in README file.
> 
> Andrew
> 
> PS I'm Polish, so my English isn't very good :P
> 


-- 
------------------------------------------------------ skequell ------
  Gerhard Quell                       Software & Knowledge Engineering
  Schützenweg 3      eMail:     gq...@sk...  Fon: 0731-26400651
  89275 Elchingen    web  : http://www.skequell.de  Fax: 0731-26400652
--------------- pgp: 473EC53C  -  http://www.keyserver.net/en---------

[Pypgsql-users] Installation in README.

[Andrzej D. <and...@o2...>]

Hi!

I think that in file README.txt in chapter INSTALLATION it should be one 
point more. I installed pyPgSQL without any problems but when I tried 
run example script "basic.py"...

[postgres@localhost python]$ python basic.py
Traceback (most recent call last):
   File "./basic.py", line 3, in ?
     from pyPgSQL import PgSQL
   File "/usr/lib/python2.2/site-packages/pyPgSQL/PgSQL.py", line 391, in ?
     from libpq import *
   File "/usr/lib/python2.2/site-packages/pyPgSQL/libpq/__init__.py", 
line 23, in ?
     from libpq import *
ImportError: libpq.so.3: cannot open shared object file: No such file or 
directory

It is a problem and some people had the same one. It is an answer for 
this problem. In file /etc/ld.so.conf one should write 
"/usr/local/pgsql/lib/" and run ldconfig.

I think that it should be in README file.

Andrew

PS I'm Polish, so my English isn't very good :P

[Pypgsql-users] ImportError: /usr/lib/python2.2/.../pyPgSQL/libpq/libpqmodule.so: undefined symb

[Andres N. <mas...@ho...>]

<html><div style='background-color:'><P><BR><BR></P>
<DIV>
<DIV class=RTE>
<P>Hello, I have installed in my machine Linux Red Hat 7.3 with the following packages:</P>
<P>postgresql-docs-7.2.1-2PGDG<BR>postgresql-contrib-7.2.1-2PGDG<BR>postgresql-python-7.2.1-2PGDG<BR>postgresql-tk-7.2.1-2PGDG<BR>postgresql-jdbc-7.2.1-2PGDG<BR>postgresql-7.2.1-2PGDG<BR>postgresql-devel-7.2.1-2PGDG<BR>postgresql-perl-7.2.1-2PGDG<BR>postgresql-server-7.2.1-2PGDG<BR>postgresql-test-7.2.1-2PGDG<BR>postgresql-libs-7.2.1-2PGDG<BR>postgresql-odbc-7.2.1-2PGDG<BR>postgresql-tcl-7.2.1-2PGDG</P>
<P><BR>egenix-mx-base-2.0.4-py2.2_1<BR>mx-2.0.3-1</P>
<P><BR>python-1.5.2-38<BR>python-xmlrpc-1.5.1-7.x.3<BR>rpm-python-4.0.4-7x.18<BR>postgresql-python-7.2.1-2PGDG<BR>pythonlib-1.23-1<BR>python-clap-1.0.0-3<BR>python-devel-2.2.1-17<BR>mod_python-2.7.8-2<BR>libxslt-python-1.0.33-1<BR>python2-2.2-16<BR>python-popt-0.8.8-7.x.2<BR>ibxml2-python-2.5.9-1</P>
<P>When I install the package pypgsql,from sources, it work fine with no problem, but when I try to install&nbsp; the test file in pypgsql; this show this error:</P>
<P><BR>[root@ns1 pypgsql]# python test/PgSQLTestCases.py<BR>Traceback (most recent call last):<BR>&nbsp; File "test/PgSQLTestCases.py", line 89, in ?<BR>&nbsp;&nbsp;&nbsp; from pyPgSQL import PgSQL<BR>&nbsp; File "/usr/lib/python2.2/site-packages/pyPgSQL/PgSQL.py", line 391, in ?<BR>&nbsp;&nbsp;&nbsp; from libpq import *<BR>&nbsp; File "/usr/lib/python2.2/site-packages/pyPgSQL/libpq/__init__.py", line 23, in ?<BR>&nbsp;&nbsp;&nbsp; from libpq import *<BR>ImportError: /usr/lib/python2.2/site-packages/pyPgSQL/libpq/libpqmodule.so: undefined symbol: PyUnicodeUCS2_EncodeDecimal</P>
<P><BR>Could someone give me an idea of how I can fix this problem?</P>
<P>Thank.<BR><BR></P></DIV></DIV></div><br clear=all><hr>MSN Amor <a href="http://g.msn.com/8HMBES/2752??PS=">Busca tu ½ naranja</a> </html>

Re: [Pypgsql-users] Problems installing on OpenBSD

[Mike C. F. <mcf...@ro...>]

IIRC, you need to update to a newer release of pyPgSQL.  The first error 
is probably a check that version is <= 7.3.  Second is, again IIRC, also 
fixed in newer versions.

HTH,
Mike

Tom Longson wrote:

>Hi, I'm trying to install pyPgSQL on openBSD, and having a few problems. Can
>anyone assist me getting pyPgSQL to pass the tests below? They don't really
>tell me anything useful unfortunately.
>
>Thanks,
>Tom Longson
>
>-bash-2.05b$ python /www/devel/pypgsql/test/PgSQLTestCases.py
>........................................F.F.......................
>======================================================================
>FAIL: CheckDoMoreResultObjectChecks (__main__.PgSQLTestCases)
>----------------------------------------------------------------------
>Traceback (most recent call last):
>  File "/www/devel/pypgsql/test/PgSQLTestCases.py", line 817, in
>CheckDoMoreResultObjectChecks
>    self.fail(msg)
>  File
>"/usr/ports/lang/python/2.2/w-python-2.2.1p1/fake-i386/usr/local/lib/python2
>.2/unittest.py", line 254, in fail
>    raise self.failureException, msg
>AssertionError: 7.4
>
>======================================================================
>FAIL: Test execute() with a singleton string as the parameter.
>----------------------------------------------------------------------
>Traceback (most recent call last):
>  File "/www/devel/pypgsql/test/PgSQLTestCases.py", line 639, in
>CheckExecuteWithSingleton
>    "Length of cur.description is %d, it should be %d." %
>  File
>"/usr/ports/lang/python/2.2/w-python-2.2.1p1/fake-i386/usr/local/lib/python2
>.2/unittest.py", line 286, in failUnlessEqual
>    raise self.failureException, \
>AssertionError: Length of cur.description is 11, it should be 4.
>
>----------------------------------------------------------------------
>Ran 66 tests in 0.840s
>
>FAILED (failures=2)
>  
>
 
_______________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://members.rogers.com/mcfletch/

[Pypgsql-users] Problems installing on OpenBSD

[Tom L. <ny...@es...>]

Hi, I'm trying to install pyPgSQL on openBSD, and having a few problems. Can
anyone assist me getting pyPgSQL to pass the tests below? They don't really
tell me anything useful unfortunately.

Thanks,
Tom Longson

-bash-2.05b$ python /www/devel/pypgsql/test/PgSQLTestCases.py
........................................F.F.......................
======================================================================
FAIL: CheckDoMoreResultObjectChecks (__main__.PgSQLTestCases)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/www/devel/pypgsql/test/PgSQLTestCases.py", line 817, in
CheckDoMoreResultObjectChecks
    self.fail(msg)
  File
"/usr/ports/lang/python/2.2/w-python-2.2.1p1/fake-i386/usr/local/lib/python2
.2/unittest.py", line 254, in fail
    raise self.failureException, msg
AssertionError: 7.4

======================================================================
FAIL: Test execute() with a singleton string as the parameter.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/www/devel/pypgsql/test/PgSQLTestCases.py", line 639, in
CheckExecuteWithSingleton
    "Length of cur.description is %d, it should be %d." %
  File
"/usr/ports/lang/python/2.2/w-python-2.2.1p1/fake-i386/usr/local/lib/python2
.2/unittest.py", line 286, in failUnlessEqual
    raise self.failureException, \
AssertionError: Length of cur.description is 11, it should be 4.

----------------------------------------------------------------------
Ran 66 tests in 0.840s

FAILED (failures=2)

Re: [Pypgsql-users] Problem with pyPgSQL 2.4 and PostgreSQL 7.4.1

[Shawn H. <har...@tb...>]

I had very similar (if not the same?) results with Postgres 7.4, so I'm
interested in how this is resolved.

Shawn

----- Original Message ----- 
From: "Simon Kagedal" <si...@jo...>
To: <pyp...@li...>
Sent: Monday, January 12, 2004 12:14 PM
Subject: [Pypgsql-users] Problem with pyPgSQL 2.4 and PostgreSQL 7.4.1


Hello!

I have earlier successfully used pyPgSQL 2.3 with PostgreSQL 7.1.3.
Now we upgraded PostgreSQL to 7.4.1, and my code stopped working.  I
upgraded pyPgSQL to 2.4.  Now I don't get error messages, but it's
still not working as it should.

It seems all select statements just return nothing.

The test suite gives me this output:

<snip>

Re: [Pypgsql-users] Problem with pyPgSQL 2.4 and PostgreSQL 7.4.1

[Simon K. <si...@jo...>]

Nevermind - I found the problem, and it was of course mine.  :)
(PostgreSQL update triggered a bug in my SQL code.)

Sorry for bothering you.

Greetings, Simon


On Mon, Jan 12, 2004 at 07:14:18PM +0100, Simon Kagedal wrote:
> Hello!
>=20
> I have earlier successfully used pyPgSQL 2.3 with PostgreSQL 7.1.3.
> Now we upgraded PostgreSQL to 7.4.1, and my code stopped working.  I
> upgraded pyPgSQL to 2.4.  Now I don't get error messages, but it's
> still not working as it should.
>=20
> It seems all select statements just return nothing.
>=20
> The test suite gives me this output:
>=20
> $ python2 software/pypgsql-2.4/test/PgSQLTestCases.py
> ........................................F.F.......................
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> FAIL: CheckDoMoreResultObjectChecks (__main__.PgSQLTestCases)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "software/pypgsql-2.4/test/PgSQLTestCases.py", line 817, in
> CheckDoMoreResultObjectChecks
>     self.fail(msg)
>   File "/var/tmp/python2-2.2-root/usr/lib/python2.2/unittest.py", line
> 254, in fail
>     raise self.failureException, msg
> AssertionError: 7.4
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> FAIL: Test execute() with a singleton string as the parameter.
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "software/pypgsql-2.4/test/PgSQLTestCases.py", line 639, in
> CheckExecuteWithSingleton
>     "Length of cur.description is %d, it should be %d." %
>   File "/var/tmp/python2-2.2-root/usr/lib/python2.2/unittest.py", line
> 286, in failUnlessEqual
>     raise self.failureException, \
> AssertionError: Length of cur.description is 11, it should be 4.
>=20
> ----------------------------------------------------------------------
> Ran 66 tests in 0.700s
>=20
> FAILED (failures=3D2)
> $=20
>=20
> Thanks for any help!
>=20
> --=20
> Simon K=E5gedal [ http://helgo.net/simon ] / H=F6rnan [ http://hornan.o=
rg ]
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users

--=20
Simon K=E5gedal [ http://helgo.net/simon ] / H=F6rnan [ http://hornan.org=
 ]

[Pypgsql-users] Problem with pyPgSQL 2.4 and PostgreSQL 7.4.1

[Simon K. <si...@jo...>]

Hello!

I have earlier successfully used pyPgSQL 2.3 with PostgreSQL 7.1.3.
Now we upgraded PostgreSQL to 7.4.1, and my code stopped working.  I
upgraded pyPgSQL to 2.4.  Now I don't get error messages, but it's
still not working as it should.

It seems all select statements just return nothing.

The test suite gives me this output:

$ python2 software/pypgsql-2.4/test/PgSQLTestCases.py
........................................F.F.......................
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
FAIL: CheckDoMoreResultObjectChecks (__main__.PgSQLTestCases)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "software/pypgsql-2.4/test/PgSQLTestCases.py", line 817, in
CheckDoMoreResultObjectChecks
    self.fail(msg)
  File "/var/tmp/python2-2.2-root/usr/lib/python2.2/unittest.py", line
254, in fail
    raise self.failureException, msg
AssertionError: 7.4

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
FAIL: Test execute() with a singleton string as the parameter.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "software/pypgsql-2.4/test/PgSQLTestCases.py", line 639, in
CheckExecuteWithSingleton
    "Length of cur.description is %d, it should be %d." %
  File "/var/tmp/python2-2.2-root/usr/lib/python2.2/unittest.py", line
286, in failUnlessEqual
    raise self.failureException, \
AssertionError: Length of cur.description is 11, it should be 4.

----------------------------------------------------------------------
Ran 66 tests in 0.700s

FAILED (failures=3D2)
$=20

Thanks for any help!

--=20
Simon K=E5gedal [ http://helgo.net/simon ] / H=F6rnan [ http://hornan.org=
 ]

Re: [Pypgsql-users] Interval Type Mapping

[Francois G. <fra...@cl...>]

Ooops, I've sent a buggy version of my patch :/

here is the correct one. (sorry for flooding)

On Fri, 9 Jan 2004 00:25:11 +0100
Karsten Hilbert wrote:

> > Well... I did it ! See attached patch.
> I support inclusion of the patch. Had the same problem when
> calculating due/overdue vaccinations for GnuMed.
> 
> Karsten
> -- 
> GPG key ID E4071346 @ wwwkeys.pgp.net
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users
> 

Re: [Pypgsql-users] Interval Type Mapping

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

> Well... I did it ! See attached patch.
I support inclusion of the patch. Had the same problem when
calculating due/overdue vaccinations for GnuMed.

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

Re: [Pypgsql-users] Interval Type Mapping

[Francois G. <fra...@cl...>]

Well... I did it ! See attached patch.


On Thu, 18 Dec 2003 18:29:10 +0100
Francois Girault wrote:

> Hi all,
>=20
> I'm using interval data type in postgres.
>=20
> pypgsql returns a DateTimeDelta instance when retrieving such values.
>=20
> Is there any plan to use RelativeDateTime, cause interval <->
> DateTimeDelta is destructive on client side.
>=20
> With DateTimeDelta, years can't be specified and all years haven't 365
> days. Even saying a year is  365.2425 days, working with months is worse
> :(
>=20
> Any turn-around ?=20
>=20
> Or, if I want to do it myself, is interval2DateTimeDelta the only place
> to look at for returning RelativeDateTime instead of DateTimeDelta ?
>=20
> Thanks for any help.
>=20
> Fran=E7ois=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dclick
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users
>=20

Re: [Pypgsql-users] OpenBSD3.4 + Python 2.3.3 + pyPgSQL 2.4 Error

[Sean E. <se...@es...>]

Billy,

I installed pyPgSQL using python distutils 'python setup.py install'

The only thing I had to do was point the setup.py to the correct pgsql 
include and lib dirs.

There were no errors during build/install.

I forgot to mention I'm running PostgreSQL 7.4.1

As a note, I can 'import pyPgSQL' just fine, probably because it's not 
accessing the PgSQL module.

Thanks for your reply. I hope we can solve *something* with this odd 
occurrence.

--Sean

On Jan 7, 2004, at 8:12 PM, Billy G. Allie wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sean Escex wrote:
> | I have successfully installed pyPgSQL 2.4 on a OpenBSD3.4 system 
> running
> | Python 2.3.3, but encounter a strange error.
> |
> |  From python, when:
> |
> | from pyPgSQL import PgSQL
> |
> | is executed, the interpreter simple dies and I am taken back to the
> | command line. This is regardless if I'm doing it by hand in the
> | interpreter or have the 'from pyPgSQL import PgSQL' statement inside 
> a
> | python file.
> |
> | I attempted to check the archives, but there was an error.
> |
> | Any ideas on what this is, or how to obtain some sort of error log? 
> (I
> | assume there's some general error log where the error may be caught, 
> I'm
> | just not *nix savvy enough to know it.)
> |
> | Thanks,
> | --Sean
>
> Sean,
>
> Thats a strange one.  The only thing I can think of is an error in 
> libpq
> (the C language module).
>
> How did you install pyPgSQL?
> ~  - Did you compile from the source files?
> ~  - Were there any errors compiling the source?
>
> - --
> ____       | Billy G. Allie    | Domain....: Bil...@mu...
> |  /|      | 7436 Hartwell     | MSN.......: B_G...@em...
> |-/-|----- | Dearborn, MI 48126|
> |/  |LLIE  | (313) 582-1540    |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQE//NjGnmIkMXoVVdURAl1HAJ483JjWdv6pnkfnXXp1Hp9/yWjw9wCdFGxC
> 2hW0mTlHMLCenZxm9UydVGo=
> =jgaP
> -----END PGP SIGNATURE-----
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users
>

Re: [Pypgsql-users] OpenBSD3.4 + Python 2.3.3 + pyPgSQL 2.4 Error

[Billy G. A. <bil...@mu...>]

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

Sean Escex wrote:
| I have successfully installed pyPgSQL 2.4 on a OpenBSD3.4 system running
| Python 2.3.3, but encounter a strange error.
|
|  From python, when:
|
| from pyPgSQL import PgSQL
|
| is executed, the interpreter simple dies and I am taken back to the
| command line. This is regardless if I'm doing it by hand in the
| interpreter or have the 'from pyPgSQL import PgSQL' statement inside a
| python file.
|
| I attempted to check the archives, but there was an error.
|
| Any ideas on what this is, or how to obtain some sort of error log? (I
| assume there's some general error log where the error may be caught, I'm
| just not *nix savvy enough to know it.)
|
| Thanks,
| --Sean

Sean,

Thats a strange one.  The only thing I can think of is an error in libpq
(the C language module).

How did you install pyPgSQL?
~  - Did you compile from the source files?
~  - Were there any errors compiling the source?

- --
____       | Billy G. Allie    | Domain....: Bil...@mu...
|  /|      | 7436 Hartwell     | MSN.......: B_G...@em...
|-/-|----- | Dearborn, MI 48126|
|/  |LLIE  | (313) 582-1540    |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE//NjGnmIkMXoVVdURAl1HAJ483JjWdv6pnkfnXXp1Hp9/yWjw9wCdFGxC
2hW0mTlHMLCenZxm9UydVGo=
=jgaP
-----END PGP SIGNATURE-----