websitemaster at cogeco.net
Mon Jun 13 19:00:30 EDT 2011
None here either.
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan
Sent: June-13-11 3:34 PM
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] MySQLi
On Mon, 2011-06-13 at 21:20 +0200, Dirk Haun wrote:
> I have been playing around with patch #1303, which adds MySQLi support.
To be honest, I don't see any change in performance one way or another, at
least not with the kinds of requests I was testing it with.
> Having said that: MySQLi is the recommended API for MySQL 4.1 and later.
Plus things can only get better once we understand it a bit better.
> Since MySQLi is an extension, it might not be present (although that's
unlikely). So we have to check every time which of the two APIs we've got to
use. To make this a little easier, I would like to suggest that we raise the
minimum required MySQL version to 4.1.3 (from 4.0.18). Then we can simply
check for existence of the MySQLi class and use that if present or fall back
to the old API otherwise.
> To put things into perspective: Support for MySQL 4.1 ended 1.5 years ago
(2009-12-31) - and we would only make it the mimimum requirement now. Even
RHEL 4 - one of the Linux distros for which we keep PHP 4 support around in
the 1.7.x branch - shipped with MySQL 4.1.
> Any objections or concerns?
No objections here.
For me, one thing that MySQLi has going for it is the ability to run stored
routines (procedures and functions). Though those features were not
introduced until MySQL 5.0.2
> bye, Dirk
>  http://project.geeklog.net/tracking/view.php?id=1303
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel