Martijn Tonies wrote:

> What you're doing is assigning a meaning to an artificial generated primary
> key value.
>
> This, IMO, is bad design.

Sorry for using PK, I can see that was confusing. Actually, it doesn't
have to be a primary key, it is just about using trigger and generator
to get some kind of sequence. And when doing this, having INSERT INTO...
SELECT FROM... ORDER BY... can be the quickest way to achieve this
sequence (at least as long as UPDATE statements cannot ask for some kind
of ORDER BY).

Moreover, the tables I'm talking about are more or less temporary tables
only of interest for further processing in creating a "flat table".

I agree that a primary key in normal tables should bear no meaning.

Set