You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On larger systems the auto increment causes a table lock, which decreases performance. With UUIDv4 primary keys the whole UoW can be built and then flushed without any back-and-forth to the database.
I'm guessing one of the challenges can be sorting. However, a precise microsecond time stamp could solve it easily.
WDYT about such an addition?
The text was updated successfully, but these errors were encountered:
@kiler129 Can you provide any article about this behavior in database? Anyway you should create primary key - unique index will be checked for every entry before inserting.
On larger systems the auto increment causes a table lock, which decreases performance. With UUIDv4 primary keys the whole UoW can be built and then flushed without any back-and-forth to the database.
I'm guessing one of the challenges can be sorting. However, a precise microsecond time stamp could solve it easily.
WDYT about such an addition?
The text was updated successfully, but these errors were encountered: