perfect, less work again :)

DB Changes = The Hacks modifies the database schema (eg. adding new fields, tables, indexes, etc.)
It has nothing to do with queries it uses to do it's work (gather data to display or whatever).

Lies it spreads...LIES!

I've never understood this obsession with hacks and their SQL queries.

Merging 4 threads and moving the merged thread to a different forum using inline moderation, runs 102 queries - why would you care if a hack adds a query or 2 that take a fraction of a second to run?

But... that's just me :)

It's going to be ... me?

Oh... right. :)

The only time that could become a concern is with a badly scripted modification that runs excessive queries...

And since the days of 3.0 and especially 3.5 you don't need to execute as many queries thanks to improvements in functionality ;)

Chris

Oh I'm glad to hear this will be available while we're on 3.5. :)

Ι remember asking about queries when I didn't even know what a query was! I don't think that everyone that seems so concerned about them really knows how much they add and what a query actually means.
I think some people are obsessed with the number of queries for no reason.
Anyway, DB changes is not complete cause there are hacks that don't affect the database but only run queries to read from it. So a query field is needed since we have those does-it-run-queries maniacs :p :p

It's not necessarilly the number of queries, but the quality of the queries. One badly written or implemented query can be worse then 100 properly implemented queries.

And how do you define a badly written query? :confused: