fenway

Allows a local table to "be" a remote table -- see here.

No need to double-post; I've merged these topics... That's because if you where to echo your query (which you didn't) you'd see field LIKE '%%' which matches everything. You'll have to build the where clause dynamically.

Yes, because you've left out the ON clauses for each JOIN... ON c.customer_id = a.artist_id ON i.album_id = a.album_id This is a double-post

Which replace/

You can't reuse IDs.

You need to escape() the string your passing to JS.

Yes, well, this is around the DST changeover date. I'm confused as to exactly what is happening now.

So when it saved the "wrong" times, it thought it was right?

Then you should use inner join for each step, assuming every link is always present. Drop the where clause, since it's not doing anything. And don't select * unless you actually need to.

why is the customer table in there at all? don't you just want songs/albums?

Linux will adjust this for you -- when you say one hour off, you mean dcorrectly adjusted for dst?

Check your server settings as far as time zones are concerned; check mysql, too.

I don't understand how you decided on that query.

Contact your host and have them give you root access.

This seems like an inherently bad idea, fighting for locks and such... besides, you can always use federated tables. And who told you to make a new db.

why the left join then the inner join? what do you mean "one row"?

Nope... only perl figures out what to do with barewords properly.

Can't believe I didn't see that... I thought my example had quotes.

Yes, you'll have to parse it out.... unless someone has already written a function to that do.

It sounds like you can't find the array indexes that you made... I'm saying you should put them into a hash.

You shouldn't keep them in an array -- the "uid" should be the key of the top hash. Once you've changed this, go through all of the keys in the mailSettings hash, make sure all your uids are there.

Move it to the HAVING clause... and that != won't engage the index.

You can't use aggregate functions in the WHERE clause.

What won't be?

I assume you're setting it / reading it... just convert 255 <-> FF. It's a simple hex-to-decimal function.