Neuen key generieren für das generate_key-Feld wenn ein Datensatz geklont wird#1589
Open
tyrant88 wants to merge 1 commit intoyakamara:masterfrom
Open
Neuen key generieren für das generate_key-Feld wenn ein Datensatz geklont wird#1589tyrant88 wants to merge 1 commit intoyakamara:masterfrom
tyrant88 wants to merge 1 commit intoyakamara:masterfrom
Conversation
|
Frage: ab welcher YForm Version wird das Feld uuid denn neu erstellt. Ich sehe dass das bei mir nicht der Fall ist. Die uuid bleibt gleich beim Klonen. |
Contributor
Author
|
Version 5 |
Contributor
Author
|
hier noch mal der Verleich mit dem uuid Feld: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Im Feld "uuid" gibt es diesen Mechanismus schon.
Ich hätte ihn auch gerne für das "generate_key"-Feld.
Das kommt z.B. in der ycom_user Tabelle als "activation_key" vor und hat dort auch ein validate_unique.
Daher kann man keine ycom_user klonen, denn den "activation_key" kann man im Backend nicht ändern.