🚀 go-pugleaf

"Arno Brinkman" <bnewsgroups @ abvisie.nl> wrote in message
news:3dea6f7e@newsgroups.borland.com...
> Hi,
>
> > How does one convert:
> >
> > 1) A 32-bit integer date value to an acceptable SQL value for a DATE
> column,
> > or does a 32-bit numeric value suffice ?
> > 2) A 32-bit integer time value to an acceptable SQL value for a TIME
> column,
> > or does a 32-bit numeric value suffice ?
> > 3) A 64-bit large integer value to an acceptable SQL value for a
TIMESTAMP
> > column, or does the 64 bit numeric value suffice ?
> >
> > Essentially what are the acceptable values for inserting or updating a
> DATE,
> > TIME, or TIMESTAMP value in an SQL statement in Interbase ?
>
> I can't find any specific format's in the standard-SQL language, but as
far
> as i know the most db-engines supports these formats (and so does
Interbase)
> :
>
> DATE : YY-MM-DD
> TIME : HH:NN:SS
> TIMESTAMP : YY-MM-DD HH:NN:SS

One of the problems is that sequence, at least as far as the date value, is
concerned, is locale dependent. In the US the dates are MM-DD-YY. So how
does one know which format to use ? I have searched for the SQL format for
DATE, TIME, and TIMESTAMP for Interbase in the docs to no avail. But this
seems par for the Interbase docs, which are terrible. No wonder Borland has
had such a hard time selling Interbase to customers.