openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Bayer (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1760) Should deleteTableContents always delete really ALL content?
Date Wed, 11 Aug 2010 19:28:16 GMT


Oliver Bayer commented on OPENJPA-1760:

Hi Rick,

first of all, sorry for the late reply.

In the last couple of days I tried to get into writing junit tests but atm I don't have the
time to get used to it and write an useful testcase for you to reproduce the problem. So I've
coded some console application where openjpa behaves the way it should.

But in my jsf application running in tomcat it always delets all table contents. Therefor
I started some debugging session today.

1) console app: Schema[] schemas (line 421) contains only one scheme named "null".
2) tomcat app: Schema[] schemas (line 421) contains two schemes named "null" and "public".

Null seems to be the correct scheme whereas public always contains all available tables.
Do you know if this occurs because of a misconfiguration or an another error I made?

Regards Oli

> Should deleteTableContents always delete really ALL content?
> ------------------------------------------------------------
>                 Key: OPENJPA-1760
>                 URL:
>             Project: OpenJPA
>          Issue Type: Question
>    Affects Versions: 2.0.0
>         Environment: Win XP, Postgres 8.4, OpenJPA 2.0.0 
>            Reporter: Oliver Bayer
> At my usecase not all tables are managed by openjpa so not all of them are listed with
the class-tag inside persistence.xml. I set up openjpa to delete the table contents for developping
with the following property:
> <property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema(SchemaAction='add,deleteTableContents')"/>
> But now all contents are deleted even the one of tables which aren't listed inside persistence.xml.

> Shouldn't openjpa only delete contents from tables which are configured plus the openjpa_sequence_table
rather than deleting all contents from the whole database? Is this a bug or is there a property
which I have to set to get the described behaviour?
> Greets Oli

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message