Does the user identity have to be an INT in the database field or can it be a varchar. I am trying to make encrypted user ids to improve security.
Oh great! I will need to redo it then. I have the row number as the usr id as autogenerated but he DB.
So in your example would you make the assigned_user_id the ‘key’ in the table or does the row number end up being the key still
In the view above, the appointment_id is the primary (note the PK below it). I don’t ever utilise row numbers for anything. To create my primary_keys, I use a UUID gen function in Postgres.

is it the same syntax for MySQL/MariaDB?
I read that some convert hexadecimal UUID into binary?
I don’t know. I’ve not used either. Worth reading this:
NO problem. I’ve found it UUID(). Thanks for the advice.
I’m going to have to go back and change a lot of things to now use the new UUID field as a user ID and the Identify field in Wappler 
but it will be more secure.
Thanks for the article. Will read for sure!
We actually just also added uuid support in the database manager and it’s usage as primary keys.
The default value for uuid primary key is also set to the uuid() function so they are auto generated
so if I have setup my Security Identify as the field with the UUID, it should work fine? Security Identity doesn’t have to be just an INT?
