Search Postgresql Archives

Re: CURRENT_TIMESTAMP wierd behaviour

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2006-08-10 at 09:37, Andy Foster wrote:
> Hi all 
> 
> I have created the following simple table
> 
> create table NTE_NOTES (
> 	nte_id int unique not null,
> 	nte_text text not null,
> 	nte_last_updated timestamp not null,
> 	constraint nte_pk primary key (nte_id));
> 
> If I execute the following sql as a single transaction in the admin
> interface or using JDBC it appears that the CURRENT_TIMESTAMP has the same
> value for all records including the updated one. Why?

Read here:

http://www.postgresql.org/docs/8.1/interactive/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux