Le lundi 03 octobre 2005 à 16:24 +0200, Bastian Balthazar Bux a écrit :
> Yannick Warnier wrote:
> > Le lundi 03 octobre 2005 à 12:29 +0200, Martijn Tonies a écrit :
> >
> >>>Using PhpMyAdmin, I seldom get the warning message:
> >>>PRIMARY and INDEX keys should not both be set for column `ID`
> >>
Yannick Warnier wrote:
> Le lundi 03 octobre 2005 à 12:29 +0200, Martijn Tonies a écrit :
>
>>>Using PhpMyAdmin, I seldom get the warning message:
>>>PRIMARY and INDEX keys should not both be set for column `ID`
>>>
>>>I understand its meaning, but I was wondering to what extent having a
>>>field
Le lundi 03 octobre 2005 à 12:29 +0200, Martijn Tonies a écrit :
> > Using PhpMyAdmin, I seldom get the warning message:
> > PRIMARY and INDEX keys should not both be set for column `ID`
> >
> > I understand its meaning, but I was wondering to what extent having a
> > field indexed AND being a prim
Yannick Warnier <[EMAIL PROTECTED]> wrote on 03/10/2005 11:18:05:
> Hi all,
>
> Using PhpMyAdmin, I seldom get the warning message:
> PRIMARY and INDEX keys should not both be set for column `ID`
>
> I understand its meaning, but I was wondering to what extent having a
> field indexed AND being
> Using PhpMyAdmin, I seldom get the warning message:
> PRIMARY and INDEX keys should not both be set for column `ID`
>
> I understand its meaning, but I was wondering to what extent having a
> field indexed AND being a primary key might slow down/speed up my
> queries.
>
> Is that gonna take twice
Hi all,
Using PhpMyAdmin, I seldom get the warning message:
PRIMARY and INDEX keys should not both be set for column `ID`
I understand its meaning, but I was wondering to what extent having a
field indexed AND being a primary key might slow down/speed up my
queries.
Is that gonna take twice the