Il lun, 2003-12-01 alle 16:52, Sebastien Bigaret ha scritto:
> I wrote:
> [...]
> > Of course the code used in _psyco_curs_execute() to handle the error
> > can be duplicated in psyco_conn_commit(), given that curs_commitall()
> > checks the status returned by commit_pgconn() and forwards the error
> > to the caller. I would have submitted the quite straightforward patch
> > doing this, if only I knew what should be done in the loop committing
> > the cursors: should the loop be immediately stopped? Is there
> > something that should be done for the cursors that succeeded in
> > committing their changes before the error happens?
>
> I forgot to tell that this pb annoys me and that I'll be happy to
> propose a patch for this if I can get answers to the questions above ;)
give me 24h and i'll answer. i don't have a single sec right now. :(
(this mail is just to tell you i'am not ignoring this serious problem,
thank you very much for reporting it.)
--
Federico Di Gregorio http://people.initd.org/fog
Debian GNU/Linux Developer
fog-8fiUuRrzOP0dnm+yROfE0A@xxxxxxxxxxxxxxxx
INIT.D Developer
fog-NGVKUo/i/6DYtjvyW6yDsg@xxxxxxxxxxxxxxxx
Viviamo in un mondo reale, Ciccio. -- Lucy
signature.asc
Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/+sw@xxxxxxxxxxxxxxxx
http://lists.initd.org/mailman/listinfo/psycopg
|