From dev-return-8237-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Sun May 25 00:38:20 2008 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 95018 invoked from network); 25 May 2008 00:38:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 May 2008 00:38:19 -0000 Received: (qmail 27220 invoked by uid 500); 25 May 2008 00:38:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 27188 invoked by uid 500); 25 May 2008 00:38:20 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 27159 invoked by uid 99); 25 May 2008 00:38:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 May 2008 17:38:20 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 May 2008 00:37:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2C66E234C120 for ; Sat, 24 May 2008 17:37:56 -0700 (PDT) Message-ID: <1244067821.1211675876166.JavaMail.jira@brutus> Date: Sat, 24 May 2008 17:37:56 -0700 (PDT) From: "Fay Wang (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Created: (OPENJPA-611) The findBy behaves differently when DataCache is on in some situations. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The findBy behaves differently when DataCache is on in some situations. ----------------------------------------------------------------------- Key: OPENJPA-611 URL: https://issues.apache.org/jira/browse/OPENJPA-611 Project: OpenJPA Issue Type: Bug Reporter: Fay Wang In the following two situations, the behavior of findBy with DataCache on is different from the same findBy with DataCache off: (1) When there is @PrimaryKeyJoinColumn annotation on the relation fields: Even though no relation is explicitly set in the application, when retrieving from the database, the relation field will be populated. However, if DataCache is on, the relation fields will not be populated via findBy from data cache. (2) When more than one fields are mapped to the same column with insertable=false or updateable=false: Setting different values to these fields will be saved in and restored from the datacache, but the the database will return only one value for these fields. The attached patch detects the above two situations and set the flag to instruct DataCacheStoreManager not to cache the instances of these kinds of entities so that the findBy operation for these two kinds of entities will always go to the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.