RE: Storing Guids in DB2/400

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden 
H. Leverich
Sent: Wednesday, November 08, 2006 3:14 PM
To: Midrange Systems Technical Discussion
Subject: RE: Storing Guids in DB2/400

All the GUID is is a 16 byte number, right?  

There actually is a little logic to it, see
http://en.wikipedia.org/wiki/Globally_Unique_Identifier for 
some of the
details, including having to deal with network byte ordering. 

However, the bigger problem is if I use the char(36) approach then
anything coule be stored in the field, and most of it wouldn't be a
"valid" guid of any kind.

-Walden

From http://www.itu.int/ITU-T/studygroups/com17/oid/X.667-E.pdf

"Apart from determining if the variant bits are set correctly, and that
the Time value used in a time-based UUID is in the future (and therefore
not yet assignable), there is no mechanism for determining if a UUID is
valid in any real sense, as all possible values can otherwise occur."

HTH,


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121