Alexander Makarov
Alexander Makarov
@tunecino thanks for suggestion.
Need more time to recheck and prepare it for release.
Would you please check test failures?
Seems to be tricky to properly fix it. There are database-specific differences.
Doesn't seem there's anything to fix in the code but definitely worth documenting it.
Yeah, good topic.
@schmunk42 is it still an issue?
I think it wasn't initially implemented. Efficient wildcard-fields were introduced fairly recently and before that wildcard queries were super-inefficient and even required a special option to be allowed.
There will be no 2.1. Could be closed.
It won't be relevant for 3.0. It's a big step forward and we had to break things...