Quote:
Originally Posted by Starson17
I suspect that this would be a bit too aggressive. I've run many dupe tests on my library using various SQL queries. My experience is that you want to run many different tests, as each individual test may find some dupe books, but not others. I don't mind the time to run a second dupe test over my books, even if I'm pretty sure they aren't dupes. If they weren't found to be dupes the first time, they shouldn't show up as a false positive the second time. If they do, then I want to review and find out why it's been identified as a dupe this time, when it wasn't the first time.
|
Right. I haven't realised that.
Especially when running a query doesn't require excessive time.