> >>> Allow optional () after current_user, session_user, user, current_time,
> >>> current_timestamp, current_date for ODBC compatibility.
> >> It's not apparent to me that this is an improvement in our standards
> >> compatibility.
> > ODBC is generally thought of as being a standard.
> True ... if it's okay with Thomas then I won't object.
ODBC is a standard, but not the standard targeted by our implementation
of SQL in the backend, and does not *require* direct support for all
features in the backend. In some cases, we solve that in the ODBC
driver, with perhaps help from extensions defined in odbc.sql.
SQL99 indicates that an argument between parens is required, so this
would be an extension to that standard. Also, if we agree that this
extension must be in the backend because the ODBC driver cannot
implement it (I'm not certain about that; it looks pretty reasonable to
fit it in with a few changes to the mapFunction() routine) then I'd like
to see it implemented as part of the original CURRENT_TIME(arg)
definition, not as a completely separate rule (or did you get
shift/reduce conflicts trying it that way?).
- Thomas