|
|
Posted by Andy Hassall on 08/30/05 01:33
On Mon, 29 Aug 2005 18:05:50 -0400, Tom D <noone@nowhere.com> wrote:
>I'm rewriting a database interface that our company currently has.
>Currently it's using the Pear::DB interface, but we found that that was
>introducing a bit too much overhead. I'm rewriting the interface to use
>mysqli. Most of what the interface does is to simplify getting results in
>the form of arrays (ordered and associative). Most of the code using the
>interface used sql queries with placeholders and parameters. For that
>reason I'd like to use prepared statements in mysqli, but I'm running into
>a few problems.
This isn't a direct answer, it's one of those annoying "you're doing X with Y
but have you looked at Z" answers: if overhead was the main issue, have you
compared it with ADOdb? It fares quite well in benchmarks, particularly when
compared with PEAR which seems to do quite badly.
ADOdb emulates prepared statements for older versions of MySQL, but also has
mysqli support which from a glance at the code does use mysqli_stmt_bind_param,
so is using native prepared statements.
Can't comment as to whether it would solve the other issues, though.
--
Andy Hassall :: andy@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Navigation:
[Reply to this message]
|