[11.x] Implement HasV7Uuids to use with MariaDB native uuid data type #52029
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.
This PR addresses issue #51883. The referenced issue points out that the
uuid
data type in MariaDB has problems withorderedUuid
, which is used by theHasUuid
trait.MariaDB's documentation suggests using
uuid1
or UUID versions >= 6 as a better option.With this PR, Laravel developers can better utilize their MariaDB UUID columns in terms of performance, indexing, ordering, and storage. Using UUID v7 instead of the ordered UUID v4 currently used by Laravel will:
Additionally, this PR introduces a new
uuid7
helper method inStr
.If this PR is merged, necessary edits to the documentation will be required to guide users on using this trait with MariaDB instead of HasUuid.