Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-12 Thread Medhavi Mahansaria
l-general@postgresql.org" Date: 03/06/2015 07:32 PM Subject: Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001 Medhavi Mahansaria wrote: > Now my problem is that my bind variables are of string type and > when the get a NULL value is converts it into an empty string

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-06 Thread John R Pierce
On 3/6/2015 2:12 AM, Medhavi Mahansaria wrote: I am porting my application from oracle to postgresql. in oracle it enters as NULL Oracle has the unique 'feature' that an empty string is NULL. This is contrary to the SQL spec. -- john r pierce 37N 122W

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-06 Thread Kevin Grittner
Medhavi Mahansaria wrote: > Now my problem is that my bind variables are of string type and > when the get a NULL value is converts it into an empty string in > C++ programming. > Example: > insert into check_date values > (to_date(:h1,'mmddhh24miss'), >1, >to_date(:h2,'mmddhh2

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-06 Thread Medhavi Mahansaria
03/06/2015 03:36 PM Subject: Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001 On Fri, 6 Mar 2015 15:24:28 +0530 Medhavi Mahansaria wrote: > Hi Bill, > > Here are the details of the table and the query i want to insert. > > > aml_db=> \d+ ch

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-06 Thread Karsten Hilbert
On Fri, Mar 06, 2015 at 03:24:28PM +0530, Medhavi Mahansaria wrote: > aml_db=> \d+ check_date > Table "public.check_date" > Column |Type | Modifiers | Storage | Stats > target | Description > ---+-+--

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-06 Thread Bill Moran
On Fri, 6 Mar 2015 15:24:28 +0530 Medhavi Mahansaria wrote: > Hi Bill, > > Here are the details of the table and the query i want to insert. > > > aml_db=> \d+ check_date > Table "public.check_date" > Column |Type | Modifiers | Stora

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-06 Thread Medhavi Mahansaria
__ Experience certainty. IT Services Business Solutions Consulting From: Bill Moran To: Medhavi Mahansaria Cc: pgsql-general@postgresql.org Date: 03/06/2015 02:56 PM Subjec

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-06 Thread Bill Moran
On Fri, 6 Mar 2015 10:04:38 +0530 Medhavi Mahansaria 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 behave

Re: [GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-05 Thread John R Pierce
On 3/5/2015 8:34 PM, Medhavi Mahansaria 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. umm, it seems to work fine for me?you give us no

[GENERAL] #PERSONAL# Reg: date going as 01/01/0001

2015-03-05 Thread Medhavi Mahansaria
Hi, 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. can anyone please help me out. Its urgent. Thanks in advance. Regards Medhavi Mahansaria Tata Con