On 23/10/2018 11:36, Mark Rotteveel wrote: > On 23-10-2018 16:20, liviuslivius wrote: >> Really strange "standard" here... > > Standards are nothing but inconsistent, especially as they evolve over > time. However, CURRENT_TIME dates back to at least the SQL:92 standard > (and probably existed earlier in some form in non-standardized > dialects), while LOCALTIME is more recent (probably SQL:1999 or > SQL:2003). > > And there might also be a semantic reason for it. The LOCAL in > LOCALTIME and LOCALTIMESTAMP describes an aspect of the datatype (that > it is without timezone), while the CURRENT in CURRENT_TIME and > CURRENT_TIMESTAMP describes an aspect of the value (the 'when'). > > They could also have chosen to use CURRENT_LOCALTIME, but maybe they > judged that too long.
AFAIK, but I may be wrong, "TIMESTAMP" is not a correct single word too. :) Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
