U
ujj1
Guest
We talked about a GUID data type as part of the Progress Exchange 2014 "InfoExchange" session. The use case was for when we want to uniquely identify a record with a unique id that is beyond the database level (i.e. global). Instead of identifying a customer order as order-num 1, it would be identified with a GUID. Whether it is part of the PK or just a new field would be a concern of the application/database designer. It would be a 16 byte binary to optimize storage. Currently we store a guid in a character string which would be 32bytes (with the dashes removed). A way to display the binary guid as a string would be needed also for external consumption. There was also talk about sequential GUIDs also to optimize using as a database key field.
Continue reading...
Continue reading...