List:MaxDB« Previous MessageNext Message »
From:Andrej Falout Date:October 15 2002 9:03am
Subject:RE: timestamp default '0000-00-00 00:00:00' = error
View as plain text  
In article <B9A2DDA03044D311BBD40008C75D69680DBAB33E@dewdfx24>, 
elke.zabach@stripped says...
> Andrej Falout  wrote:
> 
> > Since the beginning of the time...
> > 
> > Err, why is this OK:
> > 	default '0001-01-01 00:00:00',
> > but this is not?
> > 	'0000-00-00 00:00:00',
> 
> there is no month 0 and no day 0 possible in any case
> in a date/timestamp value. Which date should be specified by this?

Beginning of time as calculated by an obscure religious sect... :-)
 
> And as far as we know there was no year 0. Time-calculation started with year 1.
> Therefore : the whole date-portion of your 
> 0000-00-00 00:00:00
> is wrong.

What happened with time BC ? Like, if I want to store the year Egyptian kings 
where in power, this would be impossible?

Or more in timestamp spirit, how about calculated stellar events, that would 
have date AND time component too?
 
> If you just want to store time-values, please use the
> datatype time, no date/timestamp with 0-date-portion.

I'm porting existing SW (PostNuke) to SAP DB. Splitting timestamp (datetime) 
into date and time just to accommodate this is not an option. 
 
BTW, "0000-01-01 00:00:00' is invalid too... If only Romans knew...

Thanks,

-- 
Yours, Andrej Falout, http://www.falout.com/disclaimer.html
Visit the OpenSource alternative, Aubit 4gl: http://aubit4gl.sourceforge.net
PLEASE NOTE: All HTML email sent to me WILL BE DELETED AUTOMATICALLY WITHOUT 
READING.



Thread
timestamp default '0000-00-00 00:00:00' = errorAndrej Falout15 Oct
RE: timestamp default '0000-00-00 00:00:00' = errorElke Zabach15 Oct
  • RE: timestamp default '0000-00-00 00:00:00' = errorAndrej Falout15 Oct
RE: timestamp default '0000-00-00 00:00:00' = errorElke Zabach15 Oct