如何生成像“aX4j9Z”这样的短uid (JS 中)
对于我的网络应用程序(在 JavaScript 中),我想生成简短的 guid(对于不同的对象 - 实际上是不同的类型 - 字符串和字符串数组),
我想要像“aX4j9Z”这样的东西作为我的 uids(guid)。
因此,这些 uid 对于 Web 传输和 js 字符串处理来说应该足够轻量,并且对于不庞大的结构(不超过 10k 元素)来说非常独特。我所说的“非常独特”是指在生成 uid 后,我可以检查该 uid 是否已存在于结构中,如果存在则重新生成它。
For my web application (in JavaScript) I want to generate short guids (for different objects - that are actually different types - strings and arrays of strings)
I want something like "aX4j9Z" for my uids (guids).
So these uids should be lightweight enough for web transfer and js string processing and quite unique for not a huge structure (not more than 10k elements). By saying "quite unique" I mean that after the generation of the uid I could check whether this uid does already exist in the structure and regenerate it if it does.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(13)
获取一个简单的计数器,从 100000000 开始,将数字转换为基数 36。
您可以轻松拥有 20 亿个优雅的唯一 ID,就像 YouTube 一样
Get a simple counter to start from 100000000, convert the number into radix 36.
You can comfortably have 2 billion elegant unique ids, just like YouTube
以下生成 62^3 (238,328) 个 3 个字符的唯一值,前提是区分大小写是唯一的并且所有位置都允许使用数字。如果需要不区分大小写,请从 chars 字符串中删除大写或小写字符,它将生成 35^3 (42,875) 个唯一值。
可以很容易地进行调整,以便第一个字符始终是一个字母或所有字母。
毫无疑问,它可以被优化,并且在达到限制时也可以拒绝返回 id。
The following generates 62^3 (238,328) unique values of 3 characters provided case sensitivity is unique and digits are allowed in all positions. If case insensitivity is required, remove either upper or lower case characters from chars string and it will generate 35^3 (42,875) unique values.
Can be easily adapted so that first char is always a letter, or all letters.
No dobut it can be optimised, and could also refuse to return an id when the limit is reached.
考虑到 ES6 功能的实际威力,我们可以在 JavaScript 中生成哈希 ID,而无需依赖第三方库。
我使用 JavaScript 目前为我们提供的内置函数实现了一个非常简单的生成器。此实现使用
Crypto.getRandomValues()
和Uint8Array ()
如下代码所示:此实现使用这些字符:[
AZ
]、[az
]、[0-9
] 如果我们添加,总共有 62 个字符_
和-
最多可完成 64 个字符,如下所示:注意:
每小时生成 1000 个 ID 长度为 6 个字符的 ID,大约需要 2 天时间才能有 1% 的概率发生至少 1 次冲突。将其实施到您的项目中时请记住这一点。
Considering the actual power of ES6 features we can generate hash IDs in JavaScript without relying on third-party libraries.
I implemented a very simple generator using the build-in functions that JavaScript offers to us these days. This implementation uses
Crypto.getRandomValues()
andUint8Array()
as shown in the code below:This implementation uses these characters: [
A-Z
], [a-z
], [0-9
] in total they are 62 characters, if we add_
and-
it will complete up to 64 characters like this:Note:
It will take around 2 days in order to have a 1% probability of at least one collision for 1000 IDs generated per hour with ID length of 6 characters. Keep this in mind when it is implemented into your project.
这将生成一系列唯一值。它通过在所有值都用尽时增加字符串长度来改进 RobG 的答案。
用法:
此要点包含上述实现和递归版本。
This will generate a sequence of unique values. It improves on RobG's answer by growing the string length when all values have been exhaused.
Usage:
This gist contains the above implementation and a recursive version.
只是随机生成一些字符串:
just randomly generate some strings:
您可以将 GUID 缩短为 20 个可打印 ASCII 字符,而不会丢失 GUID 的信息或唯一性。
杰夫·阿特伍德(Jeff Atwood)几年前在博客中谈到了这一点:
装备我们的 ASCII Armor
You can shorten a GUID to 20 printable ASCII characters without losing information or the uniqueness of the GUID.
Jeff Atwood blogged about that years ago:
Equipping our ASCII Armor
该解决方案将 Math.random() 与计数器结合起来。
Math.random() 应该给出大约 53 位的熵(与 UUIDv4 的 128 位相比),但是当与计数器结合使用时,应该为临时 ID 提供足够的唯一性。
特点:
id
和 Reactkey
This solution combines
Math.random()
with a counter.Math.random()
should give about 53 bits of entropy (compared with UUIDv4's 128), but when combined with a counter should give plenty enough uniqueness for a temporary ID.Features:
id
and Reactkey
您可以使用 md5 算法生成随机字符串。 md5 是节点包,
每次都会生成唯一的字符串。
You can use the md5 algorithm for generating a random string. md5 is the node package
This will generate unique string every time.
我使用此 TypeScript 函数在数据库中创建比 UUID 更具可读性的唯一标识符。请注意,插入记录时,我捕获重复键异常并使用新 ID 重试。
它生成类似
20230506VJDMQD
的 ID。日期前缀对唯一性有很大帮助,特别是当您在数据库中长期创建数千条记录时。它对于客户编号或发票编号等内容也非常有帮助,其中日期部分提供了附加信息,而不仅仅是唯一性。
可以很容易地将其适应您喜欢的任何字符集,如果您不需要日期前缀,则可以轻松地从代码中删除该部分。
如果您每天需要生成数百万个 ID,那么您可以将循环计数从 6 增加到更大的数字,但在某些时候您也可能只使用 UUID。
如果你真的只想要 6 个字符,那么 JavaScript 中的简化版本是
I use this TypeScript function to create unique identifiers in my database that are much more readable than UUIDs. Note that when inserting records I catch the duplicate key exception and retry with a new ID.
It generates ids like
20230506VJDMQD
.The date prefix helps a lot with uniqueness, especially if you create thousands of records in the database over a long period of time. It's also super helpful for things like customer numbers or invoice numbers, where the date part provides additional information, not just uniqueness.
It's very easy to adapt this to any set of characters you prefer, and if you don't want the date prefix it's easy to remove that part from the code.
If you need to make millions of IDs per day, then you could increase the loop count from 6 to a bigger number, but at some point you might as well just use UUIDs.
If you really want just 6 characters, then the simplified version in JavaScript is
有关预打包解决方案,请参阅 @Mohamed 的回答(
shortid
包)。如果您没有特殊要求,请首选该解决方案,而不是本页上的任何其他解决方案。6 个字符的字母数字序列足以随机索引 10k 集合(366 = 22 亿和 363 = 46656)。
随机生成的UID在生成~√N个数字后会发生冲突(生日悖论),因此需要6位数字才能安全生成而不进行检查(旧版本仅生成4位数字,如果不检查则在1300个ID后会发生冲突) 。
如果进行碰撞检查,位数可以减少 3 或 4,但请注意,当生成越来越多的 UID 时,性能会线性下降。
如果您需要唯一性而不是不可预测性,请考虑使用顺序生成器(例如
user134_item1
、user134_item2
...)。您可以“散列”顺序生成的字符串以恢复不可预测性。使用 Math.random 生成的 UID 并不安全(无论如何您都不应该信任客户端)。在关键任务中不要依赖其独特性或不可预测性。
See @Mohamed's answer for a pre-packaged solution (the
shortid
package). Prefer that instead of any other solutions on this page if you don't have special requirements.A 6-character alphanumeric sequence is pretty enough to randomly index a 10k collection (366 = 2.2 billion and 363 = 46656).
UIDs generated randomly will have collision after generating ~ √N numbers (birthday paradox), thus 6 digits are needed for safe generation without checking (the old version only generates 4 digits which would have a collision after 1300 IDs if you don't check).
If you do collision checking, the number of digits can be reduced 3 or 4, but note that the performance will reduce linearly when you generate more and more UIDs.
Consider using a sequential generator (e.g.
user134_item1
,user134_item2
, …) if you require uniqueness and not unpredictability. You could "Hash" the sequentially generated string to recover unpredictability.UIDs generated using
Math.random
is not secure (and you shouldn't trust the client anyway). Do not rely on its uniqueness or unpredictability in mission critical tasks.08/2020 更新:
shortid
已被弃用,取而代之的是更小的 nanoid更快:更多信息请参见:https://zelark.github.io/nano-id-cc/
旧答案
还有一个很棒的npm包:shortid
用法
Update 08/2020:
shortid
has been deprecated in favor of nanoid which is smaller and faster:More info here : https://zelark.github.io/nano-id-cc/
Old answer
There is also an awesome npm package for this : shortid
Usage
这是一个单行,但它只给出小写字母和数字:
Here is a one liner, but it gives only lowercase letters and numbers: