I recommend you add breakpoints to the two
places where such error is logged (if it occurs for
multi-value QBFs as well) and look at the source and
target/removed values and the contents of the refMemories.
It is possible, that eval has some weird
issue that that causes multiple matches transiently. You could
try the name query without the eval (say the name is always
the lastName), if that behaves correctly, then my bet is on
eval, though debugging may reveal a problem in the QBF
implementation.
Cheers,
Ábel Hegedüs
Fault Tolerant Systems Research Group
Department of Measurement and Information Systems
Budapest University of Technology and Economics
On 2013.10.23.
22:55:07, Tamas Szabo <tamas.szabo@xxxxxxxxx> wrote:
Hi
@Abel: When can such a thing happen with the
Single/MultiValueQueryBasedFeature?
Can you take a look at the library.domain.base example?
If you play around with the dynamic instance model you can see
some
really weird values for the Library.name feature.
Sometimes it doesn't have a value, sometimes it has a wrong
value...
Regards,
Tamas
_______________________________________________
incquery-dev mailing list
incquery-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/incquery-dev