1/25/2024 0 Comments Mysql uuidThis special column is used to technically identify records and can be used as foreign keys in relations. Even if the primary key can be composite (built of several columns), it is a widespread good practice to dedicate a special column (often named id or id_) to this end. But most of the time, using UUID as the primary key is a sign of pre-mature optimization and it's also a choice hard to revert afterward.Why Do We Need Technical IDs in the First Place?Īny properly designed relational database table owns a Primary Key (PK) allowing you to uniquely and stably identify each record. There are valid cases of choosing UUID e.g. And most applications are less complex than those issue tracking tools. Jira, Apple's Radar, Google's issue tracker, etc. In fact, all major issue tracking systems use an integer as the issue id. and issue id such as issue/123 is definitely more readable than issue/b1e92c3b-a44a-4856-9fe3-925444ac4c23. The tool likely will have at most 5 figure projects each containing 5 figure issues. Take the classic issue tracking/project management tool as an example. order #), inspected by the operation engineer, customer support etc.ĩ9.9% of the applications won't reach internet scale and they just consist of several models allowing CRUD operations, containing thousands of records. The primary key is not only used by the system, it's also exposed to the end user (e.g. Numbers are easy to write, easy to remember and easy to communicate. Why? Readability, and readability leads to simplicity. 95% of the time, the default choice should always be Auto Increment Integer. Attackers can also scan the integer range to explore leakage (though it shouldn't happen if ACL is implemented correctly).Īs listed above, there are Pros and Cons between the 2 approaches.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |