Emanuele Panzeri
Emanuele Panzeri
@JohannesTyra what about providing the new cache layer in https://github.com/FriendsOfSymfony1/CacheLegacyBridge ? IIRC SymfonyCache already supports the Memcached backend
@alquerci @JohannesTyra @desyncr Is it OK for you to close this PR?
Closing as the proper way to include the doctrine1 plugin is: `composer require friendsofsymfony1/doctrine1`
Sorry @garak , my bad! I got confused about this one! anyway: would the removal be a BC break? handling those case on Symfony1 is a bit tricky I'd say...
I see, but if a project just requires: * friendsofsymfony1/symfony1 * friendsofsymfony1/doctrine1 will break if we release such "removal" as a minor update as the plugin will not be available...
I can confirm @magibney answer. If the field is analyzed with `string` and it contains more than 200 words the above exception is thrown. If a "short" field is used...
A first implementation for `value:[123 TO 555]` is in #14
@pspanja the exclusive should be "easy" to achive, but there is something not clear to me in the regexp you're using in the phrase token: What's the `(?
@pspanja inclusive/exclusive range added, I'll add later the support for the date ranges
Thanks for the explanation @pspanja! Should the `range` implementation be split into inclusive/exclusive (as this patch) and an additional MR for the other cases?