fenway

Try this: SELECT polls. * , poll_options. * FROM ( polls, poll_options ) LEFT JOIN poll_votes ON polls.poll_id = poll_votes.poll_id WHERE polls.poll_id =1 AND poll_options.poll_id = polls.poll_d You recently upgraded to v5, right?

I believe it's via className.

That has nothing to do with JS. Pick a set of quotes (single or doubles) and stick with it... keep escaping (you'll need to double-escape). Better yet, make some variables!

You can simply group by "crop" in your join.

This is just one of the changes that was "silently introduced" by v5... you may want to read the upgrade refman page.

Yeah, my bad, I should have said all variable-length fields.

Probably because there are other varchar columns....

I'd like to see the mysql error message. And it looks like you really need to normalize that table!

And ANALYZE too (since this deals with indexes directly)? Since you can recreate these data in another table with the same indexes (accordingly to your earlier post), it's hard to see what else is the issue here.

Have you ANALYZE / OPTIMIZE tables recently?

Like *all* client requests...

or an auto_increment_increment value set.

There are other reasons for using target other than "_blank".

I think IE has an "autocomplete" attribute, but I don't know well this is respected.

Change this: FROM tplss_matches M, tplss_matchtypes MT, tplss_opponents O LEFT OUTER JOIN tplss_previews P ON M.MatchID = P.PreviewMatchID "; To this: FROM ( tplss_matches M, tplss_matchtypes MT, tplss_opponents O ) LEFT OUTER JOIN tplss_previews P ON M.MatchID = P.PreviewMatchID ";

Don't mess up your IDs in the DB... format this on the way out with LPAD().

You can easily convert a SELECT statement into an update statement.

I just looked at the query.. and you're using a HUGE offset.

You can use GROUP BY on artist/title with a COUNT().

First, why? Second, you can use a multi-table update statement in v4.1+.

<input type="button" name="Submit" value="CLAIM YOUR KIT" on="return wrapperFunction(this.form)"> <script> fnction wrapperFunction( eForm ) { CancelChat(); return check(eForm,eForm.elements.length); } </script>

You don't have to use them... but they are known to work, and yours aren't. So I'd start with working code, get your script working, then rewrite them.

Also, from Diamond notes today:

You can self-join and see if the ranges overlap.

If you're really limited to 5-digit PIN (i.e 100K records), why not simply fill the entire table with 100K records and then auto-magically pick one? Better yet, have another table of *just* pins, generate the entire sequence, randomize the order (you can alter table order by rand()), and then assign a user_id to each record, and simply use "SELECT pin from pin_table WHERE user_id IS NOT NULL LIMIT 1"... voila!