fenway

Then you need a new version of the mysql libraries.

Yup... then just skip the first record.

What you return in your column list has nothing to do with how to mysql finds the matching records -- you need an ON clause.

Well, you need to establish what the rate-limiting step is -- are the mysql queries optimized? check EXPLAIN.

Well, debug the result set from your query directly -- otherwise, it's a php logic error.

I think you're mixing ORs and ANDs without parentheses...

Why not? There are ugly sql ways of doing this, but you'd need to tell us more about every possible variation in your dataset.

FTS acts funny on smaller datasts... how big is your table?

What you have seems correct... does it not work?

As soon as mysql needs to create a temporary table -- like when you mention this column in a GROUP BY / ORDER BY clause -- then mysql will allocate the MAX length of this column.

Well, you said 150 records, and I see limit 1?

"Configured Max Per-thread Buffers" -- how is that being calculated? usually that's the worst-case scenario, so it's likely to be true.

If there's a timeout on the server side, you have to run your script in smaller steps.

This is all determined in your my.cnf file.

Not easily.

Yes-- except the comma operator is EVIL and should never, EVER be used.

When, you can UNION those 3 bad record tables... and JOIN to $5 -- but I'm not sure if you can sql-ify #1.

So --lock-tables is appropriate -- or all-tables, depending on what you're doing.

I see blank field values... is that intentional?

Just store a timestamp associated with each download.

Until you use this column for group by / order by operations.

The closer the value is to the maximum expected value, the better... but depending on your sql mode, you may get truncated data if you go over.

Show us the table structure.

What do you mean??

Always.