openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Curtis <curti...@gmail.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 15:01:45 GMT


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

-- 
View this message in context: http://n2.nabble.com/Get-nonsensical-column-that-is-not-compatible-error-after-replacing-1-2-1-with-1-2-2-tp4436564p4440466.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Mime
View raw message