Bug #32481 Why different result?

• Submitted: 18 Nov 2007 17:03
• Modified: 18 Dec 2007 17:49
• Reporter: ngs ngs
• Status: No Feedback
• Category: MySQL Server: User-defined functions ( UDF )
• Severity: S3 (Non-critical)
• OS: Any
• CPU Architecture: Any

[18 Nov 2007 17:03] ngs ngs

Description:
select User,Date(Date) Data,nglim(Unix_TimeStamp(date),Unix_TimeStamp(date)+time_to_sec(duration)) nglim 
FROM book WHERE ID>0 AND Date BETWEEN 71001 AND 71002 
GROUP BY 1,2 
HAVING nglim;

113	2007-10-03	0
113	2007-10-17	0
120	2007-10-01	0
130	2007-11-05	0
142	2007-10-04	0
154	2007-10-07	0

result is bad

select User,Date(Date) Data,nglim(Unix_TimeStamp(date),Unix_TimeStamp(date)+time_to_sec(duration)) nglim 
FROM book 

WHERE ID>0 AND Date BETWEEN 71001 AND 71002 
GROUP BY 1,2 
HAVING nglim(Unix_TimeStamp(date),Unix_TimeStamp(date)+time_to_sec(duration);

113	2007-10-03	12
113	2007-10-17	22
120	2007-10-01	2
130	2007-11-05	54
142	2007-10-04	22
154	2007-10-07	22

How to repeat:
create aggregate function nglim returns integer soname 'sample.dll';
 
select User,Date(Date) Data,nglim(Unix_TimeStamp(date),Unix_TimeStamp(date)+time_to_sec(duration)) nglim 
FROM book WHERE ID>0 AND Date BETWEEN 71001 AND 71002 
GROUP BY 1,2 
HAVING nglim;

113	2007-10-03	0
113	2007-10-17	0
120	2007-10-01	0
130	2007-11-05	0
142	2007-10-04	0
154	2007-10-07	0

result is bad

select User,Date(Date) Data,nglim(Unix_TimeStamp(date),Unix_TimeStamp(date)+time_to_sec(duration)) nglim 
FROM book 

WHERE ID>0 AND Date BETWEEN 71001 AND 71002 
GROUP BY 1,2 
HAVING nglim(Unix_TimeStamp(date),Unix_TimeStamp(date)+time_to_sec(duration);

113	2007-10-03	12
113	2007-10-17	22
120	2007-10-01	2
130	2007-11-05	54
142	2007-10-04	22
154	2007-10-07	22

[18 Nov 2007 17:49] Valeriy Kravchuk

Please, provide a complete test case, with CREATE TABLE, data and full source code to create your UDF.

[19 Dec 2007 0:00] 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".