I've heard lots of comments over the years talking about how hard it is to work with UUIDs. I’d like to offer a different perspective. I switched to UUIDs from longints for primary keys 7 or 8 years ago. It took some careful programming to migrate the datafiles in place, but it was _so_ worth it. In all that time I’ve never once had to type in a UUID by hand. Instead, I just added the odd tool here and there that lets me copy a UUID to the clipboard. Then paste it for searching. As for looking for a UUID in a list, it’s pretty easy to look for a UUID by scanning for the first 2-3 characters and then checking that the last 2-3 characters match. In 4D list boxes, a column can be set up to show an ellipsis in the middle of a string (instead of the end) when a column is too small. This is perfect for UUID columns. Just make them wide enough to only show the first and last 3 characters. Just as easy as a longint, really.
-- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <[email protected]> <www.synergyfarmsolutions.com> > On Oct 24, 2018, at 11:17 AM, Chuck Miller via 4D_Tech <[email protected]> > wrote: > > No it is just painful let’s assume for some reason record in a many table > where assigns to wrong main table which would you rather type in to fix > 145764 or a 32 character UUID ********************************************************************** 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] **********************************************************************
