Actions
Task #183
closed
Redesign database primary keys to uuid
Start date:
11/04/2016
Due date:
% Done:
100%
Estimated time:
Owner:
Description
We are using bigint data type as primary key now. But we will need two features in future:
- easy data migration / cloning between environments (preproduction - production)
- generatate primary key on client (cloning, offline access)
We want use uuid as PK, but before this, we need answers to:
- how index size grows - e.g. for two entities parent - child - ~50 milion records
- how insert time grows
...
Postgresql will be used for first test.
Updated by Radek Tomiška over 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
I've made some tests to get the answers. Results are here - https://proj.bcvsolutions.eu/ngidm/doku.php?id=navrh:identifikatory#testovani_primarnich_klicu
Using of guid is stable, but with some cons.
Actions