From: Ken Winter <ken@sunward.org>
To: PostgreSQL pg-sql list <pgsql-sql@postgresql.org>
Subject: Defaulting a column to 'now'
Date: Wed, 14 Dec 2005 13:10:50 -0500
Message-ID: <003501c600d9$b799a1c0$6603a8c0@kenxp> (raw)
How can a column's default be set to 'now', meaning 'now' as of when each
row is inserted?
For example, here's a snip of DDL:
create table personal_data (.
effective_date_and_time TIMESTAMP WITH TIME ZONE not null default 'now',.
The problem is, when PostgreSQL processes this DDL, it interprets the 'now'
as the timestamp when the table is created, so that the tables definition
reads as if the DDL were:
effective_date_and_time TIMESTAMP WITH TIME ZONE not null default '
2005-12-14 11:00:16.749616-06 ',
so all of the newly inserted rows get assigned effective_date_and_time = '
2005-12-14 11:00:16.749616-06 ', which in addition to being wrong leads to
uniqueness constraint violations.
~ TIA
~ Ken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ken@sunward.org
Subject: Re: Defaulting a column to 'now'
In-Reply-To: <003501c600d9$b799a1c0$6603a8c0@kenxp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox