×
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.
But, I think you need to look at the purpose. I, too, would not use
this for something where you need a truly unique sequential number -
like invoices. I don't think that is the intent. But, for uniquely
identifying a row (record) and establishing relationships across tables,
it's a wonderful tool.
The Centerfield article by Dan Cruikshank and a couple of others by Kent
Milligan on Identity Columns, Sequences, and Constraints should be
required reading for every IBM-i developer.
luisro58@xxxxxxxxx 11/25/2009 12:09:10 PM >>>
<snip>
As per the business cases that David comments, I suppose that this
(the sequence object) could be seen as just another tool that SQL
provides. Myself, am a little uneasy about the storing of the data in
a *DTAARA (something that sometimes gets overlooked when restoring or
saving). Also, the fact that I can't get a guarantee of the sequence
can give some problems (think, for example, invoice numbers).
</snip>
midrange.com
