The stamp and serial both do sequential assignments and are therefore very easy to guess. The GUID generates (what appears to be) a random sequence of hex digits that is unique throughout the database and are useful in URL parameters. I have devised a simple yet effective method on my own but thanks for the info about the stamp default, this may come in handy down the road when the serial default won't do.
-----Original Message----- From: Zabach, Elke [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 11, 2004 1:32 AM To: Kevin Wilson; [EMAIL PROTECTED] Subject: RE: Universal Unique Identifier [EMAIL PROTECTED] wrote: > > > Is there any function in MaxDB that operates similar to > MS-SQL's NEWID() > function? The NEWID() generates a globally unique identifier. To make clear what confuses me at the first moment: 'globally unique identifier' is not meant to create something like a name (the word identifier is used in MaxDB where one speaks of a name) but a unique identification. There is no chance in MaxDB to create a globally unique identification which cannot be created by any other means. You can use CHAR (8) BYTE and fill it with STAMP http://www.mysql.com/documentation/maxdb/1b/2e97e1b42a11d2a97100a0c9449261/f rameset.htm and you will be assured that no other column filled with STAMP will have the same value. You can use the normal SYSKEY (the primary key always there if the user does not define a primary key itself for a table). This column cannot be changed, but selected. You can use SEQUENCES or SERIAL http://www.sapdb.org/7.4/how_tos/numbergen/howto_producenumgen_eng.htm to assure uniqueness in one table or all tables which uses this sequence. Elke SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
