Patrick,
This is really strange. At first, I thought this was just another case of
the line ending character problem. But, when I look at the svn history of
the DB2Dictionary.java file, it's as if this latest commit is the only
record of the file. But, when I look at previous revisions, the
Okay, I think we need to back out these last two changes and revert back to
revision 509885. Dave needs to go back to the drawing board for this db2
optimization change, probably create a JIRA report for this proposed
change, and use the design discussion associated with the JIRA process to
get
3. OpenJPA does support a means of passing Oracle hints along
through to
the DBDictionary. Should we be trying to reuse some of the
capabilities
here?
+1
4. In the following snippets, I'd rather if we used 'Integer.valueOf
(1)'
or, better yet, a symbolic constant, instead of creating new
Okay, I think we need to back out these last two changes and revert
back to
revision 509885. Dave needs to go back to the drawing board for
this db2
optimization change, probably create a JIRA report for this proposed
change, and use the design discussion associated with the JIRA
process
+1. FTR, despite Abe's and my barrage of design suggestions, I love the
optimization. Abe: good call on using it for ranged queries.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with
If I understand it correct, I just have to bind the EMF
onserver startup like.
context.bind(my/jndi/name/for/emf,myEMFVariable);
Yep.
//does the statement below again create a NEW EMF or ist this
//just a lookup in the jndi-tree? but why is it
called Create
Thanks for the confirmation of the optimization ideas. We'll work through
the issues and come back with another version.
On 2/22/07, Patrick Linskey [EMAIL PROTECTED] wrote:
+1. FTR, despite Abe's and my barrage of design suggestions, I love the
optimization. Abe: good call on using it for
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-151:
--
Attachment: diff.txt
Prposed changes to remove pcFlags from enhanced classes
i. remove
[
https://issues.apache.org/jira/browse/OPENJPA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475095
]
Dain Sundstrom commented on OPENJPA-158:
+1
With this change I will be able to lower the log level in
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475099
]
Pinaki Poddar commented on OPENJPA-151:
---
Why will this require re-enhancement?
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475100
]
Patrick Linskey commented on OPENJPA-151:
-
Maybe we should do something explicit to make sure that classes
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475102
]
Michael Dick commented on OPENJPA-160:
--
Another performance issue we've run into is the overhead of creating a
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475108
]
Patrick Linskey commented on OPENJPA-160:
-
1. Is there a reason why we can't reuse the BrokerImpl objects?
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475144
]
Pinaki Poddar commented on OPENJPA-151:
---
One way is to add some extra checks on isPersistenceCapable() for
Hi there,
I have a question about JPA Queries containing relationships and a WHERE
filter. I basically want to have a JSF page containing a datatable that
shows a list of Departments - each Department row shows relevant columns
(department name, ID, etc) as well as a nested list of that
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sherry Shen updated OPENJPA-94:
---
Attachment: openjpa_94.zip
Test case with README and test results.
Allow MappingTool and
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475155
]
Patrick Linskey commented on OPENJPA-151:
-
Another would be to add a new getEnhancementContractVersion()
Overuse of synchronization in AbstractBrokerFactory
---
Key: OPENJPA-161
URL: https://issues.apache.org/jira/browse/OPENJPA-161
Project: OpenJPA
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-151:
--
Attachment: PCEnhancer.AddVersion.Diff.txt
Added a public int getEnhancementContractVersion()
Unfortunately, that means that we're using a synchronized
block during the lookup. If it looks like EM lookup is a
scalability issue for your app, do let us know -- it would
be pretty straightforward to replace the synchronized block
with a concurrent map.
OK, I got fed up with that
What about something like:
select distinct e.department from employee e where e.department.deptno
=100 and e.yearsOfService=15
Not sure if the above will do the trick without trying it myself...
Dain Sundstrom wrote:
I'm no JPA expert, so take my comments with a grain of salt.
How about
How about
select dept, oldtimers from Department dept LEFT JOIN
dept.employeeCollection oldtimers WHERE dept.deptno = 100 AND
oldtimers.yearsOfService = 15
That should give you only departments that satisfy the deptno
constraint and since you are not using outer join, only departments
22 matches
Mail list logo
