Re: Tracking Down Error in Stored Procedure

From: "Aaron Bono" <postgresql(at)aranya(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "sql pgsql" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Tracking Down Error in Stored Procedure
Date: 2006-12-02 07:19:12
Message-ID: bf05e51c0612012319r79b9cfd5kea2c1d361dde611f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On 12/2/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Aaron Bono" <postgresql(at)aranya(dot)com> writes:
> > CONTEXT: PL/pgSQL function "update_web_site_hits_fn" line 200 at
> execute
> > statement
>
> > My question is this: What is line 200? Is it the 200th line after the
> > CREATE part of the stored procedure? Or is it the 200th line after the
> > BEGIN? Or maybe something else?
>
> It's the 200th line in the function body string. IIRC there is a
> special case to not count a leading newline in the body string,
> so that the counting goes like
>
> CREATE FUNCTION foo ...
> RETURNS ...
> AS $$
> DECLARE -- this is line 1
>
> or without exploiting the special case
>
> CREATE FUNCTION foo ...
> RETURNS ...
> AS $$DECLARE -- this is line 1
>
> regards, tom lane
>

I got it fixed. Thanks for the help!

--
==================================================================
Aaron Bono
Aranya Software Technologies, Inc.
http://www.aranya.com
http://codeelixir.com
==================================================================

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Ken Johanson 2006-12-02 07:41:37 Re: [HACKERS] Case Preservation disregarding case
Previous Message Tom Lane 2006-12-02 06:20:59 Re: Tracking Down Error in Stored Procedure