A
agent_008_nl
Guest
Ah, see this gentle discussion a bit tardy, too tardy to throw some vitriol in (but to be honest I'm waiting for a new delivery, currently my barn is empty). Agreed with what is said here by Marian (and others that said the same). I only object to the auto-increment integer field. A sequential number is needed for example for an "order" table, where you need to know what the order of creation is. The guid does not give you that. But in most other cases a guid is preferable to me (in case of the order table you can have the guid (PK) next to the sequence (AK)). The generation of the unique field is coupled to the db. The generation of the guid is not. You can assign it on all kinds of client-types and simply set up complete relations in a dataset on the client. Furthermore you get a problem when merging tables from two sources when you only use the sequence.
Continue reading...
Continue reading...