TypeException after calling UDF in other than sys schema (when it is initialised) #2904
Last updated: 2011-10-26 13:22:03 +0200
Date: 2011-10-13 16:27:28 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
After creating and starting new database testing, and altering the
Steps to Reproduce:
Several exceptions like:
See also bug #2903
Date: 2011-10-14 08:46:17 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=08e5fe124329
Date: 2011-10-14 08:46:45 +0200
fixed by always cleanup the sql function list.
Date: 2011-10-14 08:56:19 +0200
*** Bug #2902 has been marked as a duplicate of this bug. ***
Date: 2011-10-14 10:14:28 +0200
re-opened to remind us that we should consider adding a test.
Date: 2011-10-14 10:23:01 +0200
Just an insight from release-engineering point of view. When this bug isn't closed/nextrelease, it won't show up (automatically) on the list of closed bugs for the next release. Since this will go unnoticed for sure, it means this bug isn't listed where it is, and with the current automation, will be reported as fixed for the release afterwards (assuming it'll be closed by then).
So how about using the Keywords field to add a status like NEEDSTEST or something, such that the bug itself can remain closed?
Date: 2011-10-14 11:25:56 +0200
That would indeed be an option.
I just noticed, that closed bug with request for more information, feedback, or validation by the original reported "vanish" unnoticed, because they do no longer appear as open bugs.
in general, we would need three major categories:
Date: 2011-10-14 12:54:05 +0200
the test of both bugs is the same (the schema part doens't make a difference), ie only one needs a test.
Date: 2011-10-14 13:00:57 +0200
is there a test for bug #2902 (which is marked as dublicate of this one), then?
Date: 2011-10-17 14:21:54 +0200
Test was added.
Date: 2011-10-17 14:27:15 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f1b05d742f8f
The text was updated successfully, but these errors were encountered: