You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that there is a UUIDv7 and UUIDv6 bases (Base and AuditBase) already declared in advanced_alchemy, which is the package used to implement the UUIDBase and UUIDAuditBase. Big thanks to the manteiners of Litestar that also created this awesome advanced_alchemy package.
It would be great to mention the possibility to use UUIDv7 and UUIDv6 bases in Litestar Docs page "SQLAlchemy Models & Repository" because:
UUIDv7 (recommended) and UUIDv6 have some important advantages when used on DB indexes, since v6 and v7 are time sortable;
the advanced_alchemy package does not have almost any documention on its docs page, so it is really hard to find that UUIDv7 and UUIDv6 are available;
to use UUIDv7 and UUIDv6 bases advanced_alchemy rely on the rust based uuid-utils (very optimized), since functions to generate v6 and v7 versions are not included in the python std lib. I think it would be beneficial to Litestar users to know this dependency right in the Litestar docs if it mentions the v7 and v6 bases.
Also it would be better to mention that the standard Litestar UUIDBase and UUIDAuditBase uses UUIDv4 since this specific information is also not available anywhere on the Litestar docs.
Summary
I found that there is a UUIDv7 and UUIDv6 bases (Base and AuditBase) already declared in advanced_alchemy, which is the package used to implement the UUIDBase and UUIDAuditBase. Big thanks to the manteiners of Litestar that also created this awesome advanced_alchemy package.
It would be great to mention the possibility to use UUIDv7 and UUIDv6 bases in Litestar Docs page "SQLAlchemy Models & Repository" because:
Also it would be better to mention that the standard Litestar UUIDBase and UUIDAuditBase uses UUIDv4 since this specific information is also not available anywhere on the Litestar docs.
Note
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard
The text was updated successfully, but these errors were encountered: