Rule-based renderer: if rule does not use correct case, "test" succeeds, but no features are rendered

[Alister]

Using the rule based renderer in the new symbology:

e.g. I have a layer with a field named ENVCLASS. If I set up rules based on this class, but all with incorrect case (e.g. EnvClass=1), then the "test" button says the rule works (returns 51 features or whatever), but no features are rendered. If I change one of the rules to use the correct case (ENVCLASS), then all the features are rendered.

[Alister]

Why does Trac set up random links (or whatever they are) with a question mark like the "EnvClass?" above? I didn't put a "?".

[NathanW]

Regarding the random links: It does this because of the wiki link syntax. If you have two or more upper case letters in one word it thinks it's a internal wiki page link. Well that is how most wikis work, so I'm guessing it's the same.

[lutra]

The filter in the rule based renderer has now a query builder (in trunk), this way the problem should be fixed.

[Alister]

The query builder is very nice, but the bug is still valid.

The user can still manually type in the rule (either in the rule properties window or in the query builder). If the case is incorrect the test button (either in the rule properties window or in the query builder) will say the rule works, but nothing will be rendered.

[wonder]

fixed in r14932