×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I like the solution of the sequence object. What Chuck was also trying to
say was that if you already have either a unique or primary key on this
same column you need to null out existing values or something before you
put your new values in there. Otherwise your new value may be the same as
a value further down the line. Well, maybe not, if you start your
sequence out at 1 and you are reading the table sorted by this key value.
For example, if you are on the first row, sorted by this number, and are
changing the value to a 1 then how could 1 be in use further down? The
answer is: if you have any null values, started the numbering at zero (or
lower), used numbers that incremented by less than whole number
increments, etc.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
