Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Release Branch 4.0
-
None
Description
This may not affect other DBMS', but it definitely affects MS-Sql. Even though a "workaround" would be to only have 1 picklist at a time, I don't exactly consider that acceptable. Fortunately, it's an easy fix. It looks like this issue still lurks in the trunk as well. To sum it up, getPicklistSingleInfoInline is called for each picklist. In the method there is an "orderBy" list to which "sequenceId" is added. The first pass works fine, on the second pass, "sequenceId" is added to the list again and MS-Sql complains because the column is in the "order by" clause twice. The solution is to clear the field before-hand.