Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 8546 invoked from network); 2 Dec 2009 17:08:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Dec 2009 17:08:36 -0000 Received: (qmail 90266 invoked by uid 500); 2 Dec 2009 17:08:35 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 90214 invoked by uid 500); 2 Dec 2009 17:08:35 -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 90206 invoked by uid 99); 2 Dec 2009 17:08:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2009 17:08:35 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 88.198.21.77 is neither permitted nor denied by domain of malesch@gmail.com) Received: from [88.198.21.77] (HELO ahi.calclab.com) (88.198.21.77) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2009 17:08:33 +0000 Received: from localhost (localhost [127.0.0.1]) by ahi.calclab.com (Postfix) with ESMTP id 75F938000AF for ; Wed, 2 Dec 2009 18:08:12 +0100 (CET) X-Virus-Scanned: calclab Virus-Scanner Received: from ahi.calclab.com ([127.0.0.1]) by localhost (calclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UiMaqLO4GcG2 for ; Wed, 2 Dec 2009 18:07:58 +0100 (CET) Received: from [192.168.0.75] (32-91.5-85.cust.bluewin.ch [85.5.91.32]) by ahi.calclab.com (Postfix) with ESMTPSA id 547F78000A5 for ; Wed, 2 Dec 2009 18:07:58 +0100 (CET) Message-ID: <4B169EED.5080609@gmail.com> Date: Wed, 02 Dec 2009 18:07:57 +0100 From: malesch User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Derby Discussion Subject: Re: Different DB behavior loaded from JAR vs. file system References: <4B1546CD.3010907@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Dag I connect to my DB with the same user name with the default schema APP and, what I forgot to mention last time, the DB is encrypted. Now while creating a little program to demonstrate the effect I stumbled over something pointing to a possible explanation :-). I realized that in my demo with the extracted DB (on the file system) the expected tables didn't show up (like in the JAR case). Disappointed I opened the same DB with SquirellSQL and, surprise, the tables were there again. After this opening with SquirellSQL my demo programm showed again the previously missing tables. Is there some transaction log which is not commited and what would be the reason for this (simply not properly commiting/closing the DB?) Greetings, marcus Dag H. Wanvik wrote: > malesch writes: > >> I am seeing some very strange behavior with my Derby DB >> (version 10.4.2.0 and 10.5.3.0). >> >> If I load my DB from a JAR file, I am missing some table >> entries, that are existing if I extract the DB from the >> same JAR file and load it from the file system. >> >> How can I understand this behavior, is there an >> explanation for this? > > That seems weird. Are you connecting with the same user name (or none) > in the two scenarios? Occasionally we see users miss some tables > because they end up in an unexpected schema; the default schema is the > user name (or "APP" if not provided). > > If this is not the issue, are you able to provide a repro for it? > > Thanks, > Dag