fenway

This topic has been moved to Application Design. http://www.phpfreaks.com/forums/index.php?topic=307893.0

ORDER BY is optimized with LIMIT.

Please post actual queries.

Have you confirmed your math and logic is sound?

Not even remotely true -- that's VARCHAR you're talking about, as of mysql 5_.

Define "not correctly".

what do you mean, can you elaborate? No need for a PM. I meant just a generic EAV table.

Did you try?

Not to me, sorry -- maybe to someone else.

Always echo the actual query.

Well, if you're happy placing some reasonable restrictions, then it's easy -- thought not efficient. Just define a table with a slew of different data types, and then store the heading elsewhere.

Sorry, why can't you store these data as-is?

Say what?

Why not just add another where condition to your query?

I suppose you can do this inline with a subquery

Since there's no update command, when you "removes", I assume you mean your php code -- in which case, you're in the wrong board.

Let's see the new create command.

And in general, never use BIGINT.

If you're in double-quotes, maybe you're getting interpolation of some sort.

Then you have a php error.

The more you separate the tables, the more flexible your design.

No reason you can't do this math in mysql -- but don't necessarily store it -- and you'll need to use the result of aggregate functions in a HAVING.

Let's see the EXPLAIN output -- see my sig.

Then blame the query, not the table.

Sorry, I don't follow -- if you have SQL statements, just issue them one a at a time.