Postgres Pro
Downloads
Home   >   mailing lists

Thread: Is earlier error "Could not locate the record for deletion" fixed?

Is earlier error "Could not locate the record for deletion" fixed?

From
Knut Nymoen
Date:
Hi,

I hope you can help me a bit here.

I just discovered a problem with deleting records from a table using
pgAdmin II,
where I got the message "Could not locate the record for deletion in the
database"
I am using version 1.2.0 of pgAdmin btw and postgresql 7.1

However, I found a post from Dave at
   http://archives.postgresql.org/pgadmin-support/2001-11/msg00005.php
where he say that he is  working on this bug.

Do you know if this bug is fixed?

Thanks!

/Knut Nymoen
nymoen@systek.no
Systek AS, Billingstad, Norway




The table definition:
-- Table: productorder
CREATE TABLE "productorder" (
  "address" text,
  "productorderid" int8,
  "date" timestamp,
  "paytype" int4,
  "productid" int8,
  "number" int4,
  "state" int4,
  "customerid" int8
);

The log from postgresql:

SELECT count(*) AS count FROM "productorder" WHERE "address" = 'CATARINA
BERG. HEEN GÅRD, 1880 EIDSBERG' AND "productorderid" = '12399' AND
"date" = '2002-02-25 21:29:29' AND "paytype" = '2' AND "productid" =
'10007' AND "number" = '1' AND "state" = '2' AND "customerid" = '12232'

Re: Is earlier error "Could not locate the record for deletion" fixed?

From
"Dave Page"
Date:

> -----Original Message-----
> From: Knut Nymoen [mailto:nymoen@systek.no]
> Sent: 04 June 2002 20:06
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Is earlier error "Could not locate
> the record for deletion" fixed?
>
>
> Hi,
>
> I hope you can help me a bit here.
>
> I just discovered a problem with deleting records from a
> table using pgAdmin II, where I got the message "Could not
> locate the record for deletion in the database" I am using
> version 1.2.0 of pgAdmin btw and postgresql 7.1
>
> However, I found a post from Dave at
>    http://archives.postgresql.org/pgadmin-support/2001-11/msg00005.php
> where he say that he is  working on this bug.
>
> Do you know if this bug is fixed?

Yes and no. It's one of those non-exact one that will probably keep
cropping up. Currently though, I think we do a better job than
Microsoft's ADO does :-).

Anyway, the bugs mentioned in that post were fixed before v1.2.0. I have
done more work in the current development code that improves things even
more by using a primary key if one is available. You can download the
dev code from http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/binaries/ -
download the tarball & then follow the instructions in the readme.

Regards, Dave.