Bug #7114 Server Crashes using IN claus on timestamp field

• Submitted: 8 Dec 2004 20:40
• Modified: 9 Jan 2005 19:53
• Reporter: Richard Sharp
• Status: No Feedback
• Category: MySQL Server: MyISAM storage engine
• Severity: S1 (Critical)
• Version: 4.1.7
• OS: Windows (Windows Server 2003)
• CPU Architecture: Any

[8 Dec 2004 20:40] Richard Sharp

Description:
MySQL Server 4.1.7 running on Windows Server 2003, installed from binary package. Table type: MyISAM. Platform: Dual Intel Xeon 2.5 Gig processors, with 2 Gig ram, RAID5.

The following query causes the server to crash completely:

SELECT <fields> FROM <table> WHERE <timestamp field> IN (Null,00000000000000)

The problem is corrected replacing previous query with this one:
SELECT <fields> FROM <table> WHERE (<timestamp field> IS Null) OR (<timestamp field =00000000000000)

The problem only appears to affect timestamp fields. The original query worked fine on MySQL 4.0. I assume the problem is related to the new method of displaying timestamp fields, but it should case an error rather than crashing the server.

Error message in Windows event log: Faulting application mysqld-nt.exe, version 0.0.0.0, faulting module mysqld-nt.exe, version 0.0.0.0, fault address 0x00024d93.

No entry appears in the MySQL error log.

How to repeat:
SELECT <fields> FROM <table> WHERE <timestamp field> IN (Null,00000000000000)

[9 Dec 2004 9:58] Hartmut Holzgraefe

Can't reproduce this on Linux, might be Windows specific?

[9 Dec 2004 19:53] MySQL Verification Team

Wasn't able reproduce it on my Windows box. Does MySQL server crash on any table with timestamp column?

[14 Feb 2005 22:54] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".