Re: Best way to retire old code for unsupported database versions

2013-09-27 Thread Martin J. Evans
On 27/09/13 03:52, Greg Sabino Mullane wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 what to do about having something around that you can refer people who want to run 4.x (???!!!). Is a simple information tidbit if you want to use xxx, you use version x.y.z version of DBD::mysql

Best way to retire old code for unsupported database versions

2013-09-26 Thread Patrick Galbraith
Hi all, I wanted to get opinions on how do deal with old code that clutters up the driver and is only needed for really old, outdated and unsupported versions of the database. DBD::mysql has a lot of #ifdef clutter to deal with things that weren't supported in 4.0 and 4.1 (god forbid 3.x).

Re: Best way to retire old code for unsupported database versions

2013-09-26 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 what to do about having something around that you can refer people who want to run 4.x (???!!!). Is a simple information tidbit if you want to use xxx, you use version x.y.z version of DBD::mysql ? What have others done about this issue?