More on CURRENT_TIME and changes

Hi,

After the recent thread on CURRENT_TIME, I thought the note in the b4
changelog odd:

2001-12-09 19:01 thomas

* src/interfaces/odbc/: convert.c, odbc.sql: Support
ODBC-style CURRENT_TIME, CURRENT_USER, etc with trailing
empty parens. This is not SQL spec syntax, so later we will
remove this extension from gram.y.

Ok, now I understand the reasoning behind adding this (ODBC
compliance) and the reasoning behind refusing to add it (SQL
compliance). But why add it once, planning later to remove it? This
strikes me as likely to cause the same sort of confusion as the
recent discusisons around LIMIT..OFFSET. Why add a feature that you
are _planning_ to remove later?

A

--
----
Andrew Sullivan 87 Mowat Avenue
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M6K 3E3
+1 416 646 3304 x110