On 4/18/07, Jonathan Feinberg <[EMAIL PROTECTED]> wrote:
When SychronizeMappings is set to buildSchema, as it always is for me (in head-down development mode), every run of unit tests or app server is prefaced by a large collection of spurious warnings. A specimen: 3635 myproj WARN [http-8080-Processor24] openjpa.jdbc.Schema - Existing column "id" on table "public.share" is incompatible with the same column in the given schema definition. Existing column: Full Name: share.id Type: char Size: 32 Default: null Not Null: true Given column: Full Name: Share.id Type: varchar Size: 255 Default: null Not Null: true
What database are you using? Have you tried to run it against another db? I suspect it might be related to the db. Could you try out the following setting in your persistence.xml: <property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema(SchemaAction='add,deleteTableContents')" /> ? What's the result? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
