LIMIT ?,? statement

* Fixed bug where strings that were used in numeric
context were not getting quoted on execute(). Now all
parameters are bound as varchar by default.

**NOTE** this is a change in behavior that MAY cause problems
with some SQL statements. If quoted integers, for example,
cause any problems, use bind_param(, SQL_INTEGER) to
force a column to be bound as an integer.

Yes, it MAKES problems.
All queries with 'LIMIT ?,?' FAILS now,
because modern versions of MySQL fails to execute statements
with quoted LIMIT ranges.

Anyone should be able to repeat the bug with
the latest stable or development version of MySQL Server.

You want to force EVERYONE in this world to change their
coding style and STOP using convenient wrappers
like $dbh->selectrow_hashref( $statement, undef, @params ) ?

You wish that EVERYONE should use bind_param(..., ..., SQL_INTEGER)
everythere because of this STUPID change?

Please, FIX THIS.

PS: Sorry, I can't talk about this without emotions
because I'm very tired of this.

--

Regards, Walery Studennikov,
WebNames.Ru technical support

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org