I'd like to know about any potential issues of choosing a char(32) as
the column type of a primary key instead of BIGINT or some other numeric
type. A little background.
I would like to generate a unique identifier to use as a primary key for
our application instead of using an AUTOINCREMENT
-Would joins of tables with character based primary keys be slower than
-those with numeric based keys?
Yes a join on a character based key is generally slower then on an
integer key. Key lookups in general are faster on integer based keys.
Since your PRIMARY KEY storage requirement is 30
On 28-Mar-2003 Aaron Williams wrote:
I'd like to know about any potential issues of choosing a char(32) as
the column type of a primary key instead of BIGINT or some other numeric
type. A little background.
I would like to generate a unique identifier to use as a primary key for
our
