Received: from megazone.bigpanda.com ([63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAU9TQm74228 for ; Fri, 30 Nov 2001 04:29:26 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 3209DD5F1; Fri, 30 Nov 2001 01:29:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 23B0E5BED; Fri, 30 Nov 2001 01:29:27 -0800 (PST) Date: Fri, 30 Nov 2001 01:29:27 -0800 (PST) From: Stephan Szabo To: Tom Lane Cc: =?us-ascii?Q?=22Johnny_J=F8rgensen=22?= , Subject: Re: PL/pgSQL loops? In-Reply-To: <3774.1007075585@sss.pgh.pa.us> Message-ID: <20011130012817.T52306-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200111/433 X-Sequence-Number: 5815 On Thu, 29 Nov 2001, Tom Lane wrote: > I said: > > I would've expected it to count nested parentheses, at least. > > Okay, it does that now, and I found that I could tighten the error > checking to give a sooner/more useful error. Now, if you get caught > by the integer-FOR-vs-FOR-over-rows problem, you'll probably get > > ERROR: missing .. at end of SQL expression > > which at least gives you some clue that the problem has something to > do with the "FOR x IN foo .. bar" syntax. Definately better, and it probably gives a more meaningful line number too.