In a collectionFilter, numeric columns are filtered with = and character columns are filtered with LIKE, however, if either a numeric column or a character column is a foreign key to another table, either of these filters become less desirable.

With a character column, the foreign key is evaluated with %content% which isn't likely to cause any problems, but may not perform as well.

With a numeric column populated by sequence or identity, the = filter is merely limiting, preventing the use of checkboxes or multiple-select inputs allowing the user to indicate multiple foreign records.

A smarter collectionFilter alrogithm would filter all foreign keys using an &quot;IN&quot; filter, allowing for multiple selection and eliminating wildcards.

History:

Created by ike (Isaac Dealey) : 08/09/08 10:26 PM

Comment by ike (Isaac Dealey) : 05/05/12 9:09 PMI think I already fixed this a while ago, but I'm not 100% certain.

Updated by ike (Isaac Dealey) : 04/29/14 11:02 PM

To add a comment to this bug, please login using the link above.

Adobe and the Adobe product names are either registered trademarks or
trademarks of Adobe Systems Incorporated in the United States and/or other
countries.