× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I'd go with something like this:

CREATE TABLE QGPL/T1 
(
  F1 CHAR ( 16) FOR BIT DATA NOT NULL, 
  UNIQUE(F1)
) 

You shouldn't do any validation as you can't know what is a valid GUID (can
you?).  
Unique constraint should be sufficient for validation against duplicate
values (highly unlikely but better safe than sorry).

Elvis

-----Original Message-----
Subject: Storing Guids in DB2/400

All,
 
We've got a need to store Guids in a DB2 table. At first we thought we
could use the RowID column type, but there can be only one of those on a
given table (makes sense). I guess we could use a char(16) to store it
in "native" format, or a char(36) to store it in character format
(7AF7EAA1-D035-4E22-BAD8-7F5640ECC4A7). My problem with using a char()
field is we could also store '*anything' in that field and the database
would be just fine with that. 
 
So, my question is, are we missing a datatype that will store Guids? And
if not, does anyone have a check() clause that will validate a Guid
before we store it in the database?
 
-Walden



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.