Cool,
Thanks for the info, I wasn't aware that you could do that!
> -Original Message-
> From: Drew Lethbridge [mailto:[EMAIL PROTECTED]
> Sent: Friday 2 May 2008 15:34
> To: users@openjpa.apache.org
> Subject: Re: java.util.Data mapping to abstime (deprecated) in
postgres
>
> No worri
No worries mate. You don't need to modify openjpa (in this case),
it's designed to allow you to plug in your own classes, which live
inside your own jar files, by specifying your plug-ins in the
properties. Other than my DBDictionaries (I have plugged in separate
DBDic for Oracle, Postgre
Hi Drew, thanks for your suggestion, I had thought of that but didn't
want to go modifying weblogic's distribution of openjpa.
> -Original Message-
> From: Drew Lethbridge [mailto:[EMAIL PROTECTED]
> Sent: Friday 2 May 2008 14:13
> To: users@openjpa.apache.org
> Subject: Re: java.util.D
Hi Daniel. I also had your problem and fixed it by implementing my
own DBDictionary (subclass of PostgresDictionary) and plugging it in
using the kodo.jdbc.DBDictionary configuration setting... Below is an
sample of my dbdictionary which might be helpful...
cheers!
.droo.
public class M
Hi all,
I am using BEA Weblogic 10, which implements persistence by using kodo
and openjpa.
I have set this up to persist to a Postgres 8.3 Database.
I have a java.util.Date that I want as a column in a table.
When I run the mapping tool, it maps the java.util.Data datatype to
Postgres
Adam Hardy on 01/05/08 17:48, wrote:
Adam Hardy on 30/04/08 21:22, wrote:
If I am running JPA in extended persistence context, when I call
EntityManager.merge() within a transaction and then commit the
transaction, should it or shouldn't it execute the SQL?
I assumed that it would but I have
Adam Hardy on 30/04/08 21:22, wrote:
If I am running JPA in extended persistence context, when I call
EntityManager.merge() within a transaction and then commit the
transaction, should it or shouldn't it execute the SQL?
I assumed that it would but I have a situation where it won't unless I
c
Jonas,
I'm glad you asked this question as I'd also been thinking about how I
might get around restrictions the @GeneratedValue annotation enforces
within OpenJPA.
In certain circumstances I need to specify the value of a field marked
with @GeneratedValue explicitly when persisting a new ent
