On Mon, 24 Oct 2011, Vincent Snijders wrote:
2011/10/24 <michael.vancann...@wisa.be>:
On Mon, 24 Oct 2011, Vincent Snijders wrote:
2011/10/22 Graeme Geldenhuys <graemeg.li...@gmail.com>:
1) Use a GUID created at the time you do the Insert. This also means
you can do Master/Detail records with no problems at all.
I consider this bad advice. GUID are bad primary keys, because of
their size and the fact they are not sequential by design.
You just discarded most Microsoft product designs =-)
They use GUIDs all over the place :-)
Still, I won't use them as primary (clustered) key in Microsoft sql
server. If the business rules require a guid, it may become a unique
key in the table, but not a primary key.
As a rule, I don't use GUIDs at all; Same arguments as you seem to have.
And, very important but often underestimated:
At least our clients can read an integer primary/foreign key aloud over the
phone when the need arises. I can't hear them doing that with a GUID :-)
Michael.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
