So it is best to generate them with the 4th generation family of these functions.
GO UUID GENERATOR PLUS
In Postgres, you can generate UUIDs with the uuid_generate_v4() function.Īs an interesting aside, the Postgres documentation mentions that the first version of this function used the MAC address of the host machine, plus a timestamp, which meant it could reveal the identity of the machine and the time the particular record was generated, which is not great from a security perspective.Īnother interesting thing is that if you want reproducible UUIDs without any randomness in the generation process, you can use the v3 of this function with a specified “namespace” (any UUID) and a name. No natural ordering, again not great for debugging and for certain types of pagination techniques (this one on the wordpress blog cannot be used, for instance).Less human readable, thus less convenient to use them during debugging.Performance: on the same note as above, these are larger values which can adversly affect performance.I can imagine this being a significant drawback in some cases. Storage: UUIDs are 128-bit values as opposed to either 32 or 62 bit integers.
GO UUID GENERATOR CODE
They are practically unique in the universe - theoretically, there could be a collision, however, to get a grasp of how unlikely that is, have a look at this great post: Are UUIDs really unique?. They are unique, which is really handy when it comes to an identifier… They are unique across all tables, all your databases, all your systems.I wanted to use UUID for multiple reasons.
UUID stands for universally unique identifier (the term GUID refers to the same thing, typically used in the Microsoft world). In this post I would like to document my adventures of trying to set up a small Go project usingĭisclaimer: I don’t have vast experience in this topic, so take these tips with a pinch of salt.
0 kommentar(er)
