(but only a few!) developers use CreateUUID() for creating a record's PKID,
and therefore have the PKIDs be strings rather than integers. (their
argument was that they didn't have to worry about another record being
inserted in between when the CreateUUID() was called and when the first
record was actually inserted into the DB) I questioned them about the
impact this has on their joins and a few said they never saw a real decrease
in performance (I don't have any proof, but I inherently distrust that
statement!) and a few others say that they used that only for creating a
unique ID, but that they had a separate ID field in each table that was
numeric which they used for joins. This part seemed like overkill to me -
surely there's some stored procedure that accomplishes all of this?
Can someone who actually thinks about this stuff regularly (uh, that means
you, Dave Watts!) explain whether there's any merit to either group of
people above? I thought the whole point of "autonumber" fields was exactly
to make this issue moot.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
