[FOLIO-1003] Use an IDENTITY columns instead of UUIDs for primary keys Created: 31/Dec/17  Updated: 12/Nov/18  Resolved: 01/Jan/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Jon Miller Assignee: Kurt Nordstrom
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

I think it would better if the tables in FOLIO used IDENTITY columns instead of UUIDs. This is more of a general issue, not just with the user module. In the case of the user module it might not make that much of a difference performance-wise, since the number of users in the system probably won't be that great. However, as a general rule, I think it is not a good idea to use random values as primary keys. The primary key column has a clustered index. Normally, you want the ids in sequential order. Or the DBMS may need to shift the rows around upon INSERT. This is probably more of an issue for something like a bibs table where you have millions of rows. But, it would be good if the system used identity columns across the board. An added advantage is that the ids take less space on disk. Also, they are easier to work with in terms of searching. An INT value is easier to type in that a long hexadecimal string. It would also be good if FOLIO upgraded to PostgreSQL 10 which supports identity columns using the standard SQL syntax.



 Comments   
Comment by Kurt Nordstrom [ 31/Dec/17 ]

This isn't a mod-users issue, as mod-users merely follows FOLIO policy for identifiers. It would be better posted in the FOLIO project, where it can be reviewed by project coordinators.

Comment by David Crossley [ 01/Jan/18 ]

See FOLIO-1002 Closed

Generated at Thu Feb 08 23:10:06 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.