> -----Original Message-----
> From: Thomas Sandford [mailto:thomas@paradisegreen.co.uk]
> Sent: 28 March 2002 11:33
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] Can't edit tables with timestamps
>
>
> "Dave Page" <dpage@vale-housing.co.uk> wrote:
> > Thomas Sandford [mailto:thomas@paradisegreen.co.uk] wrote:
> > > [... database table using timestamp field ...]
> > > COPY "testtable" FROM stdin;
> > > 1 \N 2002-03-27 20:15:52.000000+00
> > > 2 \N 2002-03-27 20:16:05.187532+00
> > > \.
> > >
> > > You will find that whilst the 1st record can be edited using
> > > pgadmin, any attempt to edit the 2nd results in the
> message "Could
> > > not locate the record for updating in the database!"
> >
> > Yes, this is a bizarre 'feature' that's been bugging me on
> and off for
> years
> > now. Currently, pgAdmin builds an update query by generating a WHERE
> clause
> > using all available data. Unfortunately it periodically fails when
> > there
> are
> > timestamps involved. I'll put it back on my to-do list.
>
> Thought (which may have occured to you and/or be impractical,
> but I'll mention it anyway) - if the table contains a primary
> key (as in this case) could you build the update where clause
> from that alone? Would fix at least some (and quite likely
> most) instances of this type of problem.
That should fix *all* problems such as this. In fact, all we need is a
Unique column. The problem is that the ISUNIQUE property of each field
object in the recordset is null at the moment. I'll look into it some more.
Regards, Dave.