Skip site navigation (1) Skip section navigation (2)

Re: "Current value" of sequences in the properties dialogue

From: Dave Page <dpage(at)postgresql(dot)org>
To: Erwin Brandstetter <brandstetter(at)falter(dot)at>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: "Current value" of sequences in the properties dialogue
Date: 2007-03-27 10:18:12
Message-ID: 4608EF64.20108@postgresql.org (view raw or flat)
Thread:
Lists: 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.


In response to

Responses

pgadmin-support by date

Next:From: ezequiasDate: 2007-03-27 12:17:11
Subject: Images
Previous:From: 权宗亮Date: 2007-03-27 09:44:00
Subject: Re: about ssleay32.lib

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group