elieve this enhancement would allow us to leverage caching with
>>> entity
>>> conditions that want to restrict by current date/time.
>>>
>>> If we go ahead and create a JIRA and package this up; does the
>>> community
>>> think this would be valuable?
>>
>> Yes, that sounds fine to me and would be a good improvement.
>>
>> -David
>>
>>
>>
>
>
--
View this message in context:
http://n4.nabble.com/Screen-based-cache-recommendation-tp277012p277080.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
t; entity
>> conditions that want to restrict by current date/time.
>>
>> If we go ahead and create a JIRA and package this up; does the
>> community
>> think this would be valuable?
>
> Yes, that sounds fine to me and would be a good improvement.
>
> -David
>
>
>
--
View this message in context:
http://n4.nabble.com/Screen-based-cache-recommendation-tp277012p277032.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
On Oct 26, 2009, at 8:55 AM, Bob Morley wrote:
We have been spending some time looking at caching in Ofbiz. One
pattern
that we have seen in services is to perform a query (with caching
on) and
then on the result apply EntityUtil.filterByDate (to restrict to non-
expired
records). We b
rovide the client-side filtering.
We believe this enhancement would allow us to leverage caching with entity
conditions that want to restrict by current date/time.
If we go ahead and create a JIRA and package this up; does the community
think this would be valuable?
--
View this message in
