Even SERIALIZABLE might not help. Some DBs implement it based on snapshots and when transaction commits the snapshot is checked for conflicts. And if there are conflicts the tx will be rolled back. So, it is still optimistic semantics.
You would need to lock the table after the first finder is executed to prevent this.
many thanks alexey