[Pljava-dev] Cancelling trigger operation

I see what you mean :-) and yes, I do think it is a bit too cryptic
since it suggests that there actually is a row that can be deleted. It
might lead to some semantic confusion. The reason the new and old row is
represented as ResultSet instances are not that they are sets as such,
it's just the best interface when dealing with a tuple. I don't want to
add to that confusion by allowing the deletion of the tuple that they
represent. An explicit method that denotes the cancellation of the
trigger is a better choice, IMO.

Regards,
Thomas Hallgren

Markus Schaber wrote:
> Hi, Thomas,
>
> Thomas Hallgren wrote:
>
>
>> Something is definitely missing in the TriggerData interface. It should
>> have a 'setCancelled()' method that causes the returned tuple to be
>> null. Please add a bug for this.
>>
>
> What about using TriggerData.getNew().deleteRow() - is this too cryptic?
>
> Thanks,
> Markus
>
>