How do correctly create a uuid for a new database entry?

[Mr.Rubi]

For php, the @sbecks solution works perfectly. I will only refine the link to a specific post, so as not to search. Here it is:

Better password encryption

I agree it would be a great addition to access these options straight from the UI. Though I think it’s possible to use password_hash() and password_verify() by making custom formatters… Create a new php file in dmxConnectLib, Formatters called custom.php (if you already have a custom file just add the new formatters to it. [image] Add the passwordHash and passwordVerify functions shown below (the UUID formatter enables v4 UUIDs on insert), https://stackoverflow.com/questions/2040240/php-func…

As for protection against a possible UUID repeat (I understand that the probability is extremely small, but there is an option to completely exclude such an event), I plan to solve this by using additional steps in the server action:

1. UUID Generation will not be done while inserting a record, but before. The generation will be in a while loop, which will check whether the new uuid matches the existing ones in the database. If there is a match, the loop will repeat generation until a unique uuid is generated.
2. at the stage of inserting a record, the value of the already generated and verified uuid from step 1 will simply be inserted into the field.

In this case, we will get 100% protection from possible UUID duplication.