|
Okay, I don't own a theater, to borrow fm Celko's examples
in"SQL for Smarties", but I certainly have a similar need to examine a series of
numbers, a sequence, or actually a set of sequences, as there can be 1:N numbers
missing - these can be "missing" at any point in the recordset and may or may
not be contiguous.
To use today's example. I have a sample of
340 records, originally numbered (ID'd) 1:340. Now, due to processing (a
3rd party system that has its own way of doing things) some of the records will
have their ID changed. F/example, these 340 records now have
MAX(ID)=348. So, by "eyeballing" in the Data Browser, I found that ID's
19,20,58,199,209,298,300,326 [COUNT(listmembers)=8] have been changed to
341:348. (The numbers are only relevant to illustrate the example, which,
is "real world", as of 11:42am CST, today.)
My counts all "balance", so I have all the records I'm s'posed
to have, but I'd like to execute a query against the ID's I actually receive
post-processing versus what I had pre-processing. I'd hoped that Celko's
examples would be close - and they may be, but I haven't done complete due
diligence yet - but I thought I'd ask y'all about this too.
In short, I'm trying to describe via SQL the discontinuities
in a data-set. That is, have the query results show me, using today's example
the 8 ID's that are "missing"||"skipped" fm the set of ID's.
Any ideas? If not, any interest in finding out what I
do, if I meet success?
Thanks & Later,
Steve in Memphis
|
