> -Original Message-
> From: Rick Curtis [mailto:curti...@gmail.com]
> Sent: Tuesday, January 26, 2010 9:34 AM
> To: users@openjpa.apache.org
> Subject: Re: Get nonsensical "column that is not compatible" error
> after replacing 1.2.1 with 1.2.2
>
> Go
anuary 22, 2010 9:41 AM
> > To: users@openjpa.apache.org
> > Subject: Re: Get nonsensical "column that is not compatible" error
> > after replacing 1.2.1 with 1.2.2
> >
> > David -
> >
> > I looked at the files that you uploaded and I'm somewhat co
> -Original Message-
> From: Rick Curtis [mailto:curti...@gmail.com]
> Sent: Friday, January 22, 2010 9:41 AM
> To: users@openjpa.apache.org
> Subject: Re: Get nonsensical "column that is not compatible" error
> after replacing 1.2.1 with 1.2.2
>
> David
> -Original Message-
> From: Rick Curtis [mailto:curti...@gmail.com]
> Sent: Friday, January 22, 2010 9:41 AM
> To: users@openjpa.apache.org
> Subject: Re: Get nonsensical "column that is not compatible" error
> after replacing 1.2.1 with 1.2.2
>
> David
> -Original Message-
> From: Rick Curtis [mailto:curti...@gmail.com]
> Sent: Friday, January 22, 2010 9:41 AM
> To: users@openjpa.apache.org
> Subject: Re: Get nonsensical "column that is not compatible" error
> after replacing 1.2.1 with 1.2.2
>
> David
David -
I looked at the files that you uploaded and I'm somewhat confused... it
appears that the trace is from when you ran the enhancer, not when you ran
the actual test case. By any chance can you boil this down to a simple unit
test that I can use to recreate on my system?
Thanks,
Rick
On Fri
> -Original Message-
> From: KARR, DAVID (ATTCINW)
> Sent: Friday, January 22, 2010 6:57 AM
> To: users@openjpa.apache.org
> Subject: RE: Get nonsensical "column that is not compatible" error
> after replacing 1.2.1 with 1.2.2
>
> > -Origin
> -Original Message-
> From: Rick Curtis [mailto:curti...@gmail.com]
> Sent: Friday, January 22, 2010 7:02 AM
> To: users@openjpa.apache.org
> Subject: RE: Get nonsensical "column that is not compatible" error
> after replacing 1.2.1 with 1.2.2
>
> KARR,
KARR, DAVID (ATTCINW) wrote:
>
> No. I never have. I only list the orm.xml files.
>
Can you try listing your persistent types in the p.xml file to see if this
problem goes away? If that doesn't work, can you turn on trace and post it
to filebin so I can take a look at it?
Thanks,
Rick
--
> -Original Message-
> From: KARR, DAVID (ATTCINW)
> Sent: Thursday, January 21, 2010 1:43 PM
> To: users@openjpa.apache.org
> Subject: Get nonsensical "column that is not compatible" error after
> replacing 1.2.1 with 1.2.2
>
> After replacing 1.2.1 with
> -Original Message-
> From: Rick Curtis [mailto:curti...@gmail.com]
> Sent: Thursday, January 21, 2010 1:50 PM
> To: users@openjpa.apache.org
> Subject: Re: Get nonsensical "column that is not compatible" error
> after replacing 1.2.1 with 1.2.2
>
> Are
Are you listing your persistent types in the p.xml file?
On Thu, Jan 21, 2010 at 3:43 PM, KARR, DAVID (ATTCINW) wrote:
> After replacing 1.2.1 with 1.2.2 and turning on the metadata preload, I
> got a nonsensical "column that is not compatible" error. I then tried
> removing the preload setting,
After replacing 1.2.1 with 1.2.2 and turning on the metadata preload, I
got a nonsensical "column that is not compatible" error. I then tried
removing the preload setting, and it's fine. I set it back, and it
failed again, so it's repeatable.
The relevant part of the stack trace is this (some pi
13 matches
Mail list logo
