Alas, the gaps are as large as 500.
Normally, products are never deleted from the system; but I put in some
corrupt data that I did not want to pass along, even if I marked them as
discontinued. They complain about that, too.
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
>From: Mike Diehl [mailto:mdiehl@stripped]
>Sent: Thursday, September 18, 2008 1:17 PM
>Cc: Jerry Schwartz; 'Stut'
>Subject: Re: Finding gaps
>I'm just throwing something out ...
>select a.id,b.id from dataset a left join dataset b
> on a.id=b.id+1
> where b.id is null;
>This should find single gaps. It won't find larger gaps.
>Just my $.02.
>On Thursday 18 September 2008 10:44:47 am Jerry Schwartz wrote:
>> >-----Original Message-----
>> >From: Stut [mailto:stuttle@stripped]
>> >Sent: Wednesday, September 17, 2008 6:30 PM
>> >To: Jerry Schwartz
>> >Cc: mysql@stripped
>> >Subject: Re: Finding gaps
>> >On 17 Sep 2008, at 22:34, Jerry Schwartz wrote:
>> >> Our Japanese partners will notice and will ask. Similar things have
>> >> come up
>> >> before.
>> >> I want to be pro-active.
>> >Notice what? Why would it be bad? What type of data are we dealing
>> >with here?
>> [JS] In this case, we are dealing with a list of products.
>> >If each row requires a unique ID use an autonumber. If your partners
>> >don't understand that deleted items will create gaps, explain it to
>> >them. IMHO you're creating a problem that doesn't exist.
>> [JS] I can pass along my boss's email address, if you want to explain
>> him why it doesn't matter. Personally, I depend upon my job.
>> >If you just need sequential numbers for display purposes, generate
>> >them when you do the displaying. There's no need for those numbers to
>> >be in the database.
>> [JS] They are propagated into other databases that I do not control.
>> are managed and used by our main office in Japan. They notice
>> (except misspellings).