Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
User-Agent: Microsoft-Entourage/11.2.3.060209
Date: Fri, 31 Mar 2006 10:34:58 -0500
Subject: Re: Database transaction across multiple web requests
From: Sean Davis <sdavis2@mail.nih.gov>
To: Frank Wiles <frank@wiles.org>,
	Issac Goldstand <margol@beamartyr.net>
CC: <tomAtLinux@gmx.at>,
	<tomas@tuxteam.de>,
	"modperl@perl.apache.org" <modperl@perl.apache.org>
Message-ID: <C052B652.93B1%sdavis2@mail.nih.gov>
Thread-Topic: Database transaction across multiple web requests
Thread-Index: AcZU2Kqw6UWCwsDLEdqrmAANkzVl6A==
In-Reply-To: <20060331090126.b44ff3d0.frank@wiles.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit


On 3/31/06 10:01 AM, "Frank Wiles" <frank@wiles.org> wrote:

> On Fri, 31 Mar 2006 14:47:37 +0200
> Issac Goldstand <margol@beamartyr.net> wrote:
> 
>> Granted, I use a few MySQL features for this; I'm not sure if LIMIT
>> exists in postgresql, and I'm fairly sure that the SQL_CALC_FOUND_ROWS
>> directive (which will return the total rows in a select statement
>> regardless of the LIMIT directives) doesn't...
> 
>   PostgreSQL has LIMIT... it's a SQL standard.  And I don't really see
>   why you would need SQL_CALC_FOUND_ROWS unless you where going to
>   show the total number of pages.  For simple Next/Previous paging
>   you just keep going until you fall off the end.
> 
>   If you need to get a count you can just do a count() on a particular
>   column without the LIMIT and get a total.

In postgres, a count(*) can be fairly time-consuming, so a quick-and-dirty
hack is to parse the output of the "EXPLAIN ..." query to get the estimated
number of rows, which is often just fine as an estimate.  If the database is
vacuumed often or is basically query-only, these numbers will often be very
close or the same as the real thing.

Sean