Return-Path: Delivered-To: apmail-cayenne-user-archive@www.apache.org Received: (qmail 67767 invoked from network); 13 May 2009 13:28:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 May 2009 13:28:59 -0000 Received: (qmail 89360 invoked by uid 500); 13 May 2009 13:28:59 -0000 Delivered-To: apmail-cayenne-user-archive@cayenne.apache.org Received: (qmail 89334 invoked by uid 500); 13 May 2009 13:28:58 -0000 Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cayenne.apache.org Delivered-To: mailing list user@cayenne.apache.org Received: (qmail 89317 invoked by uid 99); 13 May 2009 13:28:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 May 2009 13:28:58 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of borut.bolcina@gmail.com designates 209.85.218.171 as permitted sender) Received: from [209.85.218.171] (HELO mail-bw0-f171.google.com) (209.85.218.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 May 2009 13:28:50 +0000 Received: by bwz19 with SMTP id 19so812711bwz.4 for ; Wed, 13 May 2009 06:28:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=m08hciI9StYOG9KC6Sv6k+uXLTDDrb0hCUtW+nQIWN4=; b=gQhYIjuyV1/KFRamAfeR1zXPvx7Yhvhv8cA3n25syH3hSvf/ypZ7VkY6fAn4YEcNxF iE+REEq/t4M9UlYCNJEXDTQp9ibhbc4ZwVE7AedHAN/1tSVi4aY47hqt4TA1Mm3CP63p 4NVX1iCtaX/jatBnH4CHYEmGmVCfgjtB/+Cks= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=fYWcJzD27DXIOO1RDouy9G6PvN/wiqROzlT/++TTlPa6Ir7v7m5pXLxh1YKOv3YB+Y XThq5lESsrPe2Eorkjz9h9oZQFkgoZvYS25EFWypBMHfo7nriFcxxjVSLn8NUGinFVLp 4aTZIDZQn+k31FecEy9I36DEQyDV82CTCscBY= MIME-Version: 1.0 Received: by 10.204.114.136 with SMTP id e8mr890311bkq.190.1242221308679; Wed, 13 May 2009 06:28:28 -0700 (PDT) In-Reply-To: <86C2117E-94F8-4B8A-B6B3-DB51B0850C44@objectstyle.org> References: <86C2117E-94F8-4B8A-B6B3-DB51B0850C44@objectstyle.org> Date: Wed, 13 May 2009 15:28:28 +0200 Message-ID: Subject: Re: 3.0 cache documentation From: =?UTF-8?Q?Borut_Bol=C4=8Dina?= To: user@cayenne.apache.org Content-Type: multipart/alternative; boundary=0016368e2b20d618ed0469cb2fa4 X-Virus-Checked: Checked by ClamAV on apache.org --0016368e2b20d618ed0469cb2fa4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, I am reading the cache docs now and have some suggestions and queations: "QueryCache Management The query cache provider is installed via org.apache.cayenne.cache.QueryCacheFactory. The factory can be configured in the Modeler for the DataDomain..." Create a note that this functionality is not available in current release. "...or set in code" An example would be of great value. Now a question. Let's say I create a select query on paintings with OSCache cache group paintings. Lets say there are 3 paintings: p1, p2 and p3. Now they are cached in object cache and in separete query cache? Two cache entries? Let's say I create another painting and insert it into the db. The new painting p4 is now in object cache. If I want to have fresh list of paintings, I now have to invalidate the paintings cache group in the onCommit callback function. Is there an alternative, like simply adding this p4 to cache group paintings? If not, will the subsequent fetch contact the db for all p1-p4 or is there a way that paintings will get fetched from object cache if they are there? I want to avoid reading (tens of)thousands of rows because occasionally some get inserted. Regards, Borut 2009/5/4 Andrus Adamchik > > Finally got around to documenting how the caching works in the latest Cayenne: > > http://cayenne.apache.org/doc/caching-and-fresh-data.html > > Note that the references to cache groups and factories configuration via the Modeler are applicable to the trunk code (yet unreleased 3.0M6). 3.0M5 has all the same features, but working via the API. > > I tried to stay away from the implementation details and give a user perspective instead. If there is still a feeling that the docs are lacking in this area, please share your thoughts. I will try to address any reasonable suggestions. > > Andrus --0016368e2b20d618ed0469cb2fa4--