Daryl Stultz-2 wrote:
>
> On Fri, Jun 25, 2010 at 8:46 PM, Daniel Toffetti
> wrote:
>>
>>Some time ago I started a quest for a magic tool,
>>Thanks in advance for any useful tool or URL I might have missed.
>
> I don't know exactly what you are looking for, but if you haven't looked
> a
On Thu, Jun 24, 2010 at 1:45 PM, Matthew Adams wrote:
> Instead of a virtual entity, you could create the view and tell
> OpenJPA about the view via @JoinTable annotations...
>
> Matthew, I'm wondering if you can give a few more details here. It seems
pretty straightforward, yet OpenJPA is throwin
Oh Ok ... hmm I haven't used dropping because I like to keep the old
data/schema even I am not using it.
I just checked the manual regarding the mapping tool (this property uses)
and I think you need to change your action stuff. Check Pg 262 of the 1.2.x
manual (pdf version) . It looks like I d
Hi,
Joe I am not sure exactly what your question is, is it the "SchemaAction" or
is it more generally the SynchronizeMappings property?
Hm, i think the SchemaAction.
If i understand it correctly it leads to a dropping of all tables, and
after it to a recreation of the tables based on the en
Joe I am not sure exactly what your question is, is it the "SchemaAction" or
is it more generally the SynchronizeMappings property? Anyway, I use MaxDB
with this setting on 1.2.2 and 2.0 perfectly fine.
Always use build time enhancement or buy a lotto ticket instead!
Chris
-Original Mess
Hi,
For unit tests i like to set the following property in the
persistence.xml file:
value="buildSchema(SchemaAction='dropDB,add')" />
This works for Derby and Oracle but it doesn't work for MaxDB.
I looked at:
http://openjpa.apache.org/builds/1.0.2/apache-openjpa-1.0.2/docs/manual/ref_g
