Bug #9764

SQL interface to prepared statements

Details

Submitted	2007-01-08 07:45 UTC
From	csaba dot simon at continuent dot com
Assigned	quipo
Status	Wont fix
Package	MDB2_Driver_mysql
PHP Version	5.2.0
OS	Linux
Roadmaps	(Not assigned)

Comments

[2007-01-08 07:45 UTC] csaba dot simon at continuent dot com

Description:
------------
Currently the MDB2 mysql driver is using the SQL interface to prepared statements instead of the client/server binary protocol based prepared statements (like mysqli)

On the MySQL site http://dev.mysql.com/doc/refman/5.0/en/sqlps.html is documented that "This interface is not as efficient as using the binary protocol through a prepared statement API"
However you can use only if:
* You want to test how prepared statements work in your application before coding it.
* An application has problems executing prepared statements and you want to determine interactively what the problem is.
* You want to create a test case that describes a problem you are having with prepared statements, so that you can file a bug report.
* You need to use prepared statements but do not have access to a programming API that supports them.

Is there any reason using this kind of prepared statements? Can be rewritten the driver to use the binary protocol?

[2007-01-08 11:32 UTC] pwadas at jewish dot org dot pl

Hello,
apache 2.2.3 (debian package version 2.2.3-3.2)
php 5.2.0 (debian package version 5.2.0-8)
mysql sever/client 5.1.11 (debian package 5.1.11beta-1)
driver_mysql 5.3.0

aapche child returns segfault with driver_mysql 1.3.0, and it does not with driver_mysql 1.2.2 nor mysqli 1.3.0.

This may be related to bug listed above, however it's hard to say whether its apache 2.2.3 / apache2-php5 module / mysql libs / php bug. In my system downgrading driver_mysql to 1.2.2 fixed issue.

from apache's error.log:
[Sun Jan 07 21:57:09 2007] [notice] child pid 14722 exit signal Segmentation fault (11)