Kirk, I am not suggesting using SS numbers, or anything the user can change/touch as a linking value. a longint (or other sequential value [text] - like a license plate) generated for each new record for each table which is used explicitly for identifying the record and possibly linking relational data, as needed.
On Wed, 24 Oct 2018 09:59:07 -0700, Kirk Brooks via 4D_Tech wrote: > Another way to look at this is in terms of separating the logical structure > from the data. Using UUIDs compels you to think about the logical structure > separately from the contents. That's a good thing. I agree it can be useful > to have a unique serial number on some tables. But that doesn't mean it's a > good idea to use it as a key. Social Security numbers are the perfect > example of this. I don't think the 2 fields vs 1 field is really an issue. I do see what you are getting at though. > Another instance is being able to identify records any place in the > database by a single value. For instance, I have a table for recording > notes users attach to records. The idea it to be able to attach a note to > anything. If I'm using longints it takes two fields to identify the record, > table # & id #. With a UUID I only need one. Other points well taken. --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
