On Jan 3, 2008 4:23 PM, Tanner Postert [EMAIL PROTECTED] wrote:
When I try to add a force index (PRIMARY) after the media table to try and
make is use PRIMARY, rather than TYPE, the optimizer switches and uses no
key at all.
It usually knows better than you do about indexes.
I've tried to
Can you do a show create table Table1 and see how the index is defined?
Original Message
On 2/25/04, 12:02:43 PM, James Lamanna [EMAIL PROTECTED] wrote
regarding Problem with indexes:
So I'm having issues with indexes in mysql 4.0
I issue the following:
Create Index Index1 on Table1
Found out that the problem was actually a bug in 4.0.17.
Upgrading to 4.0.18 seems to have fixed the problem.
Noted here:
http://bugs.mysql.com/bug.php?id=2446
[EMAIL PROTECTED] wrote:
Can you do a show create table Table1 and see how the index is defined?
Original Message
On 2/25/04,
I am assuming that the Memo field is a text datatype and you were
encountering the duplicate key bug.
Original Message
On 2/25/04, 3:28:58 PM, James Lamanna [EMAIL PROTECTED] wrote
regarding Re: Problem with indexes:
Found out that the problem was actually a bug in 4.0.17.
Upgrading
Yes.
[EMAIL PROTECTED] wrote:
I am assuming that the Memo field is a text datatype and you were
encountering the duplicate key bug.
Original Message
On 2/25/04, 3:28:58 PM, James Lamanna [EMAIL PROTECTED] wrote
regarding Re: Problem with indexes:
Found out that the problem was actually
