How In-Memory Database Objects Affect Database Design: Hybrid Code

Posted by drsql on SQL Blog See other posts from SQL Blog or by drsql
Published on Sat, 09 Aug 2014 01:49:18 GMT Indexed on 2014/08/18 16:38 UTC
Read the original article Hit count: 276

In my first attempts at building my code, I strictly went with either native or on-disk code. I specifically wrote the on-disk code to only use features that worked in-memory. This lead to one majorly silly bit of code, used to create system assigned key values. How would I create a customer number that was unique. We can’t use the Max(value) + 1 approach because it will be very hideous with MVCC isolation levels, since 100 connections might see the same value, leading to lots of duplication. You...(read more)

© SQL Blog or respective owner

Related posts about Development

Related posts about Devlink