Jeremy Zawodny wrote:
SELECT COUNT(*) FROM foo WHERE ...
How can I get this to work with a GROUP BY?
Can you post the query along with the output of EXPLAIN query so we
can get a good idea what's going on?
Query:
SELECT
documents.document_id
FROM
documents,
dictionary AS
neeraj arora wrote:
Hi,
I think indexing the column(s) can help you.
Already spent a week figuring how to get the SELECT to work fast when a few
results are returned, os all appropriate columns are indexed ;-)
u can find more on this page
On Thu, Dec 06, 2001 at 09:28:10AM +, Chris Withers wrote:
neeraj arora wrote:
Already spent a week figuring how to get the SELECT to work fast when a few
results are returned, os all appropriate columns are indexed ;-)
u can find more on this page
Jeremy Zawodny wrote:
SQL_BUFFER_RESULT (http://www.mysql.com/doc/S/E/SELECT.html) my help,
depending on what the real bottleneck is.
H... I thought temporary tables were bad?
Sure, change your
SELECT * FROM foo WHERE ...
to
SELECT COUNT(*) FROM foo WHERE ...
to get the
:Now, is there any way I can quickly return the length of the
:result set withotu
:actually returning the result set itself?
:
:
:Chris
:
:(MySQL question, obviously ;-)
Dunno if this was answered cause I'm on digest but,
Try SELECT Count(*) from...
erik
st.m
Hi,
If I have a SELECT that returns a large number of results, say 1000, then
returns the results for the SELECT takes much over an order of magnitude longer
than if the results set had been, say, 100.
Now, is there any way I can quickly return the length of the result set withotu
actually
Hi,
I think indexing the column(s) can help you. But there are certain
criteria before you use indexs (like number of duplicate values in the
column ..blah blah..)
u can find more on this page
http://www.linux-mag.com/cgi-bin/printer.pl?issue=2001-06article=mysql
i hope this will help you.
