> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Michiel Meeuwissen
>
> I think that I understand now that it returns a String
> because it is stored as String (probably because in the
> resulting SQL query you finally need a String). But it is a
> bit confusing because you set a Number and get a String.
Yes, but in addition to this, the value can itself be a string.
These are all valid constraints that can be represented:
name BETWEEN 'a' AND 'f'
name BETWEEN '1' AND '5'
number BETWEEN 1 AND 5
The same goes for FieldValueInConstraint.
> So, my question is, would it nog have been nicer to store the
> originally set objects rather then converting them to String
> immediately? Then the 'get' functions can work more
> intuitively and cloning will be simpler.
As far as storing the values is concerned, this is merely a matter of
implementation, chosen to avoid having to do the conversion each time
the get-method is called.
If life is made easier by storing the original objects as well, go ahead
and do it. As long as the interface methods are not affected - these
should return strings.
Rob van Maris
Technical Consultant
Quantiq
xmedia & communication solutions
Koninginneweg 11-13
1217 KP Hilversum
T +31 (0)356257211
M +31 (0)651444006
E [EMAIL PROTECTED]
