From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Chris <dmagick(at)gmail(dot)com> |
Cc: | marcosborges(at)mbsi(dot)com(dot)br, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: SQL_CALC_FOUND_ROWS in POSTGRESQL / Some one can |
Date: | 2006-12-11 04:04:38 |
Message-ID: | 1165809878.19970.2.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, 2006-12-11 at 14:33 +1100, Chris wrote:
> Marcos Borges wrote:
> > 07/12/2006 04:31
> > *SQL_CALC_FOUND_ROWS in POSTGRESQL*
> >
> > In mysqln i m using the command SQL_CALC_FOUND_ROWS in follow sintax.
> > SELECT SQL_CALC_FOUND_ROWS name, email, tel FROM mytable WHERE name <>
> > '' LIMIT 0, 10
> > to have the recorset data.
> > and
> > SELECT FOUND_ROWS();
> > to have the total of registers found.
> >
> > I dont want to use the command count(*), because the performance will
> > fall down, depending of the quantyt of tables and "joins".
> >
> > The Data base postgresql have something similar ???
>
> Nope, you're out of luck sorry. That's a mysql-ism and I doubt postgres
> will ever include something similar.
Your language will have a similar binding. Something like pg_numrows.
Sincerely,
Joshua D. Drake
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Chris | 2006-12-11 04:36:12 | Re: SQL_CALC_FOUND_ROWS in POSTGRESQL / Some one can |
Previous Message | Tatsuo Ishii | 2006-12-11 03:37:03 | Re: New to PostgreSQL, performance considerations |