]
Steven Hawkins resolved TEIIDDES-256.
-------------------------------------
Fix Version/s: 7.1
Resolution: Done
Marking as resolved as per the last comment. There may still be issues with name casing
though as Teiid is case insensitive with its identifiers.
Teiid is making column names upper case, even when specified as
lower
---------------------------------------------------------------------
Key: TEIIDDES-256
URL:
https://jira.jboss.org/browse/TEIIDDES-256
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 6.2.0
Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid
build 1/19/2010
Reporter: Paul Nittel
Fix For: 7.1
Attachments: TextMetadataTesting.zip
I've got a transformation that defines two columns like this:
SELECT
c_count, COUNT(*) AS custdist
FROM
(SELECT C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT
OUTER JOIN TPCR.ORDERS ON C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE
'%special%requests%' GROUP BY C_CUSTKEY) AS c_orders
GROUP BY c_count
In the past, when queried (SELECT * FROM ...), the columns were spelled c_count and
custdist. Now they're spelled C_COUNT and custdist. Do we now upcase column names that
are not specified as an alias (or do we only preserve case on aliases)?
I noticed this in AdminShell, but see the Designer is also doing it, so I'm thinking
it's the query engine, not the tool. (Steve H. agreed it should still be lower case
when queried.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: