| From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
|---|---|
| To: | |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | [pgAdmin III] #338: ALTER statements for sequences act like tables |
| Date: | 2011-09-10 15:54:42 |
| Message-ID: | 045.d219fc371eaa80db4ca7e52a811d1e72@code.pgadmin.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgAdmin Trac | 2011-09-10 16:04:22 | Re: [pgAdmin III] #338: ALTER statements for sequences act like tables |
| Previous Message | Guillaume Lelarge | 2011-09-10 15:37:24 | pgAdmin III commit: Fix dropping a constraint in the table properties |