Re: Feature request - Edit data and tables without a primary key

From: Thom Brown <thom(at)linux(dot)com>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de>, pgadmin-support(at)postgresql(dot)org
Subject: Re: Feature request - Edit data and tables without a primary key
Date: 2012-07-14 13:01:45
Message-ID: CAA-aLv7gHLGAU4A7Hd6=R0sPkG1+6unBqdmZGWBP-1=7m7xSKA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On 14 July 2012 13:57, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
> On Thu, 2012-07-12 at 12:31 +0100, Thom Brown wrote:
>> Use of the CTID system column would work.
>
> I don't see how that could work. CTIDs obviously are unique, but anyone,
> updating a line will get another CTID for this line. If you try to
> update it afterwards, in the best case, it errors out because there is
> no line at this CTID. In the worst case, you update a completely
> different line.

Why can't you just use "RETURNING ctid" at the end of the statement to
get the new one and update the grid with that value?
--
Thom

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Guillaume Lelarge 2012-07-14 13:02:13 Re: pgScript error when relation name contains ")" symbol
Previous Message Guillaume Lelarge 2012-07-14 12:59:21 Re: Launching Application on Desktop in RHEL 6.1 pgsql 8.4