Re: Status of DBD::mysql with MySQL 5 - Darren Duncan - com.mysql.lists.perl

4 messages in com.mysql.lists.perlRe: Status of DBD::mysql with MySQL 5

From	Sent On	Attachments
Giuseppe Maxia	25 Feb 2006 02:24
Jochen Wiedmann	25 Feb 2006 12:27
Giuseppe Maxia	25 Feb 2006 14:11
Darren Duncan	26 Feb 2006 00:22

Subject:	Re: Status of DBD::mysql with MySQL 5
From:	Darren Duncan (dar...@DarrenDuncan.net)
Date:	02/26/2006 12:22:50 AM
List:	com.mysql.lists.perl

At 11:12 PM +0100 2/25/06, Giuseppe Maxia wrote:

You are right about that. I don't deny there are some benefits in using prepared statements. I have been waiting for their implementation in MySQL and I welcome them. But I must stress that this should not be the default behavior, if it disrupts existing applications.

I disagree. True prepared statements should be the default and should be left the default. That gets the most people using them, and brings any remaining implementation issues to the fore, so that they can be fixed.

So switching back to emulatated mode is BAD, BAD, BAD.

The only best solution is to fix any remaining statements so that they work with true prepared statements.

In the mean time, people like you can manually switch back to emulated mode if you need to, but that inferior situation shouldn't be pushed on others by default.

Thanks for pointing out that. I missed that method.

Unfortunately, this method doesn't seem to be implemented in DBD::mysql. When I try to enter OUT or INOUT parameters using bind_param_inout, I get the error "Output parameters not supported". Is it truly so or it is perhaps just a documentation problem?

Once again, if that isn't supported, then they should become supported. This is no excuse to default to emulated mode.