Thanks for your response @WardenCommander. The latter is a good workaround. However, does this not cause inefficiencies in the database? Where the user now has to search for a uuid (potentially across multiple tables) that is not indexed and optimised for searching, such as an id column.
over 1000’s of rows, limited db resources and potentially concurrent users, this adds up? Throwing more compute power at the problem is not cost effective.