List:General Discussion« Previous MessageNext Message »
From:Martin Ramsch Date:August 18 1999 11:13pm
Subject:Re: eq_ref optimization -- please help
View as plain text  
On Wed, 1999-08-18 15:56:01 -0700, jeremy brand wrote:
> we are migrating some of our tables to a new machine for
> developement of a new system.
> 
> here is the problem..
> 
> two identical querys are behaving differently..
[...]
> ----- developement server -- this is the problemed server... ---
> 
> Database: carecards  Table: carddata  Rows: 1292
[...]
> | artistID    | char(5)      |      | MUL |         |                |
[...]

> Database: carecards  Table: artistdata  Rows: 132
[...]
> | artistID  | int(9) unsigned |      | PRI | 0       | auto_increment |
[...]

> this is the query:
> select [...] where [...] carddata.artistID = artistdata.artistID [...]

Just guessing, but the field types of artistID don't match, and as far
as I know this makes use of indexes impossible (at least in the older
versions of MySQL).

So maybe changing carddata.artistID into int(9) unsigned might help?

Regards,
  Martin
-- 
Martin Ramsch <m.ramsch@stripped> <URL: http://home.pages.de/~ramsch/ >
PGP KeyID=0xE8EF4F75 FiPr=52 44 5E F3 B0 B1 38 26  E4 EC 80 58 7B 31 3A D7
Thread
eq_ref optimization -- please helpjeremy brand19 Aug
  • Re: eq_ref optimization -- please helpMartin Ramsch19 Aug
    • Re: eq_ref optimization -- please helpjeremy brand19 Aug
      • Re: eq_ref optimization -- please helpBenjamin Pflugmann20 Aug
        • Re: eq_ref optimization -- please helpjeremy brand20 Aug
          • Re: eq_ref optimization -- please helpBenjamin Pflugmann20 Aug
            • Re: eq_ref optimization -- please helpjeremy brand20 Aug
              • Re: eq_ref optimization -- please helpPaul DuBois20 Aug
                • Re: eq_ref optimization -- please helpjeremy brand20 Aug