Page 1 of 1

MAX and MIN don't work when subtype of INTEGER defined

Posted: Tue Oct 11, 2011 3:13 pm
by AndrewWarden
Using version 1.06 beta I got the following result on a brand new database (note how MAX works correctly before the type definition, fails after it):

max(rel{tup{x 1},tup{x 2}},x)
2

TYPE POSINT IS { INTEGER CONSTRAINT INTEGER > 0 };

Ok.

max(rel{tup{x 1},tup{x 2}},x)

ERROR: No run-time invocation targets found for MAX(RELATION {x INTEGER, %attributeName1 INTEGER}, POSINT)

Line 1, column 28 near 'x'

Hugh Darwen

Re: MAX and MIN don't work when subtype of INTEGER defined

Posted: Tue Oct 11, 2011 4:25 pm
by HughDarwen
I can confirm that the same error doesn't arise on version 1.05 beta.

Hugh Darwen

Re: MAX and MIN don't work when subtype of INTEGER defined

Posted: Wed Oct 12, 2011 2:54 pm
by Dave
I've fixed this in version 1.07, to be released shortly.