[ http://issues.apache.org/jira/browse/DERBY-1306?page=comments#action_12449013 ] Bill Robertson commented on DERBY-1306: ---------------------------------------
I don't think it's a bug at all. It's a request for a feature improvment. Even if it's not according to the sql standard I think that the current behavior violates the principle of least surprise, which is never a good thing. > Support more than just varchar with vertical bars on query > ---------------------------------------------------------- > > Key: DERBY-1306 > URL: http://issues.apache.org/jira/browse/DERBY-1306 > Project: Derby > Issue Type: Improvement > Components: SQL > Affects Versions: 10.1.2.1 > Environment: Relevant for this? Windows XP > Reporter: Bill Robertson > > I'm not sure if this is ij or derby proper, but the concat operator || should > work for just about any data type. Derby is zero maintenance, but data > rarely is, and a good sql interface is important. Often it's very convenient > to write a query that generates other sql statements and that's difficult w/o > concatination. > e.g. create a table with a timestamp column, assume that the column name is > originated. > Try the following query: > ij> select month(originated) || '-' || year(originated) from review; > get the following error: > ERROR 42846: Cannot convert types 'INTEGER' to 'VARCHAR'. > The conversion to a string should pretty much work all the time unless the > operand is some sort of blob type. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
