Isn't type timestamp a long value?
- Brill Pappin
-Original Message-
From: David Goodenough [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 4:46 PM
To: users@openjpa.apache.org
Subject: Problem with Postgresql TIMESTAMP objects
In my application I am using an @Version field wh
Hi there,
I've had some issues with classpaths and the openjpac ant task as well.
The following ticket talks about these, as well as a work-around I'd found:
https://issues.apache.org/jira/browse/OPENJPA-482
Cheers,
Andy
Łukasz Budnik wrote:
Hi All,
I'm getting very strange exception:
C:\
In my application I am using an @Version field which is a timestamp.
I declare is (in Basic for those following the saga)
@Version @Temporal(TemporalType.TIMESTAMP) private Date version;
(and that is a java.util.Date, not a java.sql.Date).
But when loading the metadata for the classes it says:-
Hi,
EntityManager.getReference() is your friend here.
-Patrick
On Thu, Apr 3, 2008 at 4:19 AM, Ognjen Blagojevic <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Is there a way to persist an Entity without loading all the referenced
> objects?
>
> I know that this is possible:
>
> Employee e = new Em
I thought that I might give today's 1.1.0 snapshot a go, just to see
if the problem had been fixed along the way.
Well it found a problem, but only when I debugged my way through
the code using Eclipse. The normal enhancer seems to suppress
such messages, but stepping through I found a message to
On Thursday 03 April 2008, David Goodenough wrote:
> On Wednesday 02 April 2008, David Goodenough wrote:
> > On Wednesday 02 April 2008, Patrick Linskey wrote:
> > > Hi,
> > >
> > > Can you post the full stack trace?
> > >
> > > -Patrick
> > >
> > > On Wed, Apr 2, 2008 at 7:59 AM, David Goodenough
So I guess no one uses OpenJPA in web applications?
Only thing I wanted were some snipplets showing how you did transactions
etc in a web application.
regards Nino
Nino Saturnino Martinez Vazquez Wael wrote:
Hi
I wonder what best practices are on persistence context when running
in a web
Hi all,
Is there a way to persist an Entity without loading all the referenced
objects?
I know that this is possible:
Employee e = new Employe();
e.setName("John Doe");
e.setIdDepartment(findDepartmentByPrimaryKey(idDept));
e.setIdRank(findRankByPrimaryKey(idRank));
// and so on
em.persist(e)
On Wednesday 02 April 2008, David Goodenough wrote:
> On Wednesday 02 April 2008, Patrick Linskey wrote:
> > Hi,
> >
> > Can you post the full stack trace?
> >
> > -Patrick
> >
> > On Wed, Apr 2, 2008 at 7:59 AM, David Goodenough
> >
> > <[EMAIL PROTECTED]> wrote:
> > > On Wednesday 02 April 2008,
