76149 – MySQL 4.0.23 handles FROM_UNIXTIME(0) differently - upstream bug?

Bug 76149 - MySQL 4.0.23 handles FROM_UNIXTIME(0) differently - upstream bug?

Summary: MySQL 4.0.23 handles FROM_UNIXTIME(0) differently - upstream bug?

Status:	RESOLVED NEEDINFO

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Gentoo Linux MySQL bugs team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-12-30 08:48 UTC by Dennis Freise
Modified:	2005-03-12 17:00 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dennis Freise 2004-12-30 08:48:51 UTC

MySQL 4.0.22 returns for FROM_UNIXTIME(0): 1970-01-01 01:00:00
MySQL 4.0.23 returns for FROM_UNIXTIME(0): NULL

The 4.0.22 way seems more usable to me, and nagios for example RELIES on that behaviour (saving of status information in mysql no longer works with 4.0.23)

Is this an upstream-bug ?

Comment 1 Robin Johnson archtester

2005-01-04 20:09:10 UTC

Fixed upstream. Waiting for 4.0.24 for it.
4.0.23 will not go in gentoo stable.
http://bugs.mysql.com/bug.php?id=7515

Comment 2 steveb 2005-01-19 04:44:15 UTC

Well.... today 4.0.23 showed up in my portage and I emerged it. I have now real trouble with many packages. Starting from postfix, mysql-ruby, nagios-core, etc...

Comment 3 Robin Johnson archtester

2005-03-12 17:00:13 UTC

Sorry about upstream's delay in 4.0.24.
4.0.24 will be in CVS in a few hours, please test it and report back.