That's not a spec API, so we can change it / augment it as we see fit.
I don't see any reason not to just change that code as you described.
-Patrick
On Thu, Apr 3, 2008 at 10:44 AM, <[EMAIL PROTECTED]> wrote:
>
> The EntitymanagerFactoryImpl.getStoreCache(String cacheName) . This method
> cal
Primary key sequences broken with postgres schemas
--
Key: OPENJPA-557
URL: https://issues.apache.org/jira/browse/OPENJPA-557
Project: OpenJPA
Issue Type: Bug
Components: jdbc
Aff
[
https://issues.apache.org/jira/browse/OPENJPA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585428#action_12585428
]
Roger Keays commented on OPENJPA-557:
-
Here is my patch for OpenJPA 1.0.2. You might p
Performance difference between Oracle and Sql server of a factor 2 to 3
---
Key: OPENJPA-558
URL: https://issues.apache.org/jira/browse/OPENJPA-558
Project: OpenJPA
Issue Ty
[
https://issues.apache.org/jira/browse/OPENJPA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christiaan updated OPENJPA-558:
---
Attachment: Oracle Performance.zip
> Performance difference between Oracle and Sql server of a facto
Is there any plan to for JPA extend support beyond standard Java classes. As
far as I see there all metadata about persisten class use Class class. That
mean that there is no chance to use any dynamic objects like Eclipse EFM
(unlike you create static model for them) or Map. It would be great to
[
https://issues.apache.org/jira/browse/OPENJPA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585527#action_12585527
]
Michael Dick commented on OPENJPA-558:
--
Do you see the same behavior if you use JPA?
Just an FYI -
I have the same situation with openJPA1.0.2.
I solved it the same way you did. I was not sure it was a bug so did no
reported it.
F
"Andy Schlaikjer
OpenJPA typically uses an enhancer-added "detached state field" to
differentiate newly-constructed instances that need to be inserted vs.
detached instances that need to be updated on merge. This is covered in
more detail in the user manual.
OpenJPA also allows users with version fields to manual
Hi,
We (BEA) would like to get a 1.1.0 release underway so that we can
release off of the 1.1.x line for our upcoming WebLogic Server
release. Soo:
- Any objections to getting the process under way to make a 1.1.0 release?
- The first step is to do some JIRA issue triage work to figure out
w
java.rmi.MarshalException due to mismatched serialization UIDs of: Source
(RepId RMI:org.apache.openjpa.kernel.DetachedStateManager
---
Key: OPENJPA-559
Hi Abe,
I'm guilty of not updating 245 after I finished it. The scenario that got me
to look into it is the edge case you mentioned - the entity has no auto
generated fields.
Improving the story for other scenarios sounds good to me and I like the
approach.
My main concern is that we don't break
On Fri, Apr 4, 2008 at 12:22 PM, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> We (BEA) would like to get a 1.1.0 release underway so that we can
> release off of the 1.1.x line for our upcoming WebLogic Server
> release. Soo:
>
> - Any objections to getting the process under way to make a
[
https://issues.apache.org/jira/browse/OPENJPA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Albert Lee resolved OPENJPA-559.
Resolution: Fixed
> java.rmi.MarshalException due to mismatched serialization UIDs of: Source
> (
That's right, that the code here (transformToVersionSafePCDatas) should call
cache.containsAll() or cache.getAll(). That way, it will save a lot for any
data cache that provide getAll(). It won't gain much for OpanJPA "native"
data cache since it is delegated to AbstractDataCache.getAll() (ln. 44
[
https://issues.apache.org/jira/browse/OPENJPA-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Albert Lee resolved OPENJPA-552.
Resolution: Fixed
> Do not recognize Connection* properties in persistence.xml in appl server
> c
Here's another option that might suit everyone:
- We change the enhancement so that a non-default auto-assigned pk field
makes an instance detached even in the absence of detached state, as I
proposed.
- If the entity doesn't use auto-assigned pk fields (and has no version
field) and detached stat
[
https://issues.apache.org/jira/browse/OPENJPA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Catalina Wei reassigned OPENJPA-547:
Assignee: Catalina Wei
> INNER JOIN Fetch query incorrectly generates LEFT join SQL
> ---
The latest snapshot should have this behavior now.
> It won't gain much for OpanJPA "native"
> data cache since it is delegated to AbstractDataCache.getAll() (ln. 449)
> which loops thru the list to get the objects from the cache. However, it
> save the traffic if any.
Also, the built-in dat
(I left the issue open since the current behavior inefficiently copies
a Collection into a List; once we figure out whether or not we can
change that signature, we can resolve this issue.)
-Patrick
On Fri, Apr 4, 2008 at 2:18 PM, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> The latest snapshot sh
It is still a good practice because, for the third party data cache plugins
which support special getAll() API to batch the get function may benefit a
lot from the implementation, especially in the cluster environment.
On Fri, Apr 4, 2008 at 2:18 PM, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> T
The reason I raised that point was becuase I am using a Coherence cache.
And I am implementing the getAll - putAll method etc... into a brand new
plugin for OpenJPA.
But I think that for anyone else that create an OpenJPA plugin for their
favorite cache product - this would give them the ability t
alleluia
I am running Coherence clusters. OpenJPA needs to do the right thing when
it comes to interacting with a cache. Otherwise the all performance aspect
goes by the window. Which is our reason to use a cache in the first place.
One small suggestion about OpenJPA and caching in general. I thi
> I hope this goes through very soon in the code...
As I mentioned, I already checked in the change, so it's there in the
latest 1.1.0-SNAPSHOT builds.
-Patrick
On Fri, Apr 4, 2008 at 5:05 PM, <[EMAIL PROTECTED]> wrote:
> The reason I raised that point was becuase I am using a Coherence cache.
Yeah, it'd definitely be nice to formalize the cache pluggability a
bunch. We haven't done it largely because it's really really hard to
get pluggability APIs right for just one use case, so in the absence
of doing a bunch of plugins, you're unlikely to get it right.
To what extent is the code tha
I dont think anyone responded to this request yet - so I am asking again
I would like OpenJPA to remove all the toString() method on all children
class of OpenJPAId.
Reason: OpenJPAId class already has the toString() and it handles it well.
It puts the type and the id together - like this:
com.m
> PS: Can someone give me check in right in the code base... ;) - Have a good
> week end everyone.
The path to svn write access starts with patch submission
-Patrick
On Fri, Apr 4, 2008 at 5:32 PM, <[EMAIL PROTECTED]> wrote:
>
> I dont think anyone responded to this request yet - so I am
Patrick -
What you said was music to my ears.
I am very happy to see that you are interested in cleaning this up - it
gives me great hope for future version of openJPA.
It is not easy to discuss this in emails - maybe we will need a way to have
a conversation on this some day.
In a nutshell - af
28 matches
Mail list logo
