Menu
▾
▴
pypgsql-devel — List for discussion of pyPgSQL development.
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(4) |
Aug
(9) |
Sep
(22) |
Oct
(21) |
Nov
(20) |
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
(5) |
Mar
(30) |
Apr
(1) |
May
(5) |
Jun
(5) |
Jul
(2) |
Aug
(1) |
Sep
(2) |
Oct
(13) |
Nov
(7) |
Dec
(11) |
| 2004 |
Jan
(5) |
Feb
(6) |
Mar
(6) |
Apr
(2) |
May
(4) |
Jun
(2) |
Jul
(10) |
Aug
(17) |
Sep
(6) |
Oct
(10) |
Nov
(3) |
Dec
|
| 2005 |
Jan
(1) |
Feb
(29) |
Mar
(6) |
Apr
(5) |
May
(5) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
|
Oct
(5) |
Nov
|
Dec
|
| 2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(27) |
Jul
(2) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(3) |
| 2007 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(9) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(7) |
| 2008 |
Jan
|
Feb
|
Mar
(4) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <no...@so...> - 2002-09-20 05:12:46
|
Bugs item #611979, was opened at 2002-09-20 01:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611979&group_id=16528 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: CREATE DATABASE impossible? Initial Comment: It appears that the current code-base makes a create-database call impossible. Basically, the call can't happen within a transaction, so the default operation of wrapping everything in a transaction prevents the operation from working. I'm new to the project, but this would seem to be a minimal workaround: #378 re_CREATEDB = re.compile('[\s]*CREATE[\s]+DATABASE[\s]', re.I) #2518 _badQuery = re_CREATEDB.search(query) or ( (self.conn.version < 70100) and \ (re_DRT.search(query) or re_DRI.search(query) ) ) However, that doesn't address any other potential calls that need a non-transactional framework. Not sure how you'd want to do this in the general case (probably another method would be required). Enjoy, and thanks for the module, Mike ---------------------------------------------------------------------- Comment By: Mike C. Fletcher (mcfletch) Date: 2002-09-20 01:12 Message: Logged In: YES user_id=34901 Sorry, this report was from me, just forgot to log in first. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611979&group_id=16528 |
|
From: <no...@so...> - 2002-09-20 05:11:44
|
Bugs item #611979, was opened at 2002-09-19 22:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611979&group_id=16528 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: CREATE DATABASE impossible? Initial Comment: It appears that the current code-base makes a create-database call impossible. Basically, the call can't happen within a transaction, so the default operation of wrapping everything in a transaction prevents the operation from working. I'm new to the project, but this would seem to be a minimal workaround: #378 re_CREATEDB = re.compile('[\s]*CREATE[\s]+DATABASE[\s]', re.I) #2518 _badQuery = re_CREATEDB.search(query) or ( (self.conn.version < 70100) and \ (re_DRT.search(query) or re_DRI.search(query) ) ) However, that doesn't address any other potential calls that need a non-transactional framework. Not sure how you'd want to do this in the general case (probably another method would be required). Enjoy, and thanks for the module, Mike ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611979&group_id=16528 |
|
From: <no...@so...> - 2002-09-19 12:22:12
|
Feature Requests item #481716, was opened at 2001-11-14 16:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=366528&aid=481716&group_id=16528 Category: None Group: None >Status: Closed Priority: 3 Submitted By: Sergei Barbarash (sgt) Assigned to: Billy G. Allie (ballie01) Summary: PgResultSet: more dict behaviour Initial Comment: Would be nice if PgResultSet emulated more of the regular Python dictionary behaviour - like method get(key, default_value) or method __del__. BTW, why not use UserDict? ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-08 16:32 Message: Logged In: YES user_id=163326 Because of the optimization I did for PgResultSet, we cannot support __delitem__. I just made a few changes to PgResultSet that I'll commit shortly. Among them is that using a default value for get() is now supported. ---------------------------------------------------------------------- Comment By: Billy G. Allie (ballie01) Date: 2001-11-15 19:11 Message: Logged In: YES user_id=8500 As to why I didn't use one the available dictionary wrappers: basicly, I wanted more capability than just being able to access the results as a dictionary (i.e. being able to access results via the column name as an attribute to the result set). Also, the result set contains a copy of the cursor.description attribute (accessable via the description method of the result set). This makes the result set a stand-alone object once it's created. You don't need the cursor to access the information that is in the description. You can also slice data out of the result set and the description information for the sliced columns is in the resulting result set. BTW: You can always tell PgSQL to return a Python list instead of a pgResultSet and use the various dictionary wrappers to provide the dictionary access. ---------------------------------------------------------------------- Comment By: Sergei Barbarash (sgt) Date: 2001-11-14 16:43 Message: Logged In: YES user_id=58905 err I meant __delitem__ <code> def get(self, key, default): if self.has_key(key): return self[key] else: return default def __delitem__(self, key): del self._xlatkey[key] </code> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=366528&aid=481716&group_id=16528 |
|
From: <no...@so...> - 2002-09-19 12:20:23
|
Patches item #605455, was opened at 2002-09-06 09:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 Category: None Group: None >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Sean Reifschneider (jafo) Assigned to: Gerhard Häring (ghaering) Summary: RPM .spec file for 2.2. Initial Comment: I'm uploading a .spec file for creating RPMs. I've tweeked this from the one I got with a version of 2.0. The RPM and SRPM for pyPgSQL and egenix-mx-base (built correctly for the Red Hat python 2.2) at: ftp://ftp.tummy.com/pub/tummy/RPMS/SRPMS/ ftp://ftp.tummy.com/pub/tummy/RPMS/binaries-KRUD-7.3-i386/ If you include this .spec file in the base .tar file, and update the version number in it as appropriate, users will be able to build RPMs directly from the tar file with "rpm -ta pypgsql-version.tar.gz". Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-09-09 00:12 Message: Logged In: YES user_id=81797 Ugh, the last one didn't fix paths in the examples. Use this one instead, please. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-09-08 23:52 Message: Logged In: YES user_id=81797 Thanks for the suggestions. They are implemented in this file. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-08 17:32 Message: Logged In: YES user_id=163326 Committed, thanks. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-06 10:04 Message: Logged In: YES user_id=163326 Thanks. A few ideas for improvement: no %doc for README and examples no runtime dependency on PostgreSQL-client or Python no build dependency on PostgreSQL-devel or Python-devel The argument against adding too many dependencies is that these RPMs are probably named slightly different on stock Redhat, KRUD, and in the postgresql.org RPMs. Do you think these should be added? I'll try to test this and add it later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 |
|
From: <no...@so...> - 2002-09-19 12:18:02
|
Bugs item #611483, was opened at 2002-09-19 11:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611483&group_id=16528 Category: PgSQL Group: None Status: Open >Resolution: Invalid Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Gerhard Häring (ghaering) Summary: NULL not represented by Python None Initial Comment: According to the Database API 2.0, "SQL NULL values are represented by the Python None singleton on input and output." This doesn't seem to be the case: INSERT INTO "XXX" ("foo", "bar", "baz", "bop") VALUES ('boo', None, None, None) Traceback (most recent call last): File "XXX.py", line 90, in ? print XYZ_add() File "XXX.py", line 33, in ZZZ self.add_XYZ() File "XXX.py", line 25, in YYY self.cursor.execute(SQL) File "/usr/lib/python2.1/site-packages/pyPgSQL/PgSQL.py", line 2135, in execute raise OperationalError, msg libpq.OperationalError: ERROR: Attribute 'none' not found ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-09-19 14:18 Message: Logged In: YES user_id=163326 Don't put None literally in SQL. If you want NULL in a SQL string, put NULL in ;-) You can, however, use Python Nones when binding parameters to your SQL statement, like this: cursor.execute(""" INSERT INTO MYTABLE (MYCOLUMN) VALUES (%s) """, (None,)) HTH ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611483&group_id=16528 |
|
From: <no...@so...> - 2002-09-19 09:09:08
|
Bugs item #611483, was opened at 2002-09-19 02:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611483&group_id=16528 Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: NULL not represented by Python None Initial Comment: According to the Database API 2.0, "SQL NULL values are represented by the Python None singleton on input and output." This doesn't seem to be the case: INSERT INTO "XXX" ("foo", "bar", "baz", "bop") VALUES ('boo', None, None, None) Traceback (most recent call last): File "XXX.py", line 90, in ? print XYZ_add() File "XXX.py", line 33, in ZZZ self.add_XYZ() File "XXX.py", line 25, in YYY self.cursor.execute(SQL) File "/usr/lib/python2.1/site-packages/pyPgSQL/PgSQL.py", line 2135, in execute raise OperationalError, msg libpq.OperationalError: ERROR: Attribute 'none' not found ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=611483&group_id=16528 |
|
From: <no...@so...> - 2002-09-08 22:12:18
|
Patches item #605455, was opened at 2002-09-06 07:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Submitted By: Sean Reifschneider (jafo) Assigned to: Gerhard Häring (ghaering) Summary: RPM .spec file for 2.2. Initial Comment: I'm uploading a .spec file for creating RPMs. I've tweeked this from the one I got with a version of 2.0. The RPM and SRPM for pyPgSQL and egenix-mx-base (built correctly for the Red Hat python 2.2) at: ftp://ftp.tummy.com/pub/tummy/RPMS/SRPMS/ ftp://ftp.tummy.com/pub/tummy/RPMS/binaries-KRUD-7.3-i386/ If you include this .spec file in the base .tar file, and update the version number in it as appropriate, users will be able to build RPMs directly from the tar file with "rpm -ta pypgsql-version.tar.gz". Sean ---------------------------------------------------------------------- >Comment By: Sean Reifschneider (jafo) Date: 2002-09-08 22:12 Message: Logged In: YES user_id=81797 Ugh, the last one didn't fix paths in the examples. Use this one instead, please. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-09-08 21:52 Message: Logged In: YES user_id=81797 Thanks for the suggestions. They are implemented in this file. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-08 15:32 Message: Logged In: YES user_id=163326 Committed, thanks. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-06 08:04 Message: Logged In: YES user_id=163326 Thanks. A few ideas for improvement: no %doc for README and examples no runtime dependency on PostgreSQL-client or Python no build dependency on PostgreSQL-devel or Python-devel The argument against adding too many dependencies is that these RPMs are probably named slightly different on stock Redhat, KRUD, and in the postgresql.org RPMs. Do you think these should be added? I'll try to test this and add it later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 |
|
From: <no...@so...> - 2002-09-08 21:52:06
|
Patches item #605455, was opened at 2002-09-06 07:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 Category: None Group: None >Status: Open Resolution: Accepted Priority: 5 Submitted By: Sean Reifschneider (jafo) Assigned to: Gerhard Häring (ghaering) >Summary: RPM .spec file for 2.2. Initial Comment: I'm uploading a .spec file for creating RPMs. I've tweeked this from the one I got with a version of 2.0. The RPM and SRPM for pyPgSQL and egenix-mx-base (built correctly for the Red Hat python 2.2) at: ftp://ftp.tummy.com/pub/tummy/RPMS/SRPMS/ ftp://ftp.tummy.com/pub/tummy/RPMS/binaries-KRUD-7.3-i386/ If you include this .spec file in the base .tar file, and update the version number in it as appropriate, users will be able to build RPMs directly from the tar file with "rpm -ta pypgsql-version.tar.gz". Sean ---------------------------------------------------------------------- >Comment By: Sean Reifschneider (jafo) Date: 2002-09-08 21:52 Message: Logged In: YES user_id=81797 Thanks for the suggestions. They are implemented in this file. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-08 15:32 Message: Logged In: YES user_id=163326 Committed, thanks. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-06 08:04 Message: Logged In: YES user_id=163326 Thanks. A few ideas for improvement: no %doc for README and examples no runtime dependency on PostgreSQL-client or Python no build dependency on PostgreSQL-devel or Python-devel The argument against adding too many dependencies is that these RPMs are probably named slightly different on stock Redhat, KRUD, and in the postgresql.org RPMs. Do you think these should be added? I'll try to test this and add it later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 |
|
From: <no...@so...> - 2002-09-08 15:33:28
|
Patches item #484468, was opened at 2001-11-22 07:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=484468&group_id=16528 Category: None Group: None Status: Open >Resolution: Postponed Priority: 5 Submitted By: Gerhard Häring (ghaering) Assigned to: Gerhard Häring (ghaering) Summary: Draft Unicode patch Initial Comment: Ok, here comes what I've done so far for adding Unicode support. Jjust to show what I've been talking about on the mailing list and by no means finished or bugfree. Bugs are (at least): - no checks if PostgreSQL multibyte support is available at all (compiles may perhaps fail) - for some reason, no exception is raised when setting the clientencoding fails ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-06-05 19:32 Message: Logged In: YES user_id=163326 I've now uploaded an updated patch that applies cleanly to pyPgSQL version 2.1. I'd be very grateful if those interested in Unicode support could test it and tell me (on the mailing list, preferrably) what should be done differently and which features are still missing, if any. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-04-16 05:18 Message: Logged In: YES user_id=163326 Hmm. The patch is pretty large. So one more comment: The only relevant addition is the __unicodeConvert() method in the Connection class. The other relevant changes can be found by grepping for "unicode". There's also cosmetic changes to the typechecking in this patch (always use "is" instead of "==" and "is not" instead of "!="). And also always compare to "None" with "is" - the comparison with "==" has bitten a pyPgSQL user once. The is-Check is more pythonic and slightly faster. Enough for today :) ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-04-16 05:06 Message: Logged In: YES user_id=163326 I'm publishing here my update to the patch. This patch is against the latest CVS version of pyPgSQL. It turns out that changes to libpq are not necessary at all. Some testing code is already there and I'm pretty confident that I'm on the right track with the current approach. More later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=484468&group_id=16528 |
|
From: <no...@so...> - 2002-09-08 15:32:07
|
Patches item #605455, was opened at 2002-09-06 09:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 Category: None Group: None >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Sean Reifschneider (jafo) Assigned to: Gerhard Häring (ghaering) Summary: RPM .spec file for 2.1. Initial Comment: I'm uploading a .spec file for creating RPMs. I've tweeked this from the one I got with a version of 2.0. The RPM and SRPM for pyPgSQL and egenix-mx-base (built correctly for the Red Hat python 2.2) at: ftp://ftp.tummy.com/pub/tummy/RPMS/SRPMS/ ftp://ftp.tummy.com/pub/tummy/RPMS/binaries-KRUD-7.3-i386/ If you include this .spec file in the base .tar file, and update the version number in it as appropriate, users will be able to build RPMs directly from the tar file with "rpm -ta pypgsql-version.tar.gz". Sean ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-09-08 17:32 Message: Logged In: YES user_id=163326 Committed, thanks. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-09-06 10:04 Message: Logged In: YES user_id=163326 Thanks. A few ideas for improvement: no %doc for README and examples no runtime dependency on PostgreSQL-client or Python no build dependency on PostgreSQL-devel or Python-devel The argument against adding too many dependencies is that these RPMs are probably named slightly different on stock Redhat, KRUD, and in the postgresql.org RPMs. Do you think these should be added? I'll try to test this and add it later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 |
|
From: <no...@so...> - 2002-09-08 14:32:46
|
Feature Requests item #481716, was opened at 2001-11-14 16:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=366528&aid=481716&group_id=16528 Category: None Group: None Status: Open Priority: 3 Submitted By: Sergei Barbarash (sgt) Assigned to: Billy G. Allie (ballie01) Summary: PgResultSet: more dict behaviour Initial Comment: Would be nice if PgResultSet emulated more of the regular Python dictionary behaviour - like method get(key, default_value) or method __del__. BTW, why not use UserDict? ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-09-08 16:32 Message: Logged In: YES user_id=163326 Because of the optimization I did for PgResultSet, we cannot support __delitem__. I just made a few changes to PgResultSet that I'll commit shortly. Among them is that using a default value for get() is now supported. ---------------------------------------------------------------------- Comment By: Billy G. Allie (ballie01) Date: 2001-11-15 19:11 Message: Logged In: YES user_id=8500 As to why I didn't use one the available dictionary wrappers: basicly, I wanted more capability than just being able to access the results as a dictionary (i.e. being able to access results via the column name as an attribute to the result set). Also, the result set contains a copy of the cursor.description attribute (accessable via the description method of the result set). This makes the result set a stand-alone object once it's created. You don't need the cursor to access the information that is in the description. You can also slice data out of the result set and the description information for the sliced columns is in the resulting result set. BTW: You can always tell PgSQL to return a Python list instead of a pgResultSet and use the various dictionary wrappers to provide the dictionary access. ---------------------------------------------------------------------- Comment By: Sergei Barbarash (sgt) Date: 2001-11-14 16:43 Message: Logged In: YES user_id=58905 err I meant __delitem__ <code> def get(self, key, default): if self.has_key(key): return self[key] else: return default def __delitem__(self, key): del self._xlatkey[key] </code> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=366528&aid=481716&group_id=16528 |
|
From: <no...@so...> - 2002-09-06 08:04:21
|
Patches item #605455, was opened at 2002-09-06 09:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sean Reifschneider (jafo) >Assigned to: Gerhard Häring (ghaering) Summary: RPM .spec file for 2.1. Initial Comment: I'm uploading a .spec file for creating RPMs. I've tweeked this from the one I got with a version of 2.0. The RPM and SRPM for pyPgSQL and egenix-mx-base (built correctly for the Red Hat python 2.2) at: ftp://ftp.tummy.com/pub/tummy/RPMS/SRPMS/ ftp://ftp.tummy.com/pub/tummy/RPMS/binaries-KRUD-7.3-i386/ If you include this .spec file in the base .tar file, and update the version number in it as appropriate, users will be able to build RPMs directly from the tar file with "rpm -ta pypgsql-version.tar.gz". Sean ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-09-06 10:04 Message: Logged In: YES user_id=163326 Thanks. A few ideas for improvement: no %doc for README and examples no runtime dependency on PostgreSQL-client or Python no build dependency on PostgreSQL-devel or Python-devel The argument against adding too many dependencies is that these RPMs are probably named slightly different on stock Redhat, KRUD, and in the postgresql.org RPMs. Do you think these should be added? I'll try to test this and add it later. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 |
|
From: <no...@so...> - 2002-09-06 07:13:31
|
Patches item #605455, was opened at 2002-09-06 07:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sean Reifschneider (jafo) Assigned to: Nobody/Anonymous (nobody) Summary: RPM .spec file for 2.1. Initial Comment: I'm uploading a .spec file for creating RPMs. I've tweeked this from the one I got with a version of 2.0. The RPM and SRPM for pyPgSQL and egenix-mx-base (built correctly for the Red Hat python 2.2) at: ftp://ftp.tummy.com/pub/tummy/RPMS/SRPMS/ ftp://ftp.tummy.com/pub/tummy/RPMS/binaries-KRUD-7.3-i386/ If you include this .spec file in the base .tar file, and update the version number in it as appropriate, users will be able to build RPMs directly from the tar file with "rpm -ta pypgsql-version.tar.gz". Sean ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=605455&group_id=16528 |
|
From: <no...@so...> - 2002-08-03 06:05:37
|
Bugs item #589370, was opened at 2002-07-31 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Gerhard Häring (ghaering) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-08-03 08:05 Message: Logged In: YES user_id=163326 Fixed in revision 1.13 of PgSQL.py. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-02 10:52 Message: Logged In: YES user_id=163326 I'm uploading a patch that is most likely all that's required to fix this bug (and it wasn't PostgreSQL's fault, which I was too quick to blame). ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-02 10:27 Message: Logged In: YES user_id=163326 I could produce a very minimal test case (see upload). Looks like a PostgreSQL bug that we have to work around: if OID is in the select statement, and the query doesn't produce any rows (_res.ntuples == 0), then _res.nfields != 0 because PostgreSQL says that it has returned an OID value, which it hasn't :-/ That's at least my interpretation for now. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-01 22:34 Message: Logged In: NO ERROR REPORT 31.07.2002 22:15 By Frank H. Raschke fr...@nk... Hello! I have some problems with pyPgSQL i'd like to mention: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. ################################################### #### DETAILS: The following Tables where created by a script using pgsql: CREATE TABLE "alletitel" ( "dauer" double precision NOT NULL, "dauertxt" character varying(10) NOT NULL, "title" character varying(150) NOT NULL, "genre" character varying(40) NOT NULL, "artist" character varying(150) NOT NULL, "album" character varying(150) NOT NULL, "bitrate" double precision NOT NULL, "jahr" character(4) NOT NULL, "track" integer NOT NULL, "filename" character varying(250) NOT NULL, "importstamp" timestamp with time zone NOT NULL ); CREATE INDEX alletitel_artist ON alletitel (artist); CREATE INDEX alletitel_artisttitle ON alletitel (artist,title); CREATE INDEX alletitel_title ON alletitel (title); CREATE TABLE "playlists" ( "playlist" integer NOT NULL, "item" integer NOT NULL, "name" character varying(40) NOT NULL, "kommentar" character varying(250) NOT NULL, "entry" integer NOT NULL ); CREATE INDEX playlists_playlistitem ON playlists (playlist,item); ################################################### #### The following statement was executed by "cursor.execute (statement)" where "alletitel" contained some rows but "playlists" was empty and so the result was of course empty too (important!) select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OID,b.Tr ack,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b.Album ,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item The real Source won't help you much, I think, because this statement is generated by the wrapper sqldb.py. The thing above is taken from a "print" of the query string. Identical query wors fine with mySQL... But if it helps, I can send you the little jukebox-app, but how can I do so ? Should I submit new ? Here I can't upload anymore.... ################################################### #### This results in the following error (Notice: There are the OIDs of both tables selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ################################################### #### Thank You Bye ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 09:08 Message: Logged In: YES user_id=163326 I can't reproduce the problem here with PostgreSQL 7.2.1, but will try later with a 7.1.3 at home. It'd still be ueful if you could upload your schema and code. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 08:55 Message: Logged In: YES user_id=163326 Thanks for your submission. Your attachment wasn't uploaded. Most probably you forgot to activate the checkbox titled "Check to Upload and Attach a File". This is a Sourceforge annoyance that we can do nothing about. Would you please upload your file again? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-08-02 08:54:14
|
Bugs item #589370, was opened at 2002-07-31 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Gerhard Häring (ghaering) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-02 10:52 Message: Logged In: YES user_id=163326 I'm uploading a patch that is most likely all that's required to fix this bug (and it wasn't PostgreSQL's fault, which I was too quick to blame). ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-02 10:27 Message: Logged In: YES user_id=163326 I could produce a very minimal test case (see upload). Looks like a PostgreSQL bug that we have to work around: if OID is in the select statement, and the query doesn't produce any rows (_res.ntuples == 0), then _res.nfields != 0 because PostgreSQL says that it has returned an OID value, which it hasn't :-/ That's at least my interpretation for now. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-01 22:34 Message: Logged In: NO ERROR REPORT 31.07.2002 22:15 By Frank H. Raschke fr...@nk... Hello! I have some problems with pyPgSQL i'd like to mention: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. ################################################### #### DETAILS: The following Tables where created by a script using pgsql: CREATE TABLE "alletitel" ( "dauer" double precision NOT NULL, "dauertxt" character varying(10) NOT NULL, "title" character varying(150) NOT NULL, "genre" character varying(40) NOT NULL, "artist" character varying(150) NOT NULL, "album" character varying(150) NOT NULL, "bitrate" double precision NOT NULL, "jahr" character(4) NOT NULL, "track" integer NOT NULL, "filename" character varying(250) NOT NULL, "importstamp" timestamp with time zone NOT NULL ); CREATE INDEX alletitel_artist ON alletitel (artist); CREATE INDEX alletitel_artisttitle ON alletitel (artist,title); CREATE INDEX alletitel_title ON alletitel (title); CREATE TABLE "playlists" ( "playlist" integer NOT NULL, "item" integer NOT NULL, "name" character varying(40) NOT NULL, "kommentar" character varying(250) NOT NULL, "entry" integer NOT NULL ); CREATE INDEX playlists_playlistitem ON playlists (playlist,item); ################################################### #### The following statement was executed by "cursor.execute (statement)" where "alletitel" contained some rows but "playlists" was empty and so the result was of course empty too (important!) select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OID,b.Tr ack,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b.Album ,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item The real Source won't help you much, I think, because this statement is generated by the wrapper sqldb.py. The thing above is taken from a "print" of the query string. Identical query wors fine with mySQL... But if it helps, I can send you the little jukebox-app, but how can I do so ? Should I submit new ? Here I can't upload anymore.... ################################################### #### This results in the following error (Notice: There are the OIDs of both tables selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ################################################### #### Thank You Bye ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 09:08 Message: Logged In: YES user_id=163326 I can't reproduce the problem here with PostgreSQL 7.2.1, but will try later with a 7.1.3 at home. It'd still be ueful if you could upload your schema and code. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 08:55 Message: Logged In: YES user_id=163326 Thanks for your submission. Your attachment wasn't uploaded. Most probably you forgot to activate the checkbox titled "Check to Upload and Attach a File". This is a Sourceforge annoyance that we can do nothing about. Would you please upload your file again? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-08-02 08:53:04
|
Bugs item #589370, was opened at 2002-07-31 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Gerhard Häring (ghaering) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-08-02 10:52 Message: Logged In: YES user_id=163326 I'm uploading a patch that is most likely all that's required to fix this bug (and it wasn't PostgreSQL's fault, which I was too quick to blame). ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-02 10:27 Message: Logged In: YES user_id=163326 I could produce a very minimal test case (see upload). Looks like a PostgreSQL bug that we have to work around: if OID is in the select statement, and the query doesn't produce any rows (_res.ntuples == 0), then _res.nfields != 0 because PostgreSQL says that it has returned an OID value, which it hasn't :-/ That's at least my interpretation for now. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-01 22:34 Message: Logged In: NO ERROR REPORT 31.07.2002 22:15 By Frank H. Raschke fr...@nk... Hello! I have some problems with pyPgSQL i'd like to mention: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. ################################################### #### DETAILS: The following Tables where created by a script using pgsql: CREATE TABLE "alletitel" ( "dauer" double precision NOT NULL, "dauertxt" character varying(10) NOT NULL, "title" character varying(150) NOT NULL, "genre" character varying(40) NOT NULL, "artist" character varying(150) NOT NULL, "album" character varying(150) NOT NULL, "bitrate" double precision NOT NULL, "jahr" character(4) NOT NULL, "track" integer NOT NULL, "filename" character varying(250) NOT NULL, "importstamp" timestamp with time zone NOT NULL ); CREATE INDEX alletitel_artist ON alletitel (artist); CREATE INDEX alletitel_artisttitle ON alletitel (artist,title); CREATE INDEX alletitel_title ON alletitel (title); CREATE TABLE "playlists" ( "playlist" integer NOT NULL, "item" integer NOT NULL, "name" character varying(40) NOT NULL, "kommentar" character varying(250) NOT NULL, "entry" integer NOT NULL ); CREATE INDEX playlists_playlistitem ON playlists (playlist,item); ################################################### #### The following statement was executed by "cursor.execute (statement)" where "alletitel" contained some rows but "playlists" was empty and so the result was of course empty too (important!) select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OID,b.Tr ack,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b.Album ,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item The real Source won't help you much, I think, because this statement is generated by the wrapper sqldb.py. The thing above is taken from a "print" of the query string. Identical query wors fine with mySQL... But if it helps, I can send you the little jukebox-app, but how can I do so ? Should I submit new ? Here I can't upload anymore.... ################################################### #### This results in the following error (Notice: There are the OIDs of both tables selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ################################################### #### Thank You Bye ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 09:08 Message: Logged In: YES user_id=163326 I can't reproduce the problem here with PostgreSQL 7.2.1, but will try later with a 7.1.3 at home. It'd still be ueful if you could upload your schema and code. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 08:55 Message: Logged In: YES user_id=163326 Thanks for your submission. Your attachment wasn't uploaded. Most probably you forgot to activate the checkbox titled "Check to Upload and Attach a File". This is a Sourceforge annoyance that we can do nothing about. Would you please upload your file again? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-08-02 08:27:35
|
Bugs item #589370, was opened at 2002-07-31 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Gerhard Häring (ghaering) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-08-02 10:27 Message: Logged In: YES user_id=163326 I could produce a very minimal test case (see upload). Looks like a PostgreSQL bug that we have to work around: if OID is in the select statement, and the query doesn't produce any rows (_res.ntuples == 0), then _res.nfields != 0 because PostgreSQL says that it has returned an OID value, which it hasn't :-/ That's at least my interpretation for now. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-01 22:34 Message: Logged In: NO ERROR REPORT 31.07.2002 22:15 By Frank H. Raschke fr...@nk... Hello! I have some problems with pyPgSQL i'd like to mention: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. ################################################### #### DETAILS: The following Tables where created by a script using pgsql: CREATE TABLE "alletitel" ( "dauer" double precision NOT NULL, "dauertxt" character varying(10) NOT NULL, "title" character varying(150) NOT NULL, "genre" character varying(40) NOT NULL, "artist" character varying(150) NOT NULL, "album" character varying(150) NOT NULL, "bitrate" double precision NOT NULL, "jahr" character(4) NOT NULL, "track" integer NOT NULL, "filename" character varying(250) NOT NULL, "importstamp" timestamp with time zone NOT NULL ); CREATE INDEX alletitel_artist ON alletitel (artist); CREATE INDEX alletitel_artisttitle ON alletitel (artist,title); CREATE INDEX alletitel_title ON alletitel (title); CREATE TABLE "playlists" ( "playlist" integer NOT NULL, "item" integer NOT NULL, "name" character varying(40) NOT NULL, "kommentar" character varying(250) NOT NULL, "entry" integer NOT NULL ); CREATE INDEX playlists_playlistitem ON playlists (playlist,item); ################################################### #### The following statement was executed by "cursor.execute (statement)" where "alletitel" contained some rows but "playlists" was empty and so the result was of course empty too (important!) select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OID,b.Tr ack,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b.Album ,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item The real Source won't help you much, I think, because this statement is generated by the wrapper sqldb.py. The thing above is taken from a "print" of the query string. Identical query wors fine with mySQL... But if it helps, I can send you the little jukebox-app, but how can I do so ? Should I submit new ? Here I can't upload anymore.... ################################################### #### This results in the following error (Notice: There are the OIDs of both tables selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ################################################### #### Thank You Bye ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 09:08 Message: Logged In: YES user_id=163326 I can't reproduce the problem here with PostgreSQL 7.2.1, but will try later with a 7.1.3 at home. It'd still be ueful if you could upload your schema and code. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 08:55 Message: Logged In: YES user_id=163326 Thanks for your submission. Your attachment wasn't uploaded. Most probably you forgot to activate the checkbox titled "Check to Upload and Attach a File". This is a Sourceforge annoyance that we can do nothing about. Would you please upload your file again? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-08-02 01:40:07
|
Bugs item #589270, was opened at 2002-07-31 14:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589270&group_id=16528 Category: PgInt8 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Billy G. Allie (ballie01) Summary: strtoll strtoull not in Compac C on OSF Initial Comment: The routines to convert strings to signed and unsigned long longs, strtoll, strtoull, do not seem to available in Compaq C V6.1-123 on Digital UNIX V4.0G (Rev. 1530) (and not part of ANSI C). The package then does not build properly on our ALPHA OSF 1 V4.0 1530. ---------------------------------------------------------------------- >Comment By: Billy G. Allie (ballie01) Date: 2002-08-01 21:40 Message: Logged In: YES user_id=8500 I think we should rename the functions to pg_strtoll and pg_strtoull and always use those. When can then avoid the special casing of setup.py as you suggested. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 03:15 Message: Logged In: YES user_id=163326 Billy, what do we do in this case? Use the stuff from the windows/ directory? Anonymous, could you please post what >>> import sys, os >>> print sys.platform >>> print os.name prints on your DEC machine? On a very old box I have access to, this prints: 'osf1V4' and 'posix'. Another possibility is to rename the functions in the windows/ directory, to avoid name conflicts with libc stuff on other platforms, and *always* use our own implementations. Maybe that's preferrable to special-case for the dozens of Unices out there. Anonymous, as a temporary workaround you can use the functions in the windows/ directory. You'll need to change setup.py so that these get linked in, just search for how it's done for the win32 platform. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589270&group_id=16528 |
|
From: <no...@so...> - 2002-08-01 20:34:58
|
Bugs item #589370, was opened at 2002-07-31 14:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-01 13:34 Message: Logged In: NO ERROR REPORT 31.07.2002 22:15 By Frank H. Raschke fr...@nk... Hello! I have some problems with pyPgSQL i'd like to mention: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. ################################################### #### DETAILS: The following Tables where created by a script using pgsql: CREATE TABLE "alletitel" ( "dauer" double precision NOT NULL, "dauertxt" character varying(10) NOT NULL, "title" character varying(150) NOT NULL, "genre" character varying(40) NOT NULL, "artist" character varying(150) NOT NULL, "album" character varying(150) NOT NULL, "bitrate" double precision NOT NULL, "jahr" character(4) NOT NULL, "track" integer NOT NULL, "filename" character varying(250) NOT NULL, "importstamp" timestamp with time zone NOT NULL ); CREATE INDEX alletitel_artist ON alletitel (artist); CREATE INDEX alletitel_artisttitle ON alletitel (artist,title); CREATE INDEX alletitel_title ON alletitel (title); CREATE TABLE "playlists" ( "playlist" integer NOT NULL, "item" integer NOT NULL, "name" character varying(40) NOT NULL, "kommentar" character varying(250) NOT NULL, "entry" integer NOT NULL ); CREATE INDEX playlists_playlistitem ON playlists (playlist,item); ################################################### #### The following statement was executed by "cursor.execute (statement)" where "alletitel" contained some rows but "playlists" was empty and so the result was of course empty too (important!) select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OID,b.Tr ack,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b.Album ,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item The real Source won't help you much, I think, because this statement is generated by the wrapper sqldb.py. The thing above is taken from a "print" of the query string. Identical query wors fine with mySQL... But if it helps, I can send you the little jukebox-app, but how can I do so ? Should I submit new ? Here I can't upload anymore.... ################################################### #### This results in the following error (Notice: There are the OIDs of both tables selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ################################################### #### Thank You Bye ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 00:08 Message: Logged In: YES user_id=163326 I can't reproduce the problem here with PostgreSQL 7.2.1, but will try later with a 7.1.3 at home. It'd still be ueful if you could upload your schema and code. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-07-31 23:55 Message: Logged In: YES user_id=163326 Thanks for your submission. Your attachment wasn't uploaded. Most probably you forgot to activate the checkbox titled "Check to Upload and Attach a File". This is a Sourceforge annoyance that we can do nothing about. Would you please upload your file again? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-08-01 07:15:52
|
Bugs item #589270, was opened at 2002-07-31 20:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589270&group_id=16528 Category: PgInt8 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Billy G. Allie (ballie01) Summary: strtoll strtoull not in Compac C on OSF Initial Comment: The routines to convert strings to signed and unsigned long longs, strtoll, strtoull, do not seem to available in Compaq C V6.1-123 on Digital UNIX V4.0G (Rev. 1530) (and not part of ANSI C). The package then does not build properly on our ALPHA OSF 1 V4.0 1530. ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 09:15 Message: Logged In: YES user_id=163326 Billy, what do we do in this case? Use the stuff from the windows/ directory? Anonymous, could you please post what >>> import sys, os >>> print sys.platform >>> print os.name prints on your DEC machine? On a very old box I have access to, this prints: 'osf1V4' and 'posix'. Another possibility is to rename the functions in the windows/ directory, to avoid name conflicts with libc stuff on other platforms, and *always* use our own implementations. Maybe that's preferrable to special-case for the dozens of Unices out there. Anonymous, as a temporary workaround you can use the functions in the windows/ directory. You'll need to change setup.py so that these get linked in, just search for how it's done for the win32 platform. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589270&group_id=16528 |
|
From: <no...@so...> - 2002-08-01 07:08:15
|
Bugs item #589370, was opened at 2002-07-31 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 09:08 Message: Logged In: YES user_id=163326 I can't reproduce the problem here with PostgreSQL 7.2.1, but will try later with a 7.1.3 at home. It'd still be ueful if you could upload your schema and code. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 08:55 Message: Logged In: YES user_id=163326 Thanks for your submission. Your attachment wasn't uploaded. Most probably you forgot to activate the checkbox titled "Check to Upload and Attach a File". This is a Sourceforge annoyance that we can do nothing about. Would you please upload your file again? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-08-01 06:55:16
|
Bugs item #589370, was opened at 2002-07-31 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-08-01 08:55 Message: Logged In: YES user_id=163326 Thanks for your submission. Your attachment wasn't uploaded. Most probably you forgot to activate the checkbox titled "Check to Upload and Attach a File". This is a Sourceforge annoyance that we can do nothing about. Would you please upload your file again? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-07-31 21:03:01
|
Bugs item #589370, was opened at 2002-07-31 14:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: PgSQL.py hangs on empty result Initial Comment: PACKAGE: pyPgSQL 2.1 (and in 2.0 too) Win32 USING: python 2.2 (Win32) Server 7.1.2 Mandrake Linux 8.1 ERROR: PgSQL.py hangs on line 2142 on empty result. SEE DETAILS IN ATTACHED FILE! select b.Bitrate,b.DauerTxt,b.Dauer,b.OID,b.Artist,a.Name,a.OI D,b.Track,b.Genre, a.PlayList,a.Kommentar,b.Jahr,b.ImportStamp,a.Item,b. Album,a.Entry,b.Title,b.Filename from PlayLists as a,AlleTitel as b where a.Entry=b.OID and (a.PlayList=1 and a.Item>=0) order by a.Item ############################################### ######## This results in the following error (Notice: There are the OIDs of both files selected!) Traceback (most recent call last): File "jukebox.py", line 476, in ? main() File "jukebox.py", line 472, in main myApp = App() File "jukebox.py", line 27, in __init__ wxApp.__init__(self,0) File "C:\Programme\python22\lib\site- packages\wxPython\wx.py", line 1587, in __init__ _wxStart(self.OnInit) File "jukebox.py", line 38, in OnInit self.readPlaylist() File "jukebox.py", line 296, in readPlaylist self.tbPtitles.readTitles(playlist) File "jukedb.py", line 271, in readTitles return self.readMore(where=wcls, order="a.Item") File "sqldb.py", line 228, in readMore cursor.execute(query) File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2415, in execute self.__makedesc__() File "C:\PROGRA~1\Python22\Lib\site- packages\pyPgSQL\PgSQL.py", line 2142, in __makedesc__ _p = _res.getvalue(0, _i) ValueError: result does not contain any tuples. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589370&group_id=16528 |
|
From: <no...@so...> - 2002-07-31 18:15:56
|
Bugs item #589270, was opened at 2002-07-31 11:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589270&group_id=16528 Category: PgInt8 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: strtoll strtoull not in Compac C on OSF Initial Comment: The routines to convert strings to signed and unsigned long longs, strtoll, strtoull, do not seem to available in Compaq C V6.1-123 on Digital UNIX V4.0G (Rev. 1530) (and not part of ANSI C). The package then does not build properly on our ALPHA OSF 1 V4.0 1530. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=589270&group_id=16528 |
|
From: <no...@so...> - 2002-07-29 01:02:57
|
Patches item #569203, was opened at 2002-06-14 23:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=569203&group_id=16528 Category: None Group: None >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Ken Lalonde (kenlalonde) Assigned to: Gerhard Häring (ghaering) Summary: Add missing PgNumeric ops. Initial Comment: My app failed when evaluating -x, where x is a PgNumeric instance. This patch adds the __neg__ and __nonzero__ methods to PgNumeric (pypgsql-2.1): *** PgSQL.py 2002/06/13 22:53:17 1.1 --- PgSQL.py 2002/06/14 18:30:07 *************** *** 1070,1075 **** --- 1070,1081 ---- _o = other.__v return cmp(_s, _o) + def __neg__(self): + return PgNumeric(-self.__v, self.__p, self.__s) + + def __nonzero__(self): + return self.__v not in (None, 0) + def __add__(self, other): if self.__s < other.__s: _d = other.__s - self.__s ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-07-29 03:02 Message: Logged In: YES user_id=163326 Committed. Thanks. ---------------------------------------------------------------------- Comment By: Gerhard Häring (ghaering) Date: 2002-06-19 15:23 Message: Logged In: YES user_id=163326 Thanks, I'll look at it one of these days. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=316528&aid=569203&group_id=16528 |
1 message has been excluded from this view by a project administrator.
