delete a row that is created by django using PHPPgAdmin?

Question

Using django, I added a new entry to my table. Now I want to delete it using PHPPgAdmin (postgresql), but I get No unique Identifier for this row error. What is the problem?

django automatically adds an auto-incrementing primary key, so I cannot figure out what the issue is?

I read this post, but it did not help. If you notice the image carefully, you will see that the primary key column label is id but not pk as it should be in django.

enter image description here

EDIT: No primary key is seen on table; enter image description here

But this is what django executes;

python manage.py sql auth

CREATE TABLE "auth_user" (
    "id" serial NOT NULL PRIMARY KEY,
    "password" varchar(128) NOT NULL,
    "last_login" timestamp with time zone NOT NULL,
    "is_superuser" boolean NOT NULL,
    "username" varchar(30) NOT NULL UNIQUE,
    "first_name" varchar(30) NOT NULL,
    "last_name" varchar(30) NOT NULL,
    "email" varchar(75) NOT NULL,
    "is_staff" boolean NOT NULL,
    "is_active" boolean NOT NULL,
    "date_joined" timestamp with time zone NOT NULL
)
;

EDIT: A screenshot from PHPPgAdmin, showing id as primary key enter image description here

I assume by the screenshot that you mean PHPPgAdmin. If you use `psql` to run `\d thetablename` what's the output? Does it show a `PRIMARY KEY` ? — Craig Ringer, Mar 25 '14 at 01:17
The `PRIMARY KEY` is listed after the table columns; check there. — Craig Ringer, Mar 25 '14 at 02:25
Screenshot not updated to reflect that, but if that's the case, sounds like the problem must be PHPPgAdmin. I've never used it myself, I just use `psql`, so I'm not sure what to advise from here. — Craig Ringer, Mar 25 '14 at 03:26
Is the "no unique identifier for this row" a Django error, or from PhpPgAdmin? — Craig Ringer, Mar 25 '14 at 03:43
In django `pk` is an alias that always points to the primary key, irrespective if its called `id` or anything else; which is why it is recommended to be used. What is the exact query you are running? — Burhan Khalid, Mar 25 '14 at 04:20
@CraigRinger: the error comes in pgAdmin3. The very first snapshot above. — eagertoLearn, Mar 25 '14 at 04:26
@eagertoLearn That doesn't look like PgAdmin-III's UI to me, it looks like something from a web browser. — Craig Ringer, Mar 25 '14 at 04:27
@BurhanKhalid: when I try to delete a row, from pgAdmin3, it is not allowing me to delete. the snapshots show them. — eagertoLearn, Mar 25 '14 at 04:27
Can you delete the row from psql? If so, this might be a bug in phppgadmin (and please do not confuse it with the actual [pgadmin](http://www.pgadmin.org/)). — Burhan Khalid, Mar 25 '14 at 04:32

score 0 · Answer 1 · answered Oct 28 '15 at 11:30

I think this is a bug with phpPgAdmin.

I experienced a similar problem and went directly into psql (using the command ./manage.py dbshell).

I tried deleting the row in question, and received a more helpful error message than the one from phpPgAdmin. (In my case, that the row was being referenced by another table.)

I deleted the row referenced by the other table, and was then able to delete the row in question.

delete a row that is created by django using PHPPgAdmin?

1 Answers1