Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 30317 invoked from network); 16 Apr 2007 19:29:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Apr 2007 19:29:56 -0000 Received: (qmail 11650 invoked by uid 500); 16 Apr 2007 19:29:46 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 11612 invoked by uid 500); 16 Apr 2007 19:29:45 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 11579 invoked by uid 99); 16 Apr 2007 19:29:45 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2007 12:29:45 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [68.142.225.207] (HELO smtp109.rog.mail.re2.yahoo.com) (68.142.225.207) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 16 Apr 2007 12:29:36 -0700 Received: (qmail 85903 invoked from network); 16 Apr 2007 19:29:15 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:X-MimeOLE:In-Reply-To:Thread-Index; b=edMFocwKXdfZ/kKhCnNVIzN6ka2H/JsGA6juMrUvPr74x53iLIhBqpHvCnIhxKBOQRZ9o9rLwbpMoE7DxENavEwHIYz6u/OcfFsgFWpdc8cTbbmvuyzarAr30iM5wur4vrJsVfV8hpyzuFrw5QQ7A8xvgJsow26iJw8dY/Lwo/Q= ; Received: from unknown (HELO tyan2400) (pjmoran@rogers.com@74.103.61.203 with login) by smtp109.rog.mail.re2.yahoo.com with SMTP; 16 Apr 2007 19:29:15 -0000 X-YMail-OSG: udg7158VM1kcxGhNIaP3_6BPLREnNcVQ1S.wrDEXjv1lKu4UOANbSwka8VjGXNEhxA-- From: "Phill Moran" To: Subject: RE: Duplicate query Date: Mon, 16 Apr 2007 15:29:10 -0400 Message-ID: <009401c7805d$82938bd0$6601a8c0@tyan2400> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0095_01C7803B.FB81EBD0" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: <1176751228.4913.25.camel@burns> Thread-Index: AceAXFjjKvMJT+93RaK66+PNRfgdIQAAOrNQ X-Virus-Checked: Checked by ClamAV on apache.org ------=_NextPart_000_0095_01C7803B.FB81EBD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I guess the question then is what does this mean, is OpenJPA (not) doing something due to this? You see I have another error that is not representative of some real problem that I am trying to determine and I am looking to clear away the noise. _____ From: Hans J. Prueller [mailto:hans.prueller@gmx.net] Sent: April 16, 2007 3:20 PM To: open-jpa-dev@incubator.apache.org Cc: jacek@laskowski.net.pl Subject: Re: Duplicate query Phill, I am still getting the same warning - although I am using a 0.9.7-snapshot that is some weeks old meanwhile: 160 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.Runtime - Starting OpenJPA 0.9.7-incubating-SNAPSHOT 363 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.jdbc.JDBC - OpenJPA will now connect to the database to attempt to determine what type of database dictionary to use. To prevent this connection in the future, set your openjpa.jdbc.DBDictionary configuration property to the appropriate value for your database (see the documentation for available values). 449 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.MySQLDictionary" (MySQL 5.0.24a-Debian_9ubuntu2-log ,MySQL-AB JDBC Driver mysql-connector-java-5.0.4 ( $Date: 2006-10-19 17:47:48 +0200 (Thu, 19 Oct 2006) $, $Revision: 5908 $ )). 2180 lbsims WARN [RMI TCP Connection(3)-127.0.1.1] openjpa.MetaData - Found duplicate query "PositionLog.byId" in "class com.lbslogics.ims.model.PositionLog". Ignoring. As you can see, I'm prefixing the query names with the Pojo-name to avoid duplicate names but nevertheless, the warning comes up... Hans Am Montag, den 16.04.2007, 15:11 -0400 schrieb Phill Moran: I am still getting a duplicate query where no duplicate exists. Did this get resolved in the 0.97 release or may this be a config issue on my part? Phill ------=_NextPart_000_0095_01C7803B.FB81EBD0--