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-28 07:44:35 |
Message-ID: | 460A1CE3.5020401@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Erwin Brandstetter wrote:
>
> dpage(at)postgresql(dot)org wrote:
> (...)
>> 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.
>
> Nice!
> Additionally displaying the sequence's is_called flag in the properties
> is not an easy option, I assume?
It's not a problem, it's just one of those things that inevitably leads
to confusion amongst some users.
> Congratulations on the newly released v 1.6.3, btw! Seems to be the best
> pgAdmin I have seen so far. :)
Thanks - thats usually the case with the back branches as we iron out
all the bugs. We'll have a new release soon, with a whole new set of
bugs for you to find :-p
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2007-03-28 12:23:21 | rh 4 install? |
Previous Message | Erwin Brandstetter | 2007-03-28 00:34:44 | Re: "Current value" of sequences in the properties dialogue |