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

Mathias Gug mathiaz at ubuntu.com
Mon Jul 21 15:24:33 BST 2008


On Mon, Jul 21, 2008 at 12:08:58AM -0000, Matthew wrote:
> 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.

Could specify the actual code you've used to create the store procedure
?

> 
> 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.

Could you list which sql statement you're using and the outcome you
receive ?


 status incomplete

-- 
Mathias Gug
Ubuntu Developer  http://www.ubuntu.com


** Changed in: mysql-dfsg-5.0 (Ubuntu)
       Status: New => Incomplete

-- 
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.



More information about the Ubuntu-server-bugs mailing list