Additional reserved words could then include:
SQL/XML: XML (already added) | XMLAGG | XMLATTRIBUTES | XMLBINARY | XMLCONCAT
| XMLCOMMENT | XMLELEMENT | XMLFOREST
| XMLNAMESPACES | XMLPARSE | XMLPI | XMLROOT | XMLSERIALIZE
SQL/MED: DATALINK | DLNEWCOPY | DLPREVIOUSCOPY | DLURLCOMPLETE | DLURLCOMPLETEWRITE
| DLURLCOMPLETEONLY | DLURLPATH | DLURLPATHWRITE | DLURLPATHONLY
| DLURLSCHEME | DLURLSERVER | DLVALUE
I could also look into updating the parser to remove unnecessary reserved words, such as
oj, fn, timestamp(add|diff), sql_tsi... constants, etc., but since these are unlikely
identifiers it seems unnecessary.
----- Original Message -----
From: "John Doyle" <jdoyle(a)redhat.com>
To: "Ramesh Reddy" <rareddy(a)redhat.com>
Cc: "teiid-users" <teiid-users(a)lists.jboss.org>, "teiid-dev"
<teiid-dev(a)lists.jboss.org>, "Steven Hawkins" <shawkins(a)redhat.com>
Sent: Monday, March 1, 2010 10:07:24 AM GMT -06:00 US/Canada Central
Subject: Re: [teiid-dev] [teiid-users] additional reserved words for Teiid 7.0
I would also add in the SQL/XML keywords.
----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
I would like Teiid to take on the support of data types based on
like MySQL or H2 or HSQL. As we have the supporting DDL based
on the road map, it would good to add any of those keywords upfront
(that we know of from SQL DDL)
+1 for adding the all words from the SQL-2003 list you provided.
On Sun, 2010-02-28 at 23:19 -0500, Steven Hawkins wrote:
> Hello all,
> I would like to propose adding additional reserved words. Some of
which would be used immediately others would be place holders for
future features and would help prevent users from using identifier
names that will conflict. There is the potential for breaking
existing vdbs though that use any of these words as an unqualified
> This includes:
> bigint - type alias for long
> decimal - type alias for bigdecimal
> real - type alias for real
> smallint - type alias for short
> tinyint - type alias for byte
> varchar - type alias for string
> call - to be used as a standard alternative to exec/execute a stored
> extract function (to be added) targets:
> Other possible reserved words could include all of
minor issue is that the reserved word input conflicts with our "input"
variable group used in update procedures. Since it wouldn't be used
as a table reference, it would break existing vdbs, but the generated
output strings for parsed commands would include input in double
> Any thoughts?
> teiid-users mailing list
teiid-dev mailing list