Correction: the regression was introduced from 2.0.0-beta3 to 2.0.0.
Best,
Laird
On Mon, Nov 1, 2010 at 3:50 PM, Laird Nelson wrote:
> setInverseRelation, line 469.
>
> In version 2.0.0-beta3, this all worked fine.
>
> In version 2.0.1 any named query I create blows up with a stack like the
> f
setInverseRelation, line 469.
In version 2.0.0-beta3, this all worked fine.
In version 2.0.1 any named query I create blows up with a stack like the
following:
FailedObject: SELECT j FROM JournalEntry j WHERE j.status <> :voidedEntry
AND j.effectiveOn >= :beginOn AND j.effectiveOn <= :endOn AND
Hi Georgi,
A few of us were having some build issues this morning due to a dependency
update. The change was backed out and trunk is now building again. The
error you've posted doesn't look the same, but I'm doing an install vs.
package. I'd try doing a clean before package with the very latest
Hi all.
I have the following problems when i try to build OpenJPA from trunk:
1. After "mvn compile" execution the following error occurs :
[ERROR] BUILD ERROR
[INFO]
[INFO] An Ant BuildException has occured: The followin
I use openjpa 2.0. I havent included @version field in this example but I
tried that using a timestamp field but it didnt work as well. When I dont
use any of those according to documentation it says that value in @Id field
will be used to issue update or insert, but that is not happening in my
ca
Hi,
I think (haven't verified it) that you can use the base DBDictionary class -
this might be closer to MaxDB than Oracle or HSQL.
Which value i have to set for using the base DBDictionary class?
One other thing you / we can do is open a JIRA for supporting MaxDB, and we
can add a MaxDB di
