Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 15 of 15 total
Thread Autoinc rollover
Mon, Apr 15 2013 8:46 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


How does Autoinc find the next hole to use after its rolled over?

Roy Lambert
Wed, Apr 17 2013 9:54 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< How does Autoinc find the next hole to use after its rolled over? >>

It doesn't.  That's an issue for the developer to deal with, especially
since the chance of encountering a roll-over in the lifetime of a database
is very, very rare.

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Apr 17 2013 10:30 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

><< How does Autoinc find the next hole to use after its rolled over? >>
>
>It doesn't. That's an issue for the developer to deal with, especially
>since the chance of encountering a roll-over in the lifetime of a database
>is very, very rare.

That's what I thought but Arthur seems to think a bit differently. I think his users could be in for a looong wait if it does roll over <vbg>

Roy

Fri, Apr 19 2013 12:22 PMPermanent Link

Arthur Williams

Zarksoft

Avatar

Not at all. I never for a minute thought DBISAM handled finding free values after the index had rolled over. This piece of sh-t that I have here called Accuracer has an option to specify how AutoInc rollover is handled. I was simply curious as to what DBISAM did in that particular case.

I came late to Delphi, I normally program system exits and utilities in S/390 Assembler. I have no background in BDE usage so my use of these little db programs tends to be somewhat unconventional. To my way of coding starting the autoinc at 2,147,483,000 is just as valid as starting at 1.

>>
Roy Lambert wrote:

Tim

><< How does Autoinc find the next hole to use after its rolled over? >>
>
>It doesn't. That's an issue for the developer to deal with, especially
>since the chance of encountering a roll-over in the lifetime of a database
>is very, very rare.

That's what I thought but Arthur seems to think a bit differently. I think his users could be in for a looong wait if it does roll over <vbg>

Roy
Fri, Apr 19 2013 12:58 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Arthur

>Not at all. I never for a minute thought DBISAM handled finding free values after the index had rolled over. This piece of sh-t that I have here called Accuracer has an option to specify how AutoInc rollover is handled. I was simply curious as to what DBISAM did in that particular case.

Good of you to explain

>I came late to Delphi, I normally program system exits and utilities in S/390 Assembler. I have no background in BDE usage so my use of these little db programs tends to be somewhat unconventional. To my way of coding starting the autoinc at 2,147,483,000 is just as valid as starting at 1.

Oh well, if you said you used assembler to start with <vbg>

Roy
« Previous PagePage 2 of 2
Jump to Page:  1 2
Image