Originally posted by doodab
View Post
Let's say I have an integer called "SCAN_COUNT" on my record. We scan the script out. SCAN_COUNT = 1.
The candidate sits the exam and it is scanned back in. SCAN_COUNT now = 2.
If the result wasn't scanned back in the 1 < than the expected 2 so we have a missing script. OK so far?
Right. Good.
So in the original solution, we only scan on the way back in. So let's say when the entry is created SCAN_COUNT = 0.
Then on the way back in it is incremented to 1.
Any rows with a value of 0 would be unscanned scripts.
So in scenario 1 I have to test
WHERE SCAN_COUNT < 2
In the second scenario I have to test
WHERE SCAN_COUNT < 1
Both achieve the same thing. One of course requires let work, so is more efficient and hence cheaper. The second one requires some re-work of the system which makes it a non starter right off the bat.
Got it?
Comment