SQL execution fails to finish and reports bogus error messages #3842
Last updated: 2016-01-15 11:38:18 +0100
Date: 2015-10-29 07:58:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0
using column of table in user defined fuction will cause execution failure and bogus error message reported.
Steps to Reproduce:
get error messages like: Function '..P*' not defined. (NOTE: the function name is bogus and keeps changing every time)
get the count of the qualified rows.
Date: 2015-10-29 08:00:57 +0100
Created attachment 364
sql and data to reproduce the bug can be found in attached file.
Date: 2015-11-08 11:01:29 +0100
CREATE INDEX "chg_t_effc_tm" ON "sys"."ods_chg" ("t_effc_tm");
is not defined in the test scripts.
For the trimmed down version (4 tuples in each table) the problem
Function 'calc.>=' not defined
This hints at an error in the UDF, which indeed attempts to execute:
X_132 and X_140 are timestamps and the system only supports mtime.<=.
The issue is that this is not properly handled during the optimizer phase,
Bug added as file BugTracker-2015/Tests/missed-error.Bug-3842.sql
Date: 2015-11-11 09:22:21 +0100
(In reply to darkbluehacker from comment 0)
This part of the bug has been fixed in changeset 982c835b3f2b
Date: 2015-11-26 15:55:06 +0100
Is there any progress on this bug?
Date: 2015-12-02 07:36:29 +0100
According to our debugging, it requires multiplex function "<=" for timestamps. But the function MANIFOLDremapMultiplex is actually a dummy function and thus it reports a function(In reply to Martin Kersten from comment 2)
We found that MANIFOLDremapMultiplex is actually a dummy function and thus the 'calc.>=' is not found. But MANIFOLDevaluate (also in manifold.c) seems to have proper implementation of the 'calc.>='.
To fix this bug, can we just function mapping in manifold.mal as below?
Date: 2015-12-23 10:17:35 +0100
for sql inline functions the optimization stack wasn't run, this is now fixed.
Date: 2015-12-23 14:57:58 +0100
(In reply to Niels Nes from comment 6)
Can I get the version with the fix and learn from it?
More, https://www.monetdb.org/bugzilla/show_bug.cgi?id=3882 looks similar to this bug. Could you also check it?
The text was updated successfully, but these errors were encountered: