I just checked in (Oracle) MySQL 5.5.32 and 5.6.13. SELECT COT(0) -- returns Error CODE: 1690 DOUBLE VALUE IS OUT of RANGE IN 'cot(0)'
So this change in behaviour has its origin in (Oracle) MySQL 5.5. On Thu, Aug 1, 2013 at 9:56 PM, Ian Gilfillan <[email protected]>wrote: > Hi > > SELECT COT(0) returns: > > ERROR 1690 (22003): DOUBLE value is out of range in 'cot(0)' > > in both MariaDB 10 and 5.5, but in MySQL 5.1 it returns NULL. > > I can't find a changelog reference to this, but I see it's still > documented as returning NULL in MySQL 5.5 (I don't have this to test on). > Is this a MariaDB-specific change? When did this change in behaviour happen? > > thanks, > ian > > ______________________________**_________________ > Mailing list: > https://launchpad.net/~maria-**developers<https://launchpad.net/~maria-developers> > Post to : > maria-developers@lists.**launchpad.net<[email protected]> > Unsubscribe : > https://launchpad.net/~maria-**developers<https://launchpad.net/~maria-developers> > More help : > https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp> >
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
