Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0MFqhl83176 for ; Tue, 22 Jan 2002 10:52:43 -0500 (EST) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 673007; Tue, 22 Jan 2002 07:52:45 -0800 From: "Josh Berkus" Subject: Re: Long running queries and timeouts To: Francisco Reyes Cc: pgsql-php@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Tue, 22 Jan 2002 07:52:45 -0800 Message-ID: In-Reply-To: <20020121213523.I40885-100000@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200201/44 X-Sequence-Number: 850 Francisco, > > If queries > 2 min are common, you'll need some kind of "progress > bar" > > mechanism that updates the page every 40 seconds to prevent the > > browser from timing out. > > -Josh > > Do you have any experience on this? Sample code? > Is that a term you think I may search for on the web "progress bar"? Actually, my web developer and I talked about the programming necessary to do this, and decided that it was easier to break up the long-running function into 3 smaller functions. So, no, we don't have any sample code. In fact, we might be willing to buy some code that creates a progress bar from someone who does have it ... -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco