Re: Odd behavior with 'currval'

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Steven Hirsch <snhirsch(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Odd behavior with 'currval'
Date: 2018-02-09 15:27:55
Message-ID: CA+bJJbwenw_9TErFhuNxUz4T-FdVkPgTFOwL=pmFR+eegAnfWg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Feb 8, 2018 at 8:12 PM, Steven Hirsch <snhirsch(at)gmail(dot)com> wrote:
.....

> 2. Why is the currval() function being so blasted dumb? If
> 'pg_get_serial_sequence' cannot resolve the sequence, it returns NULL. As
> such, shouldn't the outer currval() also be returning NULL? I cannot
> imagine a rationale for the current behavior.

Are you sure it does ? http://sqlfiddle.com/#!17/9eecb/9696 shows it
returning null. ( as expected, if it is defined strict as it should
and someone has already pointed it ).

Are you sure you are not using pgAdmin or a similar thing which
displays null as 0 in a numeric field?

Francisco Olarte.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2018-02-09 15:45:16 Re: Odd behavior with 'currval'
Previous Message Thomas Kellerer 2018-02-09 07:23:32 Re: DOW is 0-based?