[Bug 250354] [NEW] MySQL doesn't accept non-real dates on stored procedure calls

[Matthew]

Public bug reported:

Binary package hint: mysql-server

Sort of hard to explain.  I created a stored procedures where you pass 2
dates, a begindate and enddate.  I used >= begindate AND <= enddate. I
couldn't figure out why sometimes I was getting unexpected results.
Eventually I figured out that "non-real" dates (for example 2008-06-31)
causes mysql to return NULL.

What's strange is that IT ACCEPTS the non-real dates in a regular
SELECT.  But if you stick the exact same SELECT into a Stored Procedure
it stops working.

I hope I have been clear enough that you understand.  I would consider
this to be a bug and not user error since the problem only occurs with
stored procedures.  Also I ahve check and some other distros don't have
this happen.

** Affects: mysql-dfsg-5.0 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
MySQL doesn't accept non-real dates on stored procedure calls
https://bugs.launchpad.net/bugs/250354
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.