> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 21 October 2004 15:26
> To: Dave Page
> Cc: PgAdmin Hackers
> Subject: Re: [pgadmin-hackers] Sequence bug
>
> Dave Page wrote:
> >
> > Hmm, it's not though is i
Dave Page wrote:
Hmm, it's not though is it, because (assuming a basic new sequence with
no odd values set), start = 1, min = 1, max = whatever. PostgreSQL will
error if you try to set it to zero. The closest thing to zero is to set
it to 1 and unset is_called.
I would say the least confusing be
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 21 October 2004 14:54
> To: Dave Page
> Cc: PgAdmin Hackers
> Subject: Re: [pgadmin-hackers] Sequence bug
>
> Dave Page wrote:
>
> >
> > Hmm, it works OK (thanks
Dave Page wrote:
Hmm, it works OK (thanks), but not as you would expect. With setval's
third arg = false, you can set the sequence value to 1, which is
displayed as expected as the 'Current Value', but then a 'SELECT
nextval()' also returns 1 which is not what you would expect (especially
if you ar
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 21 October 2004 14:28
> To: Dave Page
> Cc: PgAdmin Hackers
> Subject: Re: [pgadmin-hackers] Sequence bug
>
> Dave Page wrote:
> > Hi guys,
> >
> > Sorry, but I
Dave Page wrote:
Hi guys,
Sorry, but I don't have any time to look at this right now... I found a
quoting bug in the sequence dialogue that prevents modification of them
(such as resetting the value) - should be trivial to sort. I also
suspect that resetting to zero won't work correctly because we
Hi guys,
Sorry, but I don't have any time to look at this right now... I found a
quoting bug in the sequence dialogue that prevents modification of them
(such as resetting the value) - should be trivial to sort. I also
suspect that resetting to zero won't work correctly because we need to
use some
