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-07-17 12:10:28
|
Bugs item #562738, was opened at 2002-05-31 05:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=562738&group_id=16528 Category: PgSQL Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Gerhard Häring (ghaering) Assigned to: Gerhard Häring (ghaering) Summary: No exception thrown on empy result set Initial Comment: According to the DB-API 2.0, an exception should be thrown if fetchone(), fetchmany() or fetchall() are called but the result set was empty. ---------------------------------------------------------------------- >Comment By: Gerhard Häring (ghaering) Date: 2002-07-17 14:10 Message: Logged In: YES user_id=163326 Not a bug. See http://sourceforge.net/tracker/index.php?func=detail&aid=562737&group_id=22307&atid=374932 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=562738&group_id=16528 |
|
From: <no...@so...> - 2002-06-19 13:23:21
|
Patches item #569203, was opened at 2002-06-14 23:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=316528&aid=569203&group_id=16528 Category: None Group: None Status: Open Resolution: None 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-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: http://sourceforge.net/tracker/?func=detail&atid=316528&aid=569203&group_id=16528 |
|
From: <no...@so...> - 2002-06-14 21:45:17
|
Patches item #569203, was opened at 2002-06-14 17:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=316528&aid=569203&group_id=16528 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ken Lalonde (kenlalonde) Assigned to: Nobody/Anonymous (nobody) 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 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=316528&aid=569203&group_id=16528 |
|
From: <no...@so...> - 2002-06-05 17:32:06
|
Patches item #484468, was opened at 2001-11-22 07:04 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=316528&aid=484468&group_id=16528 Category: None Group: None Status: Open Resolution: None 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: http://sourceforge.net/tracker/?func=detail&atid=316528&aid=484468&group_id=16528 |
1 message has been excluded from this view by a project administrator.
