Closed caiquecastro closed 4 years ago
Probably fix #93
I don't think this will preserve functionality, though, as you're just resolving implicitly from string or bytes, rather than a specific version.
That said, I don't think you can really use UUID versions 2, 3, or 5 anyway, as they require additional parameters be passed anyway.
Fixed in b273499c41f62a8601a385f1652ba5ee584b0a5f
@michaeldyrynda
If 'ordered' is now pipe through uuid 6 (said in the release notes), will it have any conflicts or issues with my previous uuids that are already generated with Str::orderedUuid() ? Like will my uuid column still be correctly indexed in an ordered manner? with a mix of uuid 6 and Str::orderedUuid()?
https://github.com/laravel/framework/blob/7.x/src/Illuminate/Support/Str.php#L693
Hopefully you know the answer, thank you.
It may be possible, given that the ordered UUID does not appear to actually be a proper time-ordered UUID.
It may be worth considering updating the UUID to use the new format which forms a truer representation of an ordered UUID, albeit from a draft specification.
Noted the potential breaking changes, shall restrict to 6.1.1 for this package for the time being then.
Needs to change on dyrynda/laravel-efficient-uuid package: