Upper case for table and column name

2008-05-07 Thread Frank Schwarz
Hi, how do I have to configure OpenJPA (1.0.2) to generate upper case names for tables and columns when no table/column name is specified in the JPA mapping? value="oracle(SchemaCase=SCHEMA_CASE_UPPER)" /> does not do the trick (at least regarding logging and schema generation). Kind regar

RE: Synchronizing two databases with the same model

2008-05-07 Thread Brill Pappin
I haven't really been following the thread, but... I just thought of an old project that might still be active... Something called CJDBC which was an early attempt to provide a driver level replication, cluster and fail-over feature. If it's still around, it might be able do your replication. A

Re: Synchronizing two databases with the same model

2008-05-07 Thread Pinaki Poddar
Hi Jonas, Just finished a prototype that specializes Slice to migrate selected instances from one database to another. But I am not planning to commit it to trunk right now (mainly because the trick that made it work will require a single line but dangerous change in OpenJPA :) -- if you are int

Re: update always called on commits (still)

2008-05-07 Thread Tedman Leung
I did read some where that the Tomcat classloader may be preventing runtime enhancments to the classes, so it may not necessarily be different code but it might be the fall back mentioned in section 5.2.4, so even though I thought I was getting byte code enhancement with jdk1.6, I wasn't and I

Re: update always called on commits (still)

2008-05-07 Thread Adam Hardy
A question to the OpenJPA developers: regarding different types of byte code enhancement and the disparity in functionality between them, does this reflect a seperate code base for enhanced versus non-enhanced OpenJPA? Tedman Leung on 07/05/08 22:01, wrote: I eventually did compile time enhan

Re: update always called on commits (still)

2008-05-07 Thread Tedman Leung
I eventually did compile time enhancement (as the agent was way too problemmatic) and yeah all my problems went away. Thanks for the info. On Wed, May 07, 2008 at 11:35:55AM -0700, Tedman Leung wrote: > Well according to the documentation "unenhanced" will become enhanced at > runtime via "Dep

Re: Synchronizing two databases with the same model

2008-05-07 Thread Jonas Petersen
Hi Pinaki, thank you, this sounds interesting. The Slice Plig-In looks quite promising, I'm definitely interested in learning more about this. Jonas Pinaki Poddar schrieb: Hi, The most obvious approach would be: fetch objects from datastore A (and possibly detach the objects) and then me

Re: Synchronizing two databases with the same model

2008-05-07 Thread Pinaki Poddar
Hi, > The most obvious approach would be: fetch objects from datastore A (and > possibly detach the objects) and then merge them in database B. But this > rises a couple of problems due to versioning / sequence generators / > optimistic locking / ... Another alternative approach is to consid

Re: update always called on commits (still)

2008-05-07 Thread Tedman Leung
Well according to the documentation "unenhanced" will become enhanced at runtime via "Deploy-time enhancement", "Java 6 class retransformation", "Java 5 class redefinition". I think what I was getting from Michael's posting is that the automatic enhancement #3 has issues so right now I'm trying

Re: update always called on commits (still)

2008-05-07 Thread Andy Schlaikjer
Just to clarify, I believe there are three possible enhancement scenarios: 1. build-time enhancement - running org.apache.openjpa.enhance.PCEnhancer over your bytecode before you run your app. 2. runtime enhancement - giving the "-javaagent=openjpa.jar" argument to the JVM when you run your

Re: update always called on commits (still)

2008-05-07 Thread Tedman Leung
well, yes I'm running int "unenhanced" or in "runtime enhancement", however, I thought at was a valid way of running the system. I didn't find any documentation saying not to use that mode and it was much more "convenient" so I chose that route. On Wed, May 07, 2008 at 07:30:49PM +0200, Micha

RE: update always called on commits (still)

2008-05-07 Thread Michael Vorburger
I'm sure it's not that simple, but you aren't maybe by chance not using enhancement (build or that -javaagent) and relying on the OpenJPA feature that allows to run even unenhanced in some kind of degraded mode (there is a log at the beginning if you're in that mode), and we noticed that "change tr

RE: One-Sided One-Many Mapping, but to different tables - missing @ElementEmbeddedMapping ?

2008-05-07 Thread Michael Vorburger
Hello, my last phrase "are there any plans" was actually a question, no response... really no comment? This is unfortunately turning into a show stopper for our use of OpenJPA, and we probably have to have a look at another ORM ;-( which seems to support this kind of mapping... whine whine, hope h

update always called on commits (still)

2008-05-07 Thread Tedman Leung
Hi while back we had a discussion on updates (or more specifically preupdates) always being called even when no changes where made. I noticed there was an issue OPENJPA-506 openned for this and currently closed - but this still occurs. Both anotated @PreUpdate methods as well as updates are alw

Re: maintaining bi-directional relationships

2008-05-07 Thread Adam Hardy
Oh sorry, I should have said, the app must be JPA-compliant / portable. Michael Vorburger on 07/05/08 17:44, wrote: Why not use OpenJPA Managed Inverses, http://openjpa.apache.org/docs/latest/manual/ref_guide_inverses.html ? -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED]

RE: maintaining bi-directional relationships

2008-05-07 Thread Michael Vorburger
Why not use OpenJPA Managed Inverses, http://openjpa.apache.org/docs/latest/manual/ref_guide_inverses.html ? -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: mercredi, 7. mai 2008 17:51 To: users@openjpa.apache.org Subject: maintaining bi-directional relationships Thi

maintaining bi-directional relationships

2008-05-07 Thread Adam Hardy
This is a design question really, sorry it's a little OT. I assume I have responsibility for maintaining parent - child relationships reflected by the parent.getChildren collection and child.getParent entity at the point where the change occurs. Is there a good pattern to implement changes to

Re: General restrictions

2008-05-07 Thread Adam Hardy
alex_ro_bv on 07/05/08 10:39, wrote: Hi all, I was wondering if there is possible a general restriction for my database using openJPA. What I mean is that in my database all my tables have some common fields. For example deletedflag. So I was wondering if is there any way to exclude all these rec

General restrictions

2008-05-07 Thread alex_ro_bv
Hi all, I was wondering if there is possible a general restriction for my database using openJPA. What I mean is that in my database all my tables have some common fields. For example deletedflag. So I was wondering if is there any way to exclude all these records in my business logic somehow. So