Skip site navigation (1) Skip section navigation (2)

Re: Can't edit tables with timestamps

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: 'Thomas Sandford' <thomas(at)paradisegreen(dot)co(dot)uk>,pgadmin-support(at)postgresql(dot)org
Subject: Re: Can't edit tables with timestamps
Date: 2002-03-27 21:56:45
Message-ID: FED2B709E3270E4B903EB0175A49BCB129331D@dogbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Thomas Sandford [mailto:thomas(at)paradisegreen(dot)co(dot)uk] 
> Sent: 27 March 2002 20:32
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] Can't edit tables with timestamps
> 
> 
> Given a database created from the following SQL:
> 
> CREATE TABLE "testtable" (
>         "id" integer NOT NULL,
>         "mytext" character varying(32),
>         "mytime" timestamp with time zone,
>         Constraint "testtable_pkey" Primary Key ("id")
> );
> 
> 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.

Regards, Dave.

Responses

pgadmin-support by date

Next:From: Marc CuypersDate: 2002-03-28 06:57:00
Subject: Migrating from MS-Access to Postgresql
Previous:From: Revista Melhor Vida & TrabalhoDate: 2002-03-27 21:40:26
Subject:

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group