We have a project which involves daily creations/updates of at 1000's of nodes per day.
By my estimation, the cmsPropertyData table will grow at least 20 rows per node, and hence at least 100,000 rows per day.
While this is not a major concern for at least a couple years, I'm curious about contingency.
It would be good if Umbraco was using BigInt for primary keys. What are the implications of us changing the keys? I'm pretty sure I dont even wan to try this, but I'm just curious.
Umbraco's int primary keys
We have a project which involves daily creations/updates of at 1000's of nodes per day.
By my estimation, the cmsPropertyData table will grow at least 20 rows per node, and hence at least 100,000 rows per day.
While this is not a major concern for at least a couple years, I'm curious about contingency.
It would be good if Umbraco was using BigInt for primary keys. What are the implications of us changing the keys? I'm pretty sure I dont even wan to try this, but I'm just curious.
I read a Twitter conversation a while ago that Umbraco will be switching to guids: https://twitter.com/Shazwazza/status/557801467550388224
Jeroen
I used to be pro-guid. These days i've come full circle and now hate them as it's hard to just eye-ball a guid, vs an int.
is working on a reply...