Re: #PERSONAL# Reg: date going as 01/01/0001

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: Medhavi Mahansaria <medhavi(dot)mahansaria(at)tcs(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: #PERSONAL# Reg: date going as 01/01/0001
Date: 2015-03-06 09:26:35
Message-ID: 20150306042635.070d7d9b1ae3ac743a7910ad@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 6 Mar 2015 10:04:38 +0530
Medhavi Mahansaria <medhavi(dot)mahansaria(at)tcs(dot)com> wrote:
>
> I need to enter the date in null column based on the results obtained.
>
> but my date gets inserted as 01/01/0001 in postgresql 9.3 when there is no
> value.
> I need to enter NULL in the column.

This isn't how PostgreSQL behaves. Something else is causing this
behavior ... either the client library or triggers or something
else configured on the table.

More detail would help us help you. Provide the CREATE TABLE
statement that created the table, as well as details of what
software you're using to execute the query, and the query
itself.

--
Bill Moran

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message wambacher 2015-03-06 09:39:34 Re: autovacuum worker running amok - and me too ;)
Previous Message wambacher 2015-03-06 08:53:37 Re: autovacuum worker running amok - and me too ;)