GUID Factory

[David Merrill]

On Sun, Dec 17, 2000 at 09:54:32PM -0500, Jean-David Beyer wrote:
> David Merrill wrote:
> > 
> > On Sun, Dec 17, 2000 at 08:49:02PM -0500, Jean-David Beyer wrote:
> > > Christopher Browne wrote (in part):
> > > >
> > > > This is something that is indeed appropriately generated in the "engine,"
> > > > not in the DB; the relevance to the DB is to ask whether it can use the
> > > > GUID as one of its keys, and whether or not the DB supports foreign keys.
> > >
> > > What is this "foreign key" stuff? [snip]
> > >
> > > Whether you consider that field to be a foreign key or not depends on
> > > whether or not it is the primary key of another table, relation, or
> > > whatever you want to call it. Even then, you would not need to declare
> > > it to be a foreigh key unless you want to enforce the relationship
> > > between the two tables (which you probably should).
> > >
> > > Or am I missing something?
> > 
> > Just that the primary place a GUID is used is as a primary key, and
> > foreign keys in those tables' child tables.
> > 
> So of course an rdbms would support foreign keys, and this is a
> non-issue, right?

Right. If planned for in the table design, that is.

-- 
Dr. David C. Merrill                     http://www.lupercalia.net
Linux Documentation Project                dmerrill@lupercalia.net
Collection Editor & Coordinator            http://www.linuxdoc.org
                                       Finger me for my public key

I circle around, I circle around
The boundaries of the earth.
Wearing my long wing feathers as I fly.
		-- Native American Ghost Dance