Re: Error editing table WITH primary key

My problem is solved.

It was solved itself. All tables, insert data and primary key's creation
was launched from a SQL script. Perhaps the primary key had been creating
by PostgreSQL in the background and then pgAdmin could not access that data
tables for editing ??

I don't know what was the real reason but it was solved among an hour or so.

Solved then...

Greetings...

2009/1/17 Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] <
Susan(dot)M(dot)Thornton(at)nasa(dot)gov>

> Sorry - my bad. Here is the postgresql definition of a PRIMARY-KEY:
>
> The PRIMARY KEY column constraint specifies that a column of a table may
> contain only unique (non-duplicate), non-NULL values. The definition of
> the specified column does not have to include an explicit NOT NULL
> constraint to be included in a PRIMARY KEY constraint.
>
> Sue
>
> -----Original Message-----
> From: Raymond O'Donnell [mailto:rod(at)iol(dot)ie]
> Sent: Friday, January 16, 2009 4:17 PM
> To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS]
> Cc: Terry Yapt; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Error editing table WITH primary key
>
> On 16/01/2009 18:56, Thornton, Susan M. (LARC-B702)[NCI INFORMATION
> SYSTEMS] wrote:
> > Is your primary key defined as "Unique"? If this is the case,
> you
> > may be trying to add a value for the key that already exists. Or it
> may
>
> Is a primary key not unique by definition? - doesn't the primary key
> uniquely identify a row in a table?
>
> Ray.
>
>
> ------------------------------------------------------------------
> Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
> rod(at)iol(dot)ie
> Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals
> ------------------------------------------------------------------
>

--
Terry Yapt