Обсуждение: aparent bug with pgAdmin version 1.22.1 connected to pg 9.5: SQL Pane view of SEQUENCE object

A sequence object was created successfully when I created a table with a co=
lumn of type SEQUENCE.  However, in the SQL pane, I see the below code, whi=
ch has an ALTER TABLE statement for the assignment of ownership.  The seque=
nce object can be recreated (manually) only if I edit this statement to bec=
ome ALTER SEQUENCE, so I'm convinced that this is a defect somewhere.

-- Sequence: public.patient_patient_dbid_seq

-- DROP SEQUENCE public.patient_patient_dbid_seq;

CREATE SEQUENCE public.patient_patient_dbid_seq
  INCREMENT 1
  MINVALUE 1
  MAXVALUE 9223372036854775807
  START 1
  CACHE 1;
ALTER TABLE public.patient_patient_dbid_seq
  OWNER TO wohcdrowner;


******************************************************************
This communication is intended solely for the addressee and is confidential=
. If you
are not the intended recipient, any disclosure, copying, distribution or an=
y action taken
or omitted to be taken in reliance on it, is prohibited and may be unlawful=
. Unless
indicated to the contrary: it does not constitute professional advice or op=
inions upon
which reliance may be made by the addressee or any other party, and it shou=
ld be
considered to be a work in progress.
******************************************************************

On Tue, Feb 16, 2016 at 03:13:59PM +0000, Tom Puckett wrote:
> A sequence object was created successfully when I created a table with a column
> of type SEQUENCE.  However, in the SQL pane, I see the below code, which has an
> ALTER TABLE statement for the assignment of ownership.  The sequence object can
> be recreated (manually) only if I edit this statement to become ALTER SEQUENCE,
> so I’m convinced that this is a defect somewhere.

The alter_table manual page says:

    OWNER           This form changes the owner of the table, sequence, view,
                                                              ^^^^^^^^
    materialized view, or foreign table to the specified user.

so it does work.  You are right that ALTER SEQUENCE would be clearer,
though.

---------------------------------------------------------------------------


>
>
>
> -- Sequence: public.patient_patient_dbid_seq
>
>
>
> -- DROP SEQUENCE public.patient_patient_dbid_seq;
>
>
>
> CREATE SEQUENCE public.patient_patient_dbid_seq
>
>   INCREMENT 1
>
>   MINVALUE 1
>
>   MAXVALUE 9223372036854775807
>
>   START 1
>
>   CACHE 1;
>
> ALTER TABLE public.patient_patient_dbid_seq
>
>   OWNER TO wohcdrowner;
>
>
>
> ******************************************************************
> This communication is intended solely for the addressee and is confidential. If
> you
> are not the intended recipient, any disclosure, copying, distribution or any
> action taken
> or omitted to be taken in reliance on it, is prohibited and may be unlawful.
> Unless
> indicated to the contrary: it does not constitute professional advice or
> opinions upon
> which reliance may be made by the addressee or any other party, and it should
> be
> considered to be a work in progress.
> ******************************************************************
>

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription                             +

Tom Puckett wrote:
> A sequence object was created successfully when I created a table with a column of type SEQUENCE.  However, in the
SQLpane, I see the below code, which has an ALTER TABLE statement for the assignment of ownership.  The sequence object
canbe recreated (manually) only if I edit this statement to become ALTER SEQUENCE, so I'm convinced that this is a
defectsomewhere. 
>
> -- Sequence: public.patient_patient_dbid_seq
>
> -- DROP SEQUENCE public.patient_patient_dbid_seq;
>
> CREATE SEQUENCE public.patient_patient_dbid_seq
>   INCREMENT 1
>   MINVALUE 1
>   MAXVALUE 9223372036854775807
>   START 1
>   CACHE 1;
> ALTER TABLE public.patient_patient_dbid_seq
>   OWNER TO wohcdrowner;

This exact series of commands works fine.  Are you sure the command you
had to modify wasn't the OWNED BY one, rather than OWNER TO?

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services