On Mon, 28 Feb 2005 19:57:59 +0100 (CET), Bernd Ruehlicke (JIRA) <derby-dev@db.apache.org> wrote: > [ > http://issues.apache.org/jira/browse/DERBY-147?page=comments#action_59875 ] > > Bernd Ruehlicke commented on DERBY-147: > --------------------------------------- > > Ok I made the changes and build Derby - and tested it - seams to work. > > We may consider to make this change permanent. > > Any reason for this error log was added ? > > Here the code snipled (need to chnage getOrderBy(String, String) and > getOrderBy(String, String, int) > > ... > if (columnName.equals( resultColumn.getName()) ) > { > if (retVal == null) > { > retVal = resultColumn; > } > // DERBY-147 else if (index < size - > orderBySelect) > // DERBY-147 { > // DERBY-147 throw > StandardException.newException(SQLState.LANG_DUPLICATE_COLUMN_FOR_ORDER_BY, > columnName); > // DERBY-147 } > else > {// remove the column due to pullup of orderby > item > removeElement(resultColumn); > decOrderBySelect(); > break; > } > } > ... >
Hi, Don't know why the system was coded to throw exception for duplicate columns but it seems like it has been around in Cloudscape from very beginning. Mamta
