Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of daxiezhi@gmail.com designates
 209.85.214.174 as permitted sender)
MIME-Version: 1.0
Date: Mon, 27 Aug 2012 22:10:48 +0800
Message-ID: 
 <CABS8Zpr=KRF6JB61hrCoyzCpsHYheXoChnQdhG0oFi0f+aCVhQ@mail.gmail.com>
Subject: Existing column XXX on table XXXX is incompatible with the same
 column in the given schema definition.
From: Zhi Xie <daxiezhi@gmail.com>
To: dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=f46d043c824a806d4504c83fe4ae

--f46d043c824a806d4504c83fe4ae
Content-Type: text/plain; charset=ISO-8859-1

I have met a problem using openjpa2.1.1.
I have defined a JoinTable "user_group" with a JoinColumn "uName", the
 uName is a column of Table user defined varchar(128). But there is not a
length attribute inJoinColumn. So the default value 255 is set on the
JoinColumn
uName.

My question is how to avoid the warning.

WARN  [Schema] Existing column "uName" on table "test.user_group" is
incompatible with the same column in the given schema definition. Existing
column:
Full Name: user_group.uName
Type: varchar
Size: 128
Default: null
Not Null: true
Given column:
Full Name: user_group.uName
Type: varchar
Size: 255
Default: null
Not Null: true

I want to find a solution to avoid the warning.
Could anybody give me any comment?
-- 
Best Regards
Gary

--f46d043c824a806d4504c83fe4ae--