Currently, the standard filter expects to find a column on which a filter can be applied.
This leads to the necessity to create a large table with all possible filter columns joined.
Actually, we just join all the custom fields, which makes our queries unnecessarily slow, even when we don't filter at all.
ad A) This will lead to problems in the way we add sql customfields now. It might be necessary to still add the columns with the shortnames of the customfields, but possibly just returning an empty string as value, instead of the joining on the real customfields.
Currently, the standard filter expects to find a column on which a filter can be applied.
This leads to the necessity to create a large table with all possible filter columns joined.
Actually, we just join all the custom fields, which makes our queries unnecessarily slow, even when we don't filter at all.
ad A) This will lead to problems in the way we add sql customfields now. It might be necessary to still add the columns with the shortnames of the customfields, but possibly just returning an empty string as value, instead of the joining on the real customfields.