I'm working on some reports for our RT database, and I'm noticing that
fields get populated with 1/1/1970 if there is nothing entered into the
DB.
Is this accurate assessment? If so can I just assume that 1/1/1970 =
null?
Thanks in advance.
Justin Brodley
At Tuesday 6/19/2007 11:26 AM, Justin Brodley wrote:
I'm working on some reports for our RT database, and I'm noticing
that fields get populated with 1/1/1970 if there is nothing entered
into the DB.
Is this accurate assessment? If so can I just assume that 1/1/1970 = null?
Yes, that's
Subject: Re: [rt-users] Question about Dates in DB
At Tuesday 6/19/2007 11:26 AM, Justin Brodley wrote:
I'm working on some reports for our RT database, and I'm noticing
that fields get populated with 1/1/1970 if there is nothing entered
into the DB.
Is this accurate assessment? If so can I
FWIW, a brief snoop didn't turn up any null date fields in our MySQL RT
database.
Gene
At 08:31 AM 6/19/2007, Stephen Turner wrote:
At Tuesday 6/19/2007 11:26 AM, Justin Brodley wrote:
I'm working on some reports for our RT database, and I'm noticing that
fields get populated with 1/1/1970
Yes, 1/1/1970 is equal to 'Not set', but I think you have to expect
this to be changed to real NULL as I have very strong wish to change
it as NULLs are clearer, easier for development and more flexible.
Hope we'll have time to do it before 3.8.0
On 6/19/07, Stephen Turner [EMAIL PROTECTED]
: Tuesday, June 19, 2007 12:09 PM
To: Stephen Turner
Cc: Justin Brodley; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Question about Dates in DB
Yes, 1/1/1970 is equal to 'Not set', but I think you have to expect
this to be changed to real NULL as I have very strong wish to change
it as NULLs
