dpage@postgresql.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?
Congratulations on the newly released v 1.6.3, btw! Seems to be the best
pgAdmin I have seen so far. :)
Regards
Erwin