From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #358: Allow to set option is_called for setval Date: Tue, 27 Mar 2012 08:58:32 +0200 |
Date: | 2012-03-29 19:43:41 |
Message-ID: | 056.d6cf8dce8d8f736daeb07b93d4b3686e@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#358: Allow to set option is_called for setval Date: Tue, 27 Mar 2012 08:58:32
+0200
-----------------------------+----------------------------------------------
Reporter: Bartosz Dmytrak | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
Keywords: sequence | Platform: all
-----------------------------+----------------------------------------------
I just noticed pgAdmin cannot set value of sequence to start with 1
because generates SQL like this:
SELECT setval('"MySchema"."MySequence"', 1, true);
it is not possible to set "is_called" option of setval to false.
According to doc (http://www.postgresql.org/docs/9.1/static/functions-
sequence.html):
* "If it is set to false, the next nextval will return exactly the
specified value, and sequence advancement commences with the following
nextval"*
so, please add checkbox in sequence properties to allow to modify this
switch.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/358>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2012-03-29 19:43:54 | Re: [pgAdmin III] #358: Allow to set option is_called for setval (was: Allow to set option is_called for setval Date: Tue, 27 Mar 2012 08:58:32 +0200) |
Previous Message | Guillaume Lelarge | 2012-03-29 19:39:09 | Re: pgAdmin 1.15 experiences |