Re: [ANNOUNCEMENT] DB-1.6.0 (stable) Released.
| From: | Lukas Smith | Date: | Fri, 20 Feb 2004 10:39:30 +0000 |
| Subject: | Re: [ANNOUNCEMENT] DB-1.6.0 (stable) Released. | ||
| References: | 1 2 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-10817@lists.php.net to get a copy of this message | ||
James 'Chip' Kaufman wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 19 February 2004 16:03, PEAR Announce wrote:Uhm so since when was this bug in DB? Could you guys us some more details. Maybe Dan already knows the implications, but I just want to understand if this was a bug fix that you handled by adding a work around? regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07The new PEAR package DB-1.6.0 (stable) has been released at http://pear.php.net/. Release notes ------------- BUGS FIXED: - ifx: fetchRow() now adds 1 to the requested $rownum because ifx_fetch_row() starts at 1. (peterwb)This is nice, but it will break applications that expected the other behaviour. Is there a way for the code to determine which version of DB is running, and if DB version >= 1.6.0 do something different? My code currently handles the fetchRow issue. It could be deployed on machines running DB 1.5 or now 1.6. It works on 1.5, but will break as soon as DB gets upgraded. How can I determine at run-time which version is running so I can handle this gracefully?