Hi,
I'm getting an illegal SQL exception when working with OpenJPA
0.9.8-incubator-SNAPSHOT and PostgreSQL 8.2.3 with an persistent
attribute defined as follows:
@Column(precision = 7, scale = 3)
public BigDecimal getPensja() {
return pensja;
}
OpenJPA generates
pensja DOUBLE
I’m having the same exception. Strange is that the IDENTICAL codebase runs
without errors under Toplink JPA. I’ve only changed the provider and
properties in the persistence.xml and included the OpenJPA jars to the
project. (That is what JPA should be able to do, afterall.)
--
View this message
tbee wrote:
Jacek Laskowski-4 wrote:
So I read it that you're relying on the other mechanisms TopLink JPA
provides.
Ah, no, all classes are defined in the persistence.xml. In fact I turned
autodetection explicitely off when I was trying Hibernate (OpenJPA is
attempt 3); my
On 4/20/07, tbee [EMAIL PROTECTED] wrote:
Is it possible this has to do with the way I've setup the entity classes?
What I do is have an @Entity class without any fields and it extends a
@MappedSuperclass which is generated from the DB and where all the actual
fields are declared.
I've never
Jacek Laskowski-4 wrote:
So I read it that you're relying on the other mechanisms TopLink JPA
provides.
Ah, no, all classes are defined in the persistence.xml. In fact I turned
autodetection explicitely off when I was trying Hibernate (OpenJPA is
attempt 3); my persistent classes are
Have you checked with Spring/JUnit they support rollback during tests
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of David Van Couvering
Sent: April 20, 2007 1:46 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Help requested around rollback
OpenJPA People-
In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
, I've taken another shot at making a release and start a vote on publishing
a 0.9.7-incubating release of OpenJPA.
The release candidate is at:
tbee wrote:
Marina Vatkina wrote:
The spec defines the following limitations of a MappedSuperclass:
2.1.9.2 Mapped Superclasses
...
A mapped superclass, unlike an entity, is not queryable and cannot be
passed as
an argument to EntityManager or Query operations. A mapped superclass
cannot
How can you define relationships in the mapped superclass that are
*specified*
in terms of the entities?
Quite simple:
@Entity
class Article extends Article2
@MappedSuperclass
class Article2
@ManyToOne
private Manufacturer; // note: not Manufacturer2!!
You can always change the
+1
On Apr 20, 2007, at 12:41 PM, Michael Dick wrote:
OpenJPA People-
In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
, I've taken another shot at making a release and start a vote on
publishing
a
10 matches
Mail list logo
