Bonjour Michaël,
>> Sure. I meant that the feature would make sense to write benchmark scripts
>> which would use aset and be able to act on the success or not of this aset,
>> not to resurrect it for a hidden coverage test.
>
> This could always be discussed for v14. We'll see.
Or v15, or never, who knows? :-)
The use case I have in mind for such a feature is to be able to have a
flow of DELETE transactions in a multi-script benchmark without breaking
concurrent SELECT/UPDATE transactions. For that, the ability of extracting
data easily and testing whether it was non empty would help.
> Applied, then. Thanks!
Thanks to you!
--
Fabien.
