[ http://issues.apache.org/jira/browse/DERBY-392?page=comments#action_12314431 ]
Daniel John Debrunner commented on DERBY-392: --------------------------------------------- Not sure why we would remove a working feature, applications may be dependent on it. Now it may be that such indexes are not really working beause the btree has a limit on key length that would be make them not useable if the key value was over 1/2 page length. Or maybe if long varchar for bit data is not comparable then obviously they can't be used and so it's a bug allowing such an index. > Disable creating indexes on long varchar for bit data. Long varchar column > doesn't allow creating indexes already. > ------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-392 > URL: http://issues.apache.org/jira/browse/DERBY-392 > Project: Derby > Type: Bug > Components: SQL > Versions: 10.1.1.0, 10.0.2.2 > Environment: generic > Reporter: Satheesh Bandaram > Priority: Minor > > It should not be possible to create an index on 'long varchar for bit data' > datatypes. Derby currently doesn't allow creating indexes on 'long varchar' > datatypes and the same should apply for it's bit data equivalent too. > ij> create table longchar ( i int, c long varchar); > 0 rows inserted/updated/deleted > ij> create index longIdx on longchar(c); > ERROR X0X67: Columns of type 'LONG VARCHAR' may not be used in CREATE INDEX, > ORD > ER BY, GROUP BY, UNION, INTERSECT, EXCEPT or DISTINCT statements because > compari > sons are not supported for that type. > ij> create table longcharBitData ( i int, c long varchar for bit data); > 0 rows inserted/updated/deleted > ij> create index longIdx on longcharBitData(c); > 0 rows inserted/updated/deleted -- 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
