Re: Plpgsql - Custom fields Postgres 9.5

From: rob stone <floriparob(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Patrick B <patrickbakerbr(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Plpgsql - Custom fields Postgres 9.5
Date: 2016-12-15 00:12:46
Message-ID: 1481760766.5163.5.camel@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Wed, 2016-12-14 at 17:00 -0700, David G. Johnston wrote:
> On Wed, Dec 14, 2016 at 4:49 PM, Patrick B <patrickbakerbr(at)gmail(dot)com>
> wrote:
> > ERROR:  function logextract(integer, integer) does not exist
> > LINE 1: select logextract(20160901,20161001);
> >
>
> So change the constants you are passing into your function to text
> (i.e., surrounding them with single quotes) so it matches the new
> function signature.
>
> There exists an element of understanding the options you are being
> given and adapting if something basic like this is overlooked.
>
> David J.

1) Have you run a \df+ and made sure the function has been created
correctly?

2) In your first post there is a single apostrophe after the execute
instruction. Can't see the closing apostrophe but then my eyesight is
not the best.

3) I've always found it easier to TO_CHAR a date column when using it
for comparison purposes.

HTH.
Rob

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2016-12-15 01:00:29 Re: Plpgsql - Custom fields Postgres 9.5
Previous Message David G. Johnston 2016-12-15 00:00:23 Re: Plpgsql - Custom fields Postgres 9.5