Of course it's possible, but the probability is low.
The DELETE is a SQL DELETE setting a WRITE lock, which is released after the commit. Then FastLoad submits the BEGIN LOAD to set the FastLoad lock.
A SELECT might run concurrently with the DELETE (using ACCESS lock). Or it's queued (using READ lock) by that DELETE and then it returns zero rows after the commit.
Dieter
Of course it's possible, but the probability is low.
The DELETE is a SQL DELETE setting a WRITE lock, which is released after the commit. Then FastLoad submits the BEGIN LOAD to set the FastLoad lock.
A SELECT might run concurrently with the DELETE (using ACCESS lock). Or it's queued (using READ lock) by that DELETE and then it returns zero rows after the commit.
Dieter