Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 28658 invoked from network); 18 Nov 2005 14:46:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Nov 2005 14:46:56 -0000 Received: (qmail 29093 invoked by uid 500); 18 Nov 2005 14:46:54 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 29072 invoked by uid 500); 18 Nov 2005 14:46:53 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 29057 invoked by uid 99); 18 Nov 2005 14:46:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2005 06:46:53 -0800 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of michaelm001@frontiernet.net designates 66.133.182.166 as permitted sender) Received: from [66.133.182.166] (HELO relay03.roc.ny.frontiernet.net) (66.133.182.166) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2005 06:48:25 -0800 Received: from filter01.roc.ny.frontiernet.net (filter01.roc.ny.frontiernet.net [66.133.183.68]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 77B6535863C for ; Fri, 18 Nov 2005 14:46:30 +0000 (UTC) Received: from relay03.roc.ny.frontiernet.net ([66.133.182.166]) by filter01.roc.ny.frontiernet.net (filter01.roc.ny.frontiernet.net [66.133.183.68]) (amavisd-new, port 10024) with LMTP id 05918-02-97 for ; Fri, 18 Nov 2005 14:46:30 +0000 (UTC) Received: from [192.168.254.1] (67-137-33-205.dsl2.elk.ca.frontiernet.net [67.137.33.205]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 1649835838A for ; Fri, 18 Nov 2005 14:46:29 +0000 (UTC) Message-ID: <437DE950.3050206@frontiernet.net> Date: Fri, 18 Nov 2005 06:46:40 -0800 From: Michael McCutcheon User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Discussion Subject: Re: SV: Is Hibernate inappropriate for embedded databases? References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new-2.3.2 (20050629) at filter01.roc.ny.frontiernet.net X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N But what about the 'double caching' problems for an embedded scenario? Henrik Johansson wrote: >I tried JBoss Embedded which uses Hibernate for a small test >and it worked like a charm with Derby. > >Using Hibernate alone (or with JBoss Embedded) seems to be a >very good idea in my opinion for all sorts of reasons. > >Too bad its seemingly not production ready... > >Hibernate alone would be clever since it is very well tested and >there is no idea to reinvent the wheel. > >/ Henrik > > >-----Ursprungligt meddelande----- >Fr�n: Michael McCutcheon [mailto:michaelm001@frontiernet.net] >Skickat: den 18 november 2005 05:33 >Till: Derby Discussion >�mne: Is Hibernate inappropriate for embedded databases? > > >I'm still struggling to figure out if I should go with strait JDBC, >stored procedures or something like Hibernate for my data access/update >in my web app running on Tomcat. > >I've been looking at Hibernate, and it seems that it's claim to fame is >all of the fancy caching it can do to speed performance. > >However, doesn't derby itself cache data in memory (once the data is >accessed)? > >If the caching functionality in Hibernate is used for an embedded >database, doesn't that just mean that the data will be cached twice >(once in derby, once in hibernate), resulting in memory bloat and >potentially worse performance? > >Any thoughts on this issue would be appreciated. > >Mike > > > > > >