Re: [ANNOUNCEMENT] DB-1.6.0 (stable) Released.
| From: | Lukas Smith | Date: | Fri, 20 Feb 2004 14:33:41 +0000 |
| Subject: | Re: [ANNOUNCEMENT] DB-1.6.0 (stable) Released. | ||
| References: | 1 2 3 4 | Groups: | php.pear.general php.pear.qa |
| Request: | Send a blank email to pear-general+get-10827@lists.php.net to get a copy of this message | ||
James 'Chip' Kaufman wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 20 February 2004 04:39, Lukas Smith wrote:Ok in light of this i would say the bug as been so long standing and has such severe implications for affected users that atleast the old behaviour has to be accessible for existing users through an option. The way I got it its clearly a bug fix so the default should not be to use the old broken behaviour. Does that sound allright for all parties involed? Maybe the new portability system would do for this .. then again its so driver specific that it should probably get its own driver specific option. James could you open a bug report for this? 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 07James 'Chip' Kaufman wrote:When I first started using DB (about a year ago), I first started using mySQL as the db, then switched to Informix. I notice this in my code: /* MySQL fetches rows beginning from 0, Informix starts at 1 */-----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.comThe 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?if ($dbengine=='ifx') { $iRowOffset++; }So I knew about this for at least eight months. I'm not sure why I didn't report it then.