It's my understanding that a PK in MySQL is basically the same as a
unique index -- for MyISAM tables at least. For InnoDB it's a bit
different with InnoDB storing rows within the PK index (and inserting
a hidden PK if none is provided).
In short: I don't think you'll see any better perfo
On Wed, Nov 08, Jon Frisby wrote:
> On Nov 7, 2006, at 6:47 PM, Michael Fischer wrote:
>
> >
> > Any thoughts on using BINARY(N) or CHAR(N) as a primary key?
> >
> > Performance issues? In mysql, in general?
> >
> > Yes, in the context of the application, there is a very good
> > reason for doing
I'm curious to know why simply having a UNIQUE constraint on the
column is inadequate...
-JF
On Nov 7, 2006, at 6:47 PM, Michael Fischer wrote:
Any thoughts on using BINARY(N) or CHAR(N) as a primary key?
Performance issues? In mysql, in general?
Yes, in the context of the application, th
