[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] OT: Interbase CURRENT_TIMESTAMP problems...
- Subject: Re: [cobalt-developers] OT: Interbase CURRENT_TIMESTAMP problems...
- From: "Richard Abrams" <richard@xxxxxxxxxxxxxx>
- Date: Mon Mar 25 00:41:05 2002
- Organization: Artejano Design and Marketing
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
> I use interbase with TIMESTAMP datatype, and I use it by this way
>
> create table TABLE (
> id integer,
> date TIMESTAMP default 'NOW'
> );
Thanks Edgar,
I'll give that a go - it's strange as Interbase claims to support
CURRENT_TIMESTAMP in accordance with the SQL standard.
After some research it appears that the date it keeps stamping (17 November
1858) is considered Year 0 by Borland. It's something like Year 0 of the
Julian calender adjusted by +2400000.5 to match the Gregorian system... or
something :-)
--
Richard Abrams
Lead Web Developer
www.artejano.com