Each table insert would require a call to the a single function to get the next PK value and an additional table would be used to store the current set of values. (The developers want to put some additional meaning into a PK value and a sequence would not be sufficient, hence the need for the PK generating function and current value table).
I've never seen this done before and I would think this application would suffer greatly from contention when performing a large number of concurrent inserts.
Has anyone ever encountered a design like this? Is this a bad design?
Thanks.
Brian