It's not part of the 2003 spec. Function names don't necessarily have to be
reserved though.
----- Original Message -----
From: "John Doyle" <jdoyle(a)redhat.com>
To: "Steven Hawkins" <shawkins(a)redhat.com>
Cc: "teiid-users" <teiid-users(a)lists.jboss.org>, "teiid-dev"
<teiid-dev(a)lists.jboss.org>
Sent: Monday, March 1, 2010 10:41:03 AM GMT -06:00 US/Canada Central
Subject: Re: [teiid-users] [teiid-dev] additional reserved words for Teiid 7.0
Steve,
Do you know if XMLTABLE is a SQL/XML function? I've read some articles that say it
is, and others that don't mention it. I consider it more useful than the other
SQL/XML functions for our use cases and thing we should implement it.
~jd
----- "Steven Hawkins" <shawkins(a)redhat.com> wrote:
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
| IMPORT
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.
~jd
----- "Ramesh Reddy" <rareddy(a)redhat.com> wrote:
> I would like Teiid to take on the support of data types based on
DBMS
> like MySQL or H2 or HSQL. As we have the supporting DDL based
> metadata
> 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.
>
> Ramesh..
>
> 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
> identifier.
> >
> > 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
> procedure
> >
> > extract function (to be added) targets:
> >
> > day
> > hour
> > minute
> > month
> > second
> > timezone_hour
> > timezone_minute
> > year
> >
> > Other possible reserved words could include all of
>
http://savage.net.au/SQL/sql-2003-2.bnf.html#reserved%20word. One
> 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
> quotes.
> >
> > Any thoughts?
> > _______________________________________________
> > teiid-users mailing list
> > teiid-users(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/teiid-users
>
> _______________________________________________
> teiid-dev mailing list
> teiid-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/teiid-dev
_______________________________________________
teiid-users mailing list
teiid-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-users