: Marc Prud\'hommeaux [EMAIL PROTECTED]
An: open-jpa-dev@incubator.apache.org
Betreff: Re: Duplicate Query - where none exists
How is the category.categoryTypeFK column defined in the database?
An is there a corresponding id column in the table for the
CategoryType class?
Also, when
Prud'hommeaux
Sent: April 5, 2007 2:42 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Duplicate Query - where none exists
How is the category.categoryTypeFK column defined in the database?
An is there a corresponding id column in the table for the CategoryType class?
Also, when there is just
Datum: Wed, 4 Apr 2007 23:42:01 -0700
Von: Marc Prud\'hommeaux [EMAIL PROTECTED]
An: open-jpa-dev@incubator.apache.org
Betreff: Re: Duplicate Query - where none exists
How is the category.categoryTypeFK column defined in the database?
An is there a corresponding id column in the table
again
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On
Behalf Of Marc
Prud'hommeaux
Sent: April 5, 2007 2:42 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Duplicate Query - where none exists
How is the category.categoryTypeFK column defined
I am using 0.9.6. I will see how to package this up so you can step through
_
From: Hans J. Prueller [mailto:[EMAIL PROTECTED]
Sent: April 4, 2007 10:28 AM
To: open-jpa-dev@incubator.apache.org
Subject: RE: Duplicate Query - where none exists
I also encountered a similar problem
I think I saw this once. The problem is in JPA named queries are all
contained in a single global namespace, so if you have to persistent
beans that define queries with the same name you get a warning. It
would be nice if the warning told you where the duplicate
declarations are located.
Sundstrom [mailto:[EMAIL PROTECTED]
Sent: April 4, 2007 5:06 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Duplicate Query - where none exists
I think I saw this once. The problem is in JPA named queries are all contained
in a single global namespace, so if you have to persistent beans
: Re: Duplicate Query - where none exists
I think I saw this once. The problem is in JPA named queries are
all contained
in a single global namespace, so if you have to persistent beans
that define
queries with the same name you get a warning. It would be nice if
the warning
told you where
To: open-jpa-dev@incubator.apache.org
Subject: Re: Duplicate Query - where none exists
Phill-
While I'm not sure the cause of the duplicate query error, I do notice the
original cause in the nested stack trace is:
Caused by: 4|true|0.0.0
org.apache.openjpa.persistence.ArgumentException: You
