A "ScriptableKey" configuration is not a SearchKey, strictly speaking: a
  SearchKey generates Query instances from a value (the SearchKey contains the
  column information), and ScriptableKey's "script" does exactly that. So
  there is no need for any SearchKey to generate those Queries, so it's better
  to fix the feature at getColumnDefaultSearchKey caller's level.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25773 20353a03-c40f-0410-a6d1-a30d3c3de9de