Same here. None of the modern providers supports this. Andrus
> On Feb 15, 2017, at 12:46 PM, Aristedes Maniatis <a...@maniatis.org> wrote: > > It was a really neat feature and we used it. But we had to come up with > different solutions when we moved away from OSCache some time ago. > > Ari > > > On 15/2/17 8:34pm, Andrus Adamchik wrote: >> FYI... I really hope no one depends on multiple cache groups per query, as >> we can't support those going forward. >> >> Andrus >> >> >> >>> Begin forwarded message: >>> >>> From: "Nikita Timofeev (JIRA)" <j...@apache.org> >>> Subject: [jira] [Created] (CAY-2228) Deprecate multiple cache groups in >>> caching and query API >>> Date: February 15, 2017 at 12:07:41 PM GMT+3 >>> To: comm...@cayenne.apache.org >>> Reply-To: dev@cayenne.apache.org >>> >>> Nikita Timofeev created CAY-2228: >>> ------------------------------------ >>> >>> Summary: Deprecate multiple cache groups in caching and query API >>> Key: CAY-2228 >>> URL: https://issues.apache.org/jira/browse/CAY-2228 >>> Project: Cayenne >>> Issue Type: Improvement >>> Components: Core Library >>> Reporter: Nikita Timofeev >>> Assignee: Nikita Timofeev >>> Fix For: 4.0.M5 >>> >>> >>> We should drop support for multiple cache groups as it have little >>> practical sense. >>> Only available caching provider with proper support for it is OS Cache and >>> it is obsolete and should be actually deprecated too. >>> >>> So here is required API changes: >>> - replace internally multiple cache groups with single group >>> - deprecate corresponding 3.1 API and warn when multiple cache groups >>> provided >>> - remove corresponding 4.0 API completely (e.g. in fluent queries API) >>> >>> >>> >>> -- >>> This message was sent by Atlassian JIRA >>> (v6.3.15#6346) >> >> > > -- > --------------------------> > Aristedes Maniatis > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
