perhaps this can help out:
I just started using OpenJPA and I have ONLY A SINGLE CLASS WITHOUT ANY
RELATIONS where I get this duplicate-query warning. So I can't believe that its
related to that somehow...
Hans
Original-Nachricht
Datum: Wed, 4 Apr 2007 23:42:01 -0700
Von:
Pessimistic Lock Manager not locking the rows
--
Key: OPENJPA-203
URL: https://issues.apache.org/jira/browse/OPENJPA-203
Project: OpenJPA
Issue Type: Bug
Components: kernel
Affects
It is actually called categoryTypeFK and is char(45) related to ID, char(45) in
categoryType table.
I like the less is more but I remember getting some complaints in eclipse. I'll
try again
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On Behalf Of Marc
Hi Wanyna,
Whenever you query for entities, the result entities are put into
your persistence context. So when you then try to persist another
entity with the same identity the provider finds the query result in
the persistence context and throws EntityExistsException.
Craig
On Apr 4,
[
https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486987
]
Abe White commented on OPENJPA-182:
---
What is setting the isolation level this way actually doing? For anything
[
https://issues.apache.org/jira/browse/OPENJPA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486999
]
Abe White commented on OPENJPA-203:
---
Looks good. Although I think I'd prefer to make lockInternal() responsible
It has not been documented in the OPENJPA documentation.
On 4/4/07, Patrick Linskey (JIRA) [EMAIL PROTECTED] wrote:
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486820]
Patrick Linskey commented on
[
https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487046
]
Patrick Linskey commented on OPENJPA-182:
-
Hopefully, this will be useful for applications where there
[
https://issues.apache.org/jira/browse/OPENJPA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487070
]
Srinivasa commented on OPENJPA-203:
---
My initial approach was the same that we could move the responsibility of
Hans-
I just did a query test with the examples/hellojpa/Message.java class
in the latest openjpa-0.9.7-incubating-SNAPSHOT, and when I add:
@NamedQueries({
@NamedQuery(name=q1, query=select x from Message x),
@NamedQuery(name=q1, query=select x from Message x)
})
I get the
Hmm. I don't see anything wrong with that mapping. How is the
@OneToOne on the other side of the @ManyToOne defined (if you have one)?
It might be good to see the output of the mappingtool's validate
action on your classes. E.g.:
java org.apache.openjpa.jdbc.meta.MappingTool -action
[
https://issues.apache.org/jira/browse/OPENJPA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487078
]
Abe White commented on OPENJPA-203:
---
If we don't want the subclasses to have to unset the lock value in case of
We were unaware that fetch plan properties could be set as Hints. Now
that we look at the code we see this, but we did not find this when
we read the OpenJPA documentation.
Yeah, it seems like we should probably do some documentation of some of
these newer configuration options.
The only
[
https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487082
]
Craig Russell commented on OPENJPA-182:
---
I know that Oracle allows you to add a FOR UPDATE clause to a query,
[
https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487085
]
Abe White commented on OPENJPA-182:
---
I know that Oracle allows you to add a FOR UPDATE clause to a query, and
[
https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487086
]
Patrick Linskey commented on OPENJPA-182:
-
I know that Oracle allows you to add a FOR UPDATE clause
to
[
https://issues.apache.org/jira/browse/OPENJPA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-204.
-
Resolution: Won't Fix
This is a limitation of the JPA spec. From section 9.1.34:
But both of those settings are per-transaction things, not per-query
things. The DB2 isolation level syntax differs in that it is part of the
SQL statement issued, rather than a separate configuration for the
transaction-wide isolation level.
Theoretically, the JDBC transaction-level isolation
Hi,
Is it possible to annotate issues in JIRA with some sort of structured
or semi-structured tag? I'd like to be able to mark OPENJPA-204 so that
we can come back to it later when working on the next JPA specification
version. I guess I could clone the issue and either make a new issue
type or a
JPA2 Follow-Up
--
Key: OPENJPA-205
URL: https://issues.apache.org/jira/browse/OPENJPA-205
Project: OpenJPA
Issue Type: Improvement
Components: jpa
Reporter: Patrick Linskey
This is an umbrella issue for
Has there been any progress on this issue? I just came across a case
today where I'd like this functionality and some searching turned up
this thread. I don't see anything on this subject that is more
recent than the email below, but I'm not sure that I'm not just
looking in the wrong
[
https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487098
]
Michael Dick commented on OPENJPA-182:
--
I have no practical experience with Sybase, but I did find this in
I think I mentioned the wrong place but in SQLServer the isolation level can
be specified as a table hint. The Table hint specifies that the query
optimizer use a table scan, one or more indexes, or a locking method with
this table or view and for this SELECT, INSERT, UPDATE, or DELETE statement.
[
https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487099
]
Patrick Linskey commented on OPENJPA-182:
-
Between Ritika's SQLServer email on the dev list and Mike's
George-
I'm not sure the exact problem (your model looks OK to me at first
glance), but FTR, I just tried a simple test with a query that
returns ob, ob.someOneToOne, and it returned the expected values
(in this case, a
org.apache.openjpa.persistence.models.company.basic.Customer and
Surely you are right. The object to persist is just in the result of query.
I'v made a mistake in my test case 2, I did not notice some relations.
Thanks.
Craig L Russell wrote:
Hi Wanyna,
Whenever you query for entities, the result entities are put into
your persistence context. So
26 matches
Mail list logo
