Erwin Brandstetter wrote:
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
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
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
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.
Wouldn'
Erwin Brandstetter wrote:
>
> [EMAIL PROTECTED] 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
[EMAIL PROTECTED] 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,
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
Hi developers! Hi Dave!
Testing pgAdmin III v1.6.3 rev: 5941, client Win XP, host: Debian Sarge,
PG 8.1.8.
I have noted a peculiarity with seuqences.
If I change the "Current value" in the properties dialogue of a sequence
to a new value (111 in my example) pgAdmin sends this SQL statement t
