On Wed, Mar 02, 2005 at 11:41:00PM +0000, Sam Clegg wrote: > Steve Langasek wrote:
> > On Wed, Mar 02, 2005 at 03:55:32PM +0000, Sam Clegg wrote:
> >>I found this problem while using the python bindings which set
> >>autocommit off by default.
> >>When not in autocommit mode (SET AUTOCOMMIT=0) the client will fail on
> >>reconnect and the nature of the error is not reported to the user.
> >>In the program below the final mysql_real_query() correctly returns
> >>-1 but mysql_error() incorrectly returns an empty string.
> > The libmysqlclient10 package is in legacy "maintenance mode", so this bug is
> > not likely to be fixed any time soon. Do you see the same problem with
> > libmysqlclient12 and/or libmysqlclient14?
> I'd guessed that this might be true. The only reason I care is that
> the python bindings in sid are still linking against it. Perhaps I
> should ask thier maintainer to up the version?
This is already covered by an upcoming mass-transition to
libmysqlclient12. ("mass" because a bunch of packages need to be
updated at the same time to avoid segfaults in various applications that
could otherwise load multiple copies of libmysqlclient into memory at
once.)
> I'll see if I ge the same problem will 12/14.
Thanks.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
