@Version property doesn't ensure integrity when performing the merge operation
--
Key: OPENJPA-197
URL: https://issues.apache.org/jira/browse/OPENJPA-197
Project: OpenJPA
Is this something we can put in 0.9.7 or has that been cut already?
-dain
On Apr 1, 2007, at 10:07 PM, Craig L Russell wrote:
+1 to remove the restriction. As long as no parameters are missing,
the query should be considered sufficient.
Craig
On Apr 1, 2007, at 9:30 AM, Marc Prud'hommeaux
So, Jacek Laskowski is unable to send emails to the dev list. I don't
recall seeing any moderation messages.
Craig
Begin forwarded message:
BTW, I'm still unable to send emails to open-jpa-dev. Who should I
contact to in order to fix it?
Jacek Laskowski
Craig Russell
Architect, Sun Java
I don't think that it's been cut yet. Mike: where do we stand on the
0.9.7 process?
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486065
]
Patrick Linskey commented on OPENJPA-197:
-
I'm a bit confused. Where did Hibernate and Toplink fail? The
I'm using 0.9.6 on hsqldb and am getting exceptions like this
periodically:
0|false|0.9.6-incubating
org.apache.openjpa.persistence.PersistenceException: Index already
exists: I_BNJBBTB_A1 in statement [CREATE INDEX I_BNJBBTB_A1 ON
BEANEJB_MXM_UNI_BTOB] {stmnt 7870505 CREATE INDEX
Are you able to reproduce this in any fashion? It'd be interesting to
figure out why OpenJPA was attempting to recreate the indexes.
There are a couple of ways to get around the error:
- set the IgnoreErrors MappingTool flag to true. This will cause any
errors during schema synchronization to be
Note that I don't think OpenJPA reads index names from the existing
schema by default, so if you're adding fields or classes these might
be plain old naming conflicts due to truncation based on database
name length limits. There is a readSchema option on the mapping tool
that forces it to
say i have Library, Book, and Page classes. a Library has many Books, and a
Book has many Pages. A Library's ID is it's name (simple). A Book's ID is a
composite of it's name and it's owning Library's name (bidirectional
relationship). A Page's ID is a composite of it's number and it's owning
Is there support of InverseManager for JDO?, as the documentation shows just
the examples in JPA.
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486087
]
Jacek Laskowski commented on OPENJPA-197:
-
Hibernate and TopLink will fail once you get rid of the if
Maybe I'm on crack, but
openjpa.jdbc.SynchronizeMappings=buildSchema(Indexes=false)
has no effect on 0.9.6 as I still see the CREATE INDEX statements
in the log. I am confident that my properties are being inspected
because when I set buildSchema(ForeignKeys=true, Indexes=false,
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486089
]
Jacek Laskowski commented on OPENJPA-197:
-
As I'm unable to write to the dev mailing list I'm responding to
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486091
]
Patrick Linskey commented on OPENJPA-197:
-
Note that there are significant performance impacts to doing
On 4/2/07, Patrick Linskey [EMAIL PROTECTED] wrote:
I have no problem adding this to the release. I was hoping to get
OpenJPA-185 and OpenJPA-179 in as soon as I got commit
access, and then start the release process.
You should have commit access now.
Is there anything else that we need
Hi Mike,
You have god-like powers in Jira (group jira-administrator). You have
the ability to do anything you want.
Go to the administration page for OpenJPA. Click on manage versions;
add a version.
Craig
On Apr 2, 2007, at 11:47 AM, Michael Dick wrote:
On 4/2/07, Patrick Linskey
How do I create a goal in JIRA? I don't seem to have access
to do so, but
I'm using the same ID that I had before I became a committer.
It happens to
be the same username as my Apache account, is there something
I need to do
to link them?
I just added you to the openjpa-developers JIRA
Hibernate and TopLink will fail once you get rid of the if
statement. It's because according to the spec (and my
understanding) merge should rise exception when the versioned
property is outdated.
No, the exception can be deferred until flush/commit. Read section
3.2.4.1.
Notice:
[
https://issues.apache.org/jira/browse/OPENJPA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reassigned OPENJPA-185:
Assignee: Michael Dick
optional attribute is not overriden by xml descriptor
I downloaded the openjpa 0.9.7 nightly build to replace my current 0.9.6
version. After that, all my unit tests failed with the following exception:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'entityManagerFactory' defined in class path resource
Hi Jeff,
The pattern you use for Book/Library is
public class BookId implements Serializable {
private String name;
private String library;
The pattern you use for Page/Book is
public class PageId implements Serializable {
private int number;
private BookId book;
Have you
Hello Jeff,
OpenJPA supports the cited example where Page using a composite ID which
in turn refers to Book's composite ID.
Book/Page/Library classes work with
a) openjpa-0.9.7 (do not know whether observed errors are due to usage
of earlier 0.9.6 version)
b) following modifications in
On Apr 2, 2007, at 11:18 AM, Abe White wrote:
The spec says in 3.2.4.1 p. 52: Any Version columns used by the
entity must be checked by the persistence runtime implementation
during the merge operation and/or at flush or commit time.
So, one could agree with Abe (the and/or is the key).
Ok.
hi craig, thanks ...
your suggestion would imply that that BookId can be converted to and from a
String object, right? i checked the spec, and i expected to find a requirement
to have a toString() method and a string constructor that can work in unison to
this end, but it's not there. maybe i
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486112
]
Jacek Laskowski commented on OPENJPA-197:
-
Please close the issue with WON'T FIX or alike due to the
[
https://issues.apache.org/jira/browse/OPENJPA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abe White closed OPENJPA-197.
-
Resolution: Invalid
@Version property doesn't ensure integrity when performing the merge operation
Actually, I don't think that he does anymore... I granted him
jira-administrators briefly, and then discovered the Project Roles
business, so removed the jira-administrators bits.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
I checked the 0.9.7 openjpa.jar and found ProxyArrayList,
ProxyHashSet,
ProxyHashMap are all missing. Is this a problem with 0.9.7 build?
Not as such -- those classes are no longer part of the OpenJPA
distribution. OpenJPA now does collection and map proxying through
different means.
Can
thanks pinaki,
after making those changes, on 0.9.6, i get:
Caused by: java.lang.ClassCastException: org.apache.openjpa.util.ObjectId
at com.mycompany.book.Page.pcCopyKeyFieldsToObjectId(Page.java)
at
org.apache.openjpa.util.ApplicationIds.create(ApplicationIds.java:383)
[
https://issues.apache.org/jira/browse/OPENJPA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-185.
--
Resolution: Fixed
optional attribute is not overriden by xml descriptor
Dain-
On Apr 2, 2007, at 12:23 PM, Dain Sundstrom wrote:
Is this something we can put in 0.9.7 or has that been cut already?
I've gone ahead and committed the fix for this.
-dain
On Apr 1, 2007, at 10:07 PM, Craig L Russell wrote:
+1 to remove the restriction. As long as no parameters
[
https://issues.apache.org/jira/browse/OPENJPA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-196.
Resolution: Fixed
Fix Version/s: 0.9.7
Ease the restrictions on forcing a
Hi Mike,
On Apr 2, 2007, at 3:16 PM, Michael Dick wrote:
Earlier today I created the 0.9.8 release in JIRA, and moved most
of the
open issues from 0.9.7 to 0.9.8.
There's one open issue against 0.9.7 - OpenJPA-179 and I'll submit
a fix for
that later tonight (or move it to 0.9.8). Marc
[
https://issues.apache.org/jira/browse/OPENJPA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-57.
Resolution: Won't Fix
Fix Version/s: (was: 0.9.8)
0.9.7
If
okay, by chance i looked at the open jpa pom and saw that it calls out surefire
2.2 w/ some particular options. sure enough, that fixed the classpath problem.
however, i still get the exception w/ regard to ObjectId after making the
changes you suggested ...
Caused by:
Hi Jacek,
I'm not moderating this list (yet). I'll let you know when to try again.
Craig
On Apr 2, 2007, at 1:00 PM, Jacek Laskowski wrote:
Hopefully, it passes the gates.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Craig Russell
Architect, Sun Java Enterprise System
after doing some decompilation, the problem line is ...
PageId pageid = (PageId)((ObjectId)obj).getId();
in the enhanced Page class. so, looking at PageId, it's not an instance of
ObjectId. so, i am not sure what is supposed to be happening here. i assume
that PageId is supposed to be
I have the following query:
SELECT a.alias FROM AliasBean AS a WHERE (a.alias IS NULL AND ?1 IS
NULL) OR a.alias = ?1
Which works great when run against HSQLDB. When I switch the
database to Derby I get the following exception:
0|false|0.9.6-incubating
Marc,
All my experiments are just that - experiments. My goal is to enable DDL
generation in GlassFish when the persistence provider is set to that of the
OpenJPA and the user-visible behavior is similar to the one we have for CMP
(i.e. our internal code) and for TopLink Essentials as the
Jeff,
1. The errors look rather unrelated to original problem of composite
id.
2. The errors apparently caused by enviroment setup, so please
a) get a clean 0.9.7 openjpa (either building locally from the
source, or pre-built jars from the openjpa web-site)
b) if the error
Finish fix for persistence-unit-defaults
Key: OPENJPA-198
URL: https://issues.apache.org/jira/browse/OPENJPA-198
Project: OpenJPA
Issue Type: Sub-task
Affects Versions: 0.9.8
[
https://issues.apache.org/jira/browse/OPENJPA-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-179.
--
Resolution: Fixed
Fixed with revision 525006.
Schemas defined in orm.xml are only applied
Hi Dain,
I've seen this problem as well, with a different provider. The JPA
spec lead sez that ?1 IS NULL is not a portable JPAQL query, even
though some providers can generate SQL that some databases can
execute properly.
It might not be an easy issue for OpenJPA to fix. How easy is it
On Apr 2, 2007, at 8:06 PM, Craig L Russell wrote:
Hi Dain,
I've seen this problem as well, with a different provider. The JPA
spec lead sez that ?1 IS NULL is not a portable JPAQL query, even
though some providers can generate SQL that some databases can
execute properly.
OpenJPA is
Dain-
Also, I'm using 0.9.6 so is this a known problem?
I have a very hazy recollection of this being something that was
fixed recently, but a quick search through JIRA doesn't reveal anything.
Could you try it out against the latest 0.9.7-incubating-SNAPSHOT and
let us know if still
All too easy, thank you both!
I just added the files. Release-notes and Changes came mostly from JIRA.
Building.txt was stolen from the building OpenJPA page (credit there should
go to Marc).
On 4/2/07, Marc Prud'hommeaux [EMAIL PROTECTED] wrote:
Besides the issues mentioned above I think
46 matches
Mail list logo
