Re: Verifying a timestamp is null or in the past

From: David Johnston <polobo(at)yahoo(dot)com>
To: Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Verifying a timestamp is null or in the past
Date: 2012-01-02 22:02:36
Message-ID: 4FDF1D7F-9DE8-4D2F-A191-B0C0499CE82B@yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Jan 2, 2012, at 16:46, Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com> wrote:

> Hi,
>
> On 2 January 2012 03:26, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:
>>> And also - does PERFORM works with FOUND?
>>
>> Not sure what you mean - can you elaborate?
>
> No, perform (and execute) doesn't populate 'found' variable:
> http://www.postgresql.org/docs/9.0/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-DIAGNOSTICS
>
> You have to use something like this:
> get diagnostics rr = row_count;
>
>
> --
> Ondrej Ivanic
> (ondrej(dot)ivanic(at)gmail(dot)com)
>
>

Yes, PERFORM does populate FOUND.

From the documentation you just linked to....

A PERFORM statement sets FOUND true if it produces (and discards) one or more rows, false if no row is produced.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Hannes Erven 2012-01-02 22:06:29 Re: Adding German Character Set to PostgresSQL
Previous Message Adrian Klaver 2012-01-02 21:58:59 Re: Adding German Character Set to PostgresSQL