vsql_nanoid generates them in SQL, so a
public-facing identifier can be produced at insert time rather than in your
application.
A third party writes and maintains this extension. VillageSQL does not build,
test, or ship it, and the description below follows the maintainer’s own
documentation. Read that documentation before you rely on it.
Install
Build it from the repository, then install it into the server. It needs OpenSSL for its random source.What it adds
See also
- UUIDs in MySQL — the other way to generate an opaque identifier
- Primary key strategies — what a random key costs on an InnoDB index
- Available extensions — the full catalog
- intojhanurag/vsql-nanoid — source, examples, and the known limitations