Re: "Current value" of sequences in the properties dialogue - Mailing list pgadmin-support

From Dave Page
Subject Re: "Current value" of sequences in the properties dialogue
Date
Msg-id 4608EF64.20108@postgresql.org
Whole thread Raw
In response to "Current value" of sequences in the properties dialogue  (Erwin Brandstetter <brandstetter@falter.at>)
Responses Re: "Current value" of sequences in the properties dialogue  (Erwin Brandstetter <brandstetter@falter.at>)
List pgadmin-support
Erwin Brandstetter wrote:
> Hi developers! Hi Dave!
> 

Hi Erwin,

> It might help to use
> |    setval|('my_seq', 111, TRUE);
> or just
> |    setval|('my_seq', 111);
> as this would set "is_called" to true and thus generate a more
> consistant behaviour. "is_called" could still be set to FALSE by users,
> though.

I've implemented that change as suggested. The existing code went out of
it's way to behave as it did (using setval|('my_seq', 111, FALSE); on <
7.4 in fact!) so it was obviously a conscious design choice, but it's
not one I can see any justification for!

Cheers, Dave.



pgadmin-support by date:

Previous
From: "权宗亮"
Date:
Subject: Re: about ssleay32.lib
Next
From:
Date:
Subject: Images