HI,
if I look lifecycle page then we can really drop support for mysql <
4.1 because 4.0 ended it's lifecycle 30 Aug 2008.
Thanks,
Alex
Am 08.08.2009 um 12:11 schrieb Thomas Göttgens:
Hello Alexander,
2 alternatives:
- judging by the gap between 1.4.1 and 1.4.3 we're at least another 6
to 12 months away from a new release, despite the tons of good new
stuff
in CVS. According to http://www.mysql.com/about/legal/lifecycle/#calendar
4.0 is already out of extended support and 4.1 will be by the end of
the year. I'm +1 for requiring at least 4.1 if not 5.0 from the next
release onward.
- Another possibility would be to detect the server version from the
client lib and switch the use of escape/real_escape from that
information. The Kannel Admin status page does the detection of the
server version already, so if mysql is used in production with a
database, that information is available after the connect/bind. Of
course if the client lib is too old to provide real_escape to begin
with, this is purely an autoconf issue.
--
Best regards,
Thomas mailto:[email protected]
