[pgAdmin III] #338: ALTER statements for sequences act like tables - Mailing list pgadmin-hackers

From pgAdmin Trac
Subject [pgAdmin III] #338: ALTER statements for sequences act like tables
Date
Msg-id 045.d219fc371eaa80db4ca7e52a811d1e72@code.pgadmin.org
Whole thread Raw
Responses Re: [pgAdmin III] #338: ALTER statements for sequences act like tables  ("pgAdmin Trac" <trac@code.pgadmin.org>)
Re: [pgAdmin III] #338: ALTER statements for sequences act like tables  ("pgAdmin Trac" <trac@code.pgadmin.org>)
Re: [pgAdmin III] #338: ALTER statements for sequences act like tables  ("pgAdmin Trac" <trac@code.pgadmin.org>)
List pgadmin-hackers
#338: ALTER statements for sequences act like tables
----------------------+-----------------------------------------------------
 Reporter:  thom      |       Owner:  dpage
     Type:  bug       |      Status:  new  
 Priority:  minor     |   Milestone:       
Component:  pgadmin   |     Version:  trunk
 Keywords:  sequence  |    Platform:       
----------------------+-----------------------------------------------------
 If editing an existing sequence via its properties, attempts to change its
 name or owner results in ALTER TABLE statements instead of ALTER SEQUENCE.
 Creating a sequence and setting the owner results in the same invalid SQL.
 Also the SQL pane for sequences also shows this behaviour for setting the
 owner.

 This was tested on 1.14.0 RC1.

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/338>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

pgadmin-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: pgAdmin III commit: Fix dropping a constraint in the table properties
Next
From: "pgAdmin Trac"
Date:
Subject: Re: [pgAdmin III] #338: ALTER statements for sequences act like tables