[horde] The 'isWarning()' bug

Chuck Hagenbuch chuck at horde.org
Wed Feb 19 08:36:51 PST 2003


Quoting "Hobbs, Richard" <hobbs at mongeese.co.uk>:

> Has the following bug:
> 
>   http://bugs.horde.org/show_bug.cgi?id=1116

To be clear, this is NOT A BUG IN HORDE.

PEAR DB broke backwards compatibility. We have new releases that work with
the new (broken, API-wise) PEAR DB. It's still not a bug.

> been fixed in the latest production release of Horde (Version 2.2.1
> final), or is it due for a future release?

It was fixed in 2.2.

> I can see that the bug's status is "Closed : Fixed", but i don't know if
> it's fixed in this release, or fixed in a beta release or something. Can
> someone please confirm.

>From horde/docs/CHANGES, for the block of changes for 2.2:

[jan] Remove deprecated DB::isWarning() calls.

> Do i need to also upgrade IMP/Mnemo/Kronolith etc... to fix this bug, or
> is it only in the Horde framework itself?

Anything with a SQL driver is potentially affected. Look at the changelogs.

-chuck

--
Charles Hagenbuch, <chuck at horde.org>
must ... find ... acorns ... *thud*


More information about the horde mailing list