openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "KARR, DAVID (ATTCINW)" <dk0...@att.com>
Subject RE: Get nonsensical "column that is not compatible" error after replacing 1.2.1 with 1.2.2
Date Fri, 22 Jan 2010 17:27:31 GMT
> -----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
> 
> > -----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 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.
> 
> I'm going to see if I can get anywhere tracing this with the debugger.
> Do you have some suggestions for landmarks I should be looking for?

Hmm. That's annoying.  For some reason Eclipse won't stop at relevant
breakpoints to debug this.  I've never had trouble stepping through
third-party jar source code before.

Mime
View raw message