fenway

Does your table have multiple columns for each question/answer?

Yeah, but that's in an SP.

The information must be here.

Sorry, I didn't forget, I'm just swamped.

Yeah, for optimizations afterwards.

Why not simply: SELECT SUM( CASE WHEN user_id = 1 THEN 1 ELSE WHEN friend_id = 1 ELSE 0 END ) as friendCount FROM partners WHERE user_uid = 1 or friend_id = 1

Que_Choice1 Que_Choice2 Que_Chocie3 Que_Choice4 That's repeated 4 times.

That's just not a great DB design -- not normalized at all.

Yeah, but the IDs are arbitrary, and if I insert something for the past or the future, the id is meaningless.

Great -- now tell us what it was.

But that's the most inefficient query you could possibly write.

Echo mysql_error().

Oh, same here -- I can't possibly do it any differently at this point.

Actually, INTO has always been optional -- regardless of syntax.

If you'll post your CREATE TABLE statments, and some sample data as INSERTs, then I can give you a working query.

There's always the PHP refman.

Well, since you're getting a real error, and not a dummy one, tell us what's actually going on.

Then check mysql_error() and see why.

Actually, with the word SET, it would actually work ... alternate syntax... though it's evil.

Making changes to HTML templates hiding in an DB is just hard for no reason. There are countless examples of using that quoting function on this forum.

What's col3.col4? That doesn't make any sense.

Yeah, don't use id for this kind of thing -- a timestamp is the only useful column in this case.

ALL PRIVILEGES is usually a bad idea -- public users don't need alter, drop, etc.

I didn't understand a word of that. Are you ever searching by anything other than d_id?

Where's the mysql question?