Personally I tend to lean towards DB generated numeric primary key generation (i.e auto numbers, sequences etc)
I find that it is faster on indexing / select statements. Also - depends on your DB, and how comfortable you are with the way it handles Primary Keys. As per hiding primary keys in the URL scope - the encrypt() and decrypt() funtions always worked a treat for me :o) Which DB are you using tho? Mark ------------------------------------------------------------------ [EMAIL PROTECTED] ICQ: 3094740 Safe From Bees [ www.safefrombees.com ] Quoting Yorke Hinds <[EMAIL PROTECTED]>: > What is the support in the AU community for the > use of UUID over numeric primary keys in a DB/table? > > If not using UUID in as the primary key in the DB/table, > what can be used to encode or mask url variables that > include the primary key. I am aware of session variables > and form variables to hide numeric records. > > Anyone with experience - can you share. > > Thanks > > > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > > MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia > http://www.mxdu.com/ + 24-25 February, 2004 > > > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
