Quote:
Originally Posted by John Adams
I doubt SQL cares what your PK is, but I believe our shared memory modules do. If you read in IDs 1-100,000, it takes up 'x' amount of memory. If you start making up new IDs and now have to read in ID 1-1,000,000, that's a helluva lot more memory (if we pad that empty space, which I think we do from an earlier discussion).
|
I believe that the IDs are read and stored in a 1 to <maxid> space... there are other programming models for handling what could be a "sparse matrix/list" if the range of values for IDs were spread out to accomodate a new identification scheme. I think that (EMU code change) is far less of an issue than just managing the data transformations that would have to happen in the SQL database...
Threaded Mode
