]
Barry LaFond commented on TEIIDDES-570:
---------------------------------------
RelationalStringNameValidator or StringNameValidator.validate() uses a simple
StringNameValidator.validateStringNameChars() method which uses a simple
StringNameValidator which only allows:
1) // The first character must be an alphabetic character ...
2) // The remaining characters must be either alphabetic, digit or underscore character
...
This is a generic class that we use EVERYWHERE within Designer.
I think we need to be careful what we change here and maybe extend
RelationalStringNameValidator a little more to override the specific validate/check-char
methods.
Valid names can have almost any character, except periods. No
periods!
----------------------------------------------------------------------
Key: TEIIDDES-570
URL:
https://jira.jboss.org/browse/TEIIDDES-570
Project: Teiid Designer
Issue Type: Bug
Components: Validation
Affects Versions: 7.1
Environment: All
Reporter: Paul Nittel
This SQL:
SELECT t.* FROM
(EXEC WeatherData.invoke(action = 'GET', endpoint =
QUERYSTRING('', '38.99,-77.02 39.70,-104.80 47.6,-122.30' AS listLatLon,
'time-series' AS product, '2004-01-01T00:00:00' AS "begin",
'2013-04-20T00:00:00' AS "end", 'maxt' AS maxt, 'mint'
AS mint))) AS w, XMLTABLE('/dwml/data/location' PASSING result COLUMNS
"location-key" string, lattitude string PATH 'point/@latitude',
longitude string PATH 'point/@longitude') AS t
will fail as location-key contains a hyphen. Actually, the only character which is not
valid in a name is the period. Please verify with the Teiid server crew, but we should
loosen up the validation criteria as appropriate.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: