It really does depend on what you are aiming to model. In some cases the unique rowid numeric key will be the best solution, in other cases there may be a column, or COMBINATION of columns in your table that uniquely identify each row - and in that situation can be used for a JOINT primary key.
On 17/10/06 00:18, "Stefan" <[EMAIL PROTECTED]> wrote: > >> On Oct 16, 2006, at 11:51 AM, Daniel Stenning wrote: >> >>> Don't forget that in a relational SQL based database it is good >>> practice >>> wherever possible to build a unique key from actual data in the row >>> ( record >>> ) . This might very often require a JOINT key to be used, for >>> example >>> surname and postcode. > > I didn't follow the complete thread. Thus this web-based GUID generator > might or might not be of help: > > http://kruithof.xs4all.nl/uuid/uuidgen > > The link contains references to papers regarding GUID generation. > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives of this list here: > <http://support.realsoftware.com/listarchives/lists.html> > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
