On 14 May, 15:36, "Schemer" <nowh...@man.com> wrote:
> "Captain Paralytic" <paul_laut...@yahoo.com> wrote in message
>
> news:5276825c-e6ea-4fc1-b76a-5621584d344c@c58g2000hsc.googlegroups.com...
>
>
>
> > On 14 May, 15:04, "Schemer" <nowh...@man.com> wrote:
> >> >> A query that worked yesterday (against the mySQL db behind my web
> >> >> site)
> >> >> fails today with this error:
> >> >> "Can\'t use players: The SELECT would examine more than MAX_JOIN_SIZE
> >> >> rows;
> >> >> check your WHERE and use SET SQL_BIG_SELECTS=1 or SET
> >> >> SQL_MAX_JOIN_SIZE=#
> >> >> if
> >> >> the SELECT is okay"
>
> >> >> How can I fix this? What would be the best way to simplify this
> >> >> query?
> >> >> Thanks for any suggestions.
> >> > Errm, why are you asking us when you just posted the answer?
>
> >> Since I have little experience with SQL, I was hoping I could get some
> >> pointers on how I might be able to break down this query in a way that is
> >> useable in the php of a web page.
>
> > Well, whilst I agree that the query is rather ghastly (it should be
> > written as explicit JOINS, instead of multiple sub selects and it also
> > looks as though the underlying table structure could do with
> > changing), I don't see what stops it already being used in a php
> > script?
>
> Unfortunately, I have no control over the table structure.
> When this query is used, the error quoted in the original message is thrown.
You have already posted how to overcome the "error". The message tells
you that.