Thread

1. Re: Converting a timestamp to a date when it contains nulls.

   Michael Richards <michael@fastmail.ca> — 2000-07-23T19:52:37Z

   > "Michael Richards" <michael@fastmail.ca> writes:
   >> Shouldn't all casts be able to handle the case where it is NULL?
   >
   > Yup, it's a bug.  It's fixed in current sources.
   
   Is there a patch available that I can apply to the 7.0.2 source to 
   fix the problem? Or is there going to be a 7.0.3 that I should wait 
   for?
   
   -Michael

2. Re: Converting a timestamp to a date when it contains nulls.

   Tom Lane <tgl@sss.pgh.pa.us> — 2000-07-24T03:21:51Z

   "Michael Richards" <michael@fastmail.ca> writes:
   >>> Shouldn't all casts be able to handle the case where it is NULL?
   >> 
   >> Yup, it's a bug.  It's fixed in current sources.
   
   > Is there a patch available that I can apply to the 7.0.2 source to 
   > fix the problem? Or is there going to be a 7.0.3 that I should wait 
   > for?
   
   Just look for the place where the error is being spit out (somewhere in
   backend/utils/adt/) and change the "elog(ERROR, ...)" call into
   "return NULL".  Should work, but I haven't tried it in 7.0.
   
   			regards, tom lane