>
>A good reason to not use Integer based generators is in the case where data
>needs to be replicated to other databases, and the primary keys need to
>remain unique across multiple databases. And don't tell me to use another
>composite key on other compositely "unique" fields.

Well sure - but you can replace them with the PK value of your choice. I
use integers because I can; but I would use long or double if I had to; or
(as I have sometimes done) had a single table visible to all software from
which generated values can be gotten.

I think the issue is more divorcing what the DB or your code needs to
operate efficiently, and what the user would like to see, rather than
whether integer or any other values make better PKs.

Regards

Tim


[Non-text portions of this message have been removed]