[jira] [Reopened] (OPENJPA-2414) FinderCache does not consider active Fetch Groups/FetchPlan added Fields

[ https://issues.apache.org/jira/browse/OPENJPA-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reopened OPENJPA-2414: This change is not align with the original intent. The idea of caching a finder query is

[jira] [Updated] (OPENJPA-2421) Slices: Can't setting up FinderTargetPolicy

[ https://issues.apache.org/jira/browse/OPENJPA-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2421: --- Assignee: Pinaki Poddar Slices: Can't setting up FinderTargetPolicy

[jira] [Resolved] (OPENJPA-2421) Slices: Can't setting up FinderTargetPolicy

[ https://issues.apache.org/jira/browse/OPENJPA-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2421. Resolution: Fixed Fix Version/s: 2.3.0 Slices: Can't setting up

[jira] [Resolved] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2318. Resolution: Fixed Fix Version/s: 2.3.0 Left outer join is not generated when

[jira] [Updated] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2318: --- Assignee: Pinaki Poddar Left outer join is not generated when specifien using

[jira] [Created] (OPENJPA-2384) Rendering criteria query to JPQL-like string ignores multiple GROUP BY clauses

Pinaki Poddar created OPENJPA-2384: -- Summary: Rendering criteria query to JPQL-like string ignores multiple GROUP BY clauses Key: OPENJPA-2384 URL: https://issues.apache.org/jira/browse/OPENJPA-2384

[jira] [Commented] (OPENJPA-2384) Rendering criteria query to JPQL-like string ignores multiple GROUP BY clauses

[ https://issues.apache.org/jira/browse/OPENJPA-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664313#comment-13664313 ] Pinaki Poddar commented on OPENJPA-2384: this issue was fixed with following

[jira] [Resolved] (OPENJPA-2384) Rendering criteria query to JPQL-like string ignores multiple GROUP BY clauses

[ https://issues.apache.org/jira/browse/OPENJPA-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2384. Resolution: Fixed see revision r1456576 (that was not referred to an issue).

[jira] [Created] (OPENJPA-2380) investigate possible optimization for batch update managers

Pinaki Poddar created OPENJPA-2380: -- Summary: investigate possible optimization for batch update managers Key: OPENJPA-2380 URL: https://issues.apache.org/jira/browse/OPENJPA-2380 Project: OpenJPA

[jira] [Updated] (OPENJPA-2373) MapsId in a Child entity to a Parent entity using auto-assigned identity fails with duplicte INSERT SQL

[ https://issues.apache.org/jira/browse/OPENJPA-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2373: --- Attachment: graycol.gif Albert, I will take a look. 1. May take a little while. 2.

[jira] [Updated] (OPENJPA-2356) Use new Offset/Limit/ROWNUM features in DB2 family of databases for range queries

[ https://issues.apache.org/jira/browse/OPENJPA-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2356: --- Attachment: graycol.gif Albert, The test (TestRangeQuery) runs OK in my environment

[jira] [Created] (OPENJPA-2379) Simplify detemining load state

Pinaki Poddar created OPENJPA-2379: -- Summary: Simplify detemining load state Key: OPENJPA-2379 URL: https://issues.apache.org/jira/browse/OPENJPA-2379 Project: OpenJPA Issue Type:

[jira] [Commented] (OPENJPA-2379) Simplify detemining load state

[ https://issues.apache.org/jira/browse/OPENJPA-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649905#comment-13649905 ] Pinaki Poddar commented on OPENJPA-2379: Some tests are retired that verifies

[jira] [Created] (OPENJPA-2373) MapsId in a Child entity to a Parent entity using auto-assigned identity fails with duplicte INSERT SQL

Pinaki Poddar created OPENJPA-2373: -- Summary: MapsId in a Child entity to a Parent entity using auto-assigned identity fails with duplicte INSERT SQL Key: OPENJPA-2373 URL:

[jira] [Updated] (OPENJPA-2364) Slices: Bulk JPQL Deletes/Updates ignoring Target plugins and query hints.

[ https://issues.apache.org/jira/browse/OPENJPA-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2364: --- Assignee: Pinaki Poddar Slices: Bulk JPQL Deletes/Updates ignoring Target plugins and

[jira] [Created] (OPENJPA-2365) Support Bulk Delete operation on Slice

Pinaki Poddar created OPENJPA-2365: -- Summary: Support Bulk Delete operation on Slice Key: OPENJPA-2365 URL: https://issues.apache.org/jira/browse/OPENJPA-2365 Project: OpenJPA Issue Type:

[jira] [Updated] (OPENJPA-2356) Use new Offset/Limit/ROWNUM features in DB2 family of databases for range queries

[ https://issues.apache.org/jira/browse/OPENJPA-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2356: --- Fix Version/s: 2.3.0 Use new Offset/Limit/ROWNUM features in DB2 family of databases

[jira] [Updated] (OPENJPA-2355) CONCAT() function must support more than two arguments

[ https://issues.apache.org/jira/browse/OPENJPA-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2355: --- Fix Version/s: 2.3.0 CONCAT() function must support more than two arguments

[jira] [Resolved] (OPENJPA-2355) CONCAT() function must support more than two arguments

[ https://issues.apache.org/jira/browse/OPENJPA-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2355. Resolution: Fixed CONCAT() function must support more than two arguments

[jira] [Updated] (OPENJPA-2336) Relax Join column name comparison based on database dictionary schema case setting

[ https://issues.apache.org/jira/browse/OPENJPA-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2336: --- Fix Version/s: 2.3.0 Relax Join column name comparison based on database dictionary

[jira] [Resolved] (OPENJPA-2336) Relax Join column name comparison based on database dictionary schema case setting

[ https://issues.apache.org/jira/browse/OPENJPA-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2336. Resolution: Fixed Relax Join column name comparison based on database dictionary

[jira] [Updated] (OPENJPA-2335) Constrained foreign key column value setting needs to be flexible

[ https://issues.apache.org/jira/browse/OPENJPA-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2335: --- Fix Version/s: 2.3.0 Constrained foreign key column value setting needs to be

[jira] [Resolved] (OPENJPA-2335) Constrained foreign key column value setting needs to be flexible

[ https://issues.apache.org/jira/browse/OPENJPA-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2335. Resolution: Fixed Constrained foreign key column value setting needs to be flexible

[jira] [Resolved] (OPENJPA-2305) Canonical MetaModel class generation should not use inhertence

[ https://issues.apache.org/jira/browse/OPENJPA-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2305. Resolution: Invalid Canonical MetaModel class generation should not use inhertence

[jira] [Reopened] (OPENJPA-2305) Canonical MetaModel class generation should not use inhertence

[ https://issues.apache.org/jira/browse/OPENJPA-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reopened OPENJPA-2305: Canonical MetaModel class generation should not use inhertence

[jira] [Resolved] (OPENJPA-2305) Canonical MetaModel class generation should not use inhertence

[ https://issues.apache.org/jira/browse/OPENJPA-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2305. Resolution: Fixed Canonical MetaModel class generation should not use inhertence

[jira] [Resolved] (OPENJPA-2030) Build auditing facility

[ https://issues.apache.org/jira/browse/OPENJPA-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2030. Resolution: Fixed Assignee: Pinaki Poddar Build auditing facility

[jira] [Updated] (OPENJPA-1979) Regression for non-standard joins with constant column values

[ https://issues.apache.org/jira/browse/OPENJPA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1979: --- Fix Version/s: 2.3.0 Regression for non-standard joins with constant column values

[jira] [Resolved] (OPENJPA-1979) Regression for non-standard joins with constant column values

[ https://issues.apache.org/jira/browse/OPENJPA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-1979. Resolution: Fixed Assignee: Pinaki Poddar Regression for non-standard joins

[jira] [Resolved] (OPENJPA-1851) RESTful access to Persistence Unit runtime

[ https://issues.apache.org/jira/browse/OPENJPA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-1851. Resolution: Fixed RESTful access to Persistence Unit runtime

[jira] [Updated] (OPENJPA-1851) RESTful access to Persistence Unit runtime

[ https://issues.apache.org/jira/browse/OPENJPA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1851: --- Fix Version/s: 2.2.0 RESTful access to Persistence Unit runtime

[jira] [Updated] (OPENJPA-1160) Failed transactions must generate more focussed (and accurate) message for the cause

[ https://issues.apache.org/jira/browse/OPENJPA-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1160: --- Fix Version/s: 2.0.0 Failed transactions must generate more focussed (and accurate)

[jira] [Resolved] (OPENJPA-1160) Failed transactions must generate more focussed (and accurate) message for the cause

[ https://issues.apache.org/jira/browse/OPENJPA-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-1160. Resolution: Fixed Assignee: Pinaki Poddar Failed transactions must generate

[jira] [Created] (OPENJPA-2356) Use new Offset/Limit/ROWNUM features in DB2 family of databases for range queries

Pinaki Poddar created OPENJPA-2356: -- Summary: Use new Offset/Limit/ROWNUM features in DB2 family of databases for range queries Key: OPENJPA-2356 URL: https://issues.apache.org/jira/browse/OPENJPA-2356

[jira] [Created] (OPENJPA-2355) CONCAT() function must support more than two arguments

Pinaki Poddar created OPENJPA-2355: -- Summary: CONCAT() function must support more than two arguments Key: OPENJPA-2355 URL: https://issues.apache.org/jira/browse/OPENJPA-2355 Project: OpenJPA

[jira] [Commented] (OPENJPA-2344) You cannot invoke other java.sql.Clob/java.sql.Blob methods after calling the free() method or after the Blob/Clob's transaction has been committed or rolled back.

[ https://issues.apache.org/jira/browse/OPENJPA-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594138#comment-13594138 ] Pinaki Poddar commented on OPENJPA-2344: Run with following persistence.xml

[jira] [Commented] (OPENJPA-2305) Canonical MetaModel class generation should not use inhertence

[ https://issues.apache.org/jira/browse/OPENJPA-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13590911#comment-13590911 ] Pinaki Poddar commented on OPENJPA-2305: As per spec, the inheritance hierarchy

[jira] [Created] (OPENJPA-2335) Constrained foreign key column value setting needs to be flexible

Pinaki Poddar created OPENJPA-2335: -- Summary: Constrained foreign key column value setting needs to be flexible Key: OPENJPA-2335 URL: https://issues.apache.org/jira/browse/OPENJPA-2335 Project:

[jira] [Commented] (OPENJPA-2334) OpenJPA must support processing puRoot jar-file URLs as jar-formatted InputStreams

[ https://issues.apache.org/jira/browse/OPENJPA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581597#comment-13581597 ] Pinaki Poddar commented on OPENJPA-2334: The patch has some hardcoded error

[jira] [Created] (OPENJPA-2336) Relax Join column name comparison based on database dictionary schema case setting

Pinaki Poddar created OPENJPA-2336: -- Summary: Relax Join column name comparison based on database dictionary schema case setting Key: OPENJPA-2336 URL: https://issues.apache.org/jira/browse/OPENJPA-2336

[jira] [Updated] (OPENJPA-2280) MappingTool ignores column precision / scale for some databases

[ https://issues.apache.org/jira/browse/OPENJPA-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2280: --- Attachment: JIRA-2280.txt This patch changes the following 1. BigDecimal values are

[jira] [Commented] (OPENJPA-2280) MappingTool ignores column precision / scale for some databases

[ https://issues.apache.org/jira/browse/OPENJPA-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570737#comment-13570737 ] Pinaki Poddar commented on OPENJPA-2280: From the responses, I gather that we

[jira] [Commented] (OPENJPA-2280) MappingTool ignores column precision / scale for some databases

[ https://issues.apache.org/jira/browse/OPENJPA-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13569033#comment-13569033 ] Pinaki Poddar commented on OPENJPA-2280: The discipline with BigDecimal values

[jira] [Created] (OPENJPA-2325) MappedSuperClass without an @Id causes wrong identity type for the inherited types

Pinaki Poddar created OPENJPA-2325: -- Summary: MappedSuperClass without an @Id causes wrong identity type for the inherited types Key: OPENJPA-2325 URL: https://issues.apache.org/jira/browse/OPENJPA-2325

[jira] [Commented] (OPENJPA-2325) MappedSuperClass without an @Id causes wrong identity type for the inherited types

[ https://issues.apache.org/jira/browse/OPENJPA-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559668#comment-13559668 ] Pinaki Poddar commented on OPENJPA-2325: The problem surfaces when an instance

[jira] [Resolved] (OPENJPA-2325) MappedSuperClass without an @Id causes wrong identity type for the inherited types

[ https://issues.apache.org/jira/browse/OPENJPA-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2325. Resolution: Fixed MappedSuperClass without an @Id causes wrong identity type for

[jira] [Created] (OPENJPA-2321) Synchronizing logging output stream causes deadlock when used some JDK LogManger derivative

Pinaki Poddar created OPENJPA-2321: -- Summary: Synchronizing logging output stream causes deadlock when used some JDK LogManger derivative Key: OPENJPA-2321 URL:

[jira] [Resolved] (OPENJPA-2304) Thread deadlock in CriteriaBuilder

[ https://issues.apache.org/jira/browse/OPENJPA-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2304. Resolution: Fixed Thread deadlock in CriteriaBuilder

[jira] [Resolved] (OPENJPA-2320) CriteriaBuilder predicate construction deadlocks in multi-core VM due to static initializer

[ https://issues.apache.org/jira/browse/OPENJPA-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2320. Resolution: Fixed CriteriaBuilder predicate construction deadlocks in multi-core VM

[jira] [Resolved] (OPENJPA-2321) Synchronizing logging output stream causes deadlock when used some JDK LogManger derivative

[ https://issues.apache.org/jira/browse/OPENJPA-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2321. Resolution: Fixed Synchronizing logging output stream causes deadlock when used

[jira] [Created] (OPENJPA-2320) CriteriaBuilder predicate construction deadlocks in multi-core VM due to static initializer

Pinaki Poddar created OPENJPA-2320: -- Summary: CriteriaBuilder predicate construction deadlocks in multi-core VM due to static initializer Key: OPENJPA-2320 URL: https://issues.apache.org/jira/browse/OPENJPA-2320

[jira] [Created] (OPENJPA-2304) Thread deadlock in CriteriaBuilder

Pinaki Poddar created OPENJPA-2304: -- Summary: Thread deadlock in CriteriaBuilder Key: OPENJPA-2304 URL: https://issues.apache.org/jira/browse/OPENJPA-2304 Project: OpenJPA Issue Type: Bug

[jira] [Created] (OPENJPA-2305) Canonical MetaModel class generation should not use inhertence

Pinaki Poddar created OPENJPA-2305: -- Summary: Canonical MetaModel class generation should not use inhertence Key: OPENJPA-2305 URL: https://issues.apache.org/jira/browse/OPENJPA-2305 Project:

[jira] [Commented] (OPENJPA-2300) AnnotationProcessor shows warnings when executed on Java 7 sources

[ https://issues.apache.org/jira/browse/OPENJPA-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504359#comment-13504359 ] Pinaki Poddar commented on OPENJPA-2300: Does the annotation processor generate

[jira] [Commented] (OPENJPA-1532) Should the shared-cache-mode element in a persistence unit definition automatically turn on the data cache?

[ https://issues.apache.org/jira/browse/OPENJPA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461949#comment-13461949 ] Pinaki Poddar commented on OPENJPA-1532: Whether shared-cache-mode activates

[jira] [Commented] (OPENJPA-2220) Persistent field fetching statistic tool

[ https://issues.apache.org/jira/browse/OPENJPA-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401502#comment-13401502 ] Pinaki Poddar commented on OPENJPA-2220: I think it is a good/useful feature.

[jira] [Commented] (OPENJPA-2220) Persistent field fetching statistic tool

[ https://issues.apache.org/jira/browse/OPENJPA-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401504#comment-13401504 ] Pinaki Poddar commented on OPENJPA-2220: The documentation refers the

[jira] [Commented] (OPENJPA-2220) Persistent field fetching statistic tool

[ https://issues.apache.org/jira/browse/OPENJPA-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401804#comment-13401804 ] Pinaki Poddar commented on OPENJPA-2220: Rick, we came the consensus that if

[jira] [Commented] (OPENJPA-2039) FKs for EAGER fields that are not in the current fetchplan aren't selected

[ https://issues.apache.org/jira/browse/OPENJPA-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13085274#comment-13085274 ] Pinaki Poddar commented on OPENJPA-2039: I have not tracked the details of this

[jira] [Commented] (OPENJPA-2039) FKs for EAGER fields that are not in the current fetchplan aren't selected

[ https://issues.apache.org/jira/browse/OPENJPA-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13085418#comment-13085418 ] Pinaki Poddar commented on OPENJPA-2039: Looks OK to me. Perhaps I would a)

[jira] [Assigned] (OPENJPA-2008) OpenJPA does not work with native queries in a distributed (Slice) environment

[ https://issues.apache.org/jira/browse/OPENJPA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reassigned OPENJPA-2008: -- Assignee: Pinaki Poddar OpenJPA does not work with native queries in a distributed

[jira] [Commented] (OPENJPA-1011) Instantiate meta-model classes for JPA 2.0 from XML descriptors

[ https://issues.apache.org/jira/browse/OPENJPA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13069051#comment-13069051 ] Pinaki Poddar commented on OPENJPA-1011: Kevin, For a bug, there has to be

[jira] [Created] (OPENJPA-2030) Build auditing facility

Build auditing facility --- Key: OPENJPA-2030 URL: https://issues.apache.org/jira/browse/OPENJPA-2030 Project: OpenJPA Issue Type: New Feature Components: kernel Reporter: Pinaki Poddar Auditing

[jira] [Commented] (OPENJPA-1803) Unwrap EntityManager to Connection

[ https://issues.apache.org/jira/browse/OPENJPA-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064271#comment-13064271 ] Pinaki Poddar commented on OPENJPA-1803: + if

[jira] [Commented] (OPENJPA-2025) Byte[] and Char[] should be treated as SingularAttributes, not lists by the metamodel generator

[ https://issues.apache.org/jira/browse/OPENJPA-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060789#comment-13060789 ] Pinaki Poddar commented on OPENJPA-2025: Neat. I thought it would be more

[jira] [Updated] (OPENJPA-2026) Replace java.util.* or java.util.concurrent.* collections with scalable collection for better performance on multicore platforms?

[ https://issues.apache.org/jira/browse/OPENJPA-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-2026: --- Priority: Minor (was: Major) Summary: Replace java.util.* or java.util.concurrent.*

[jira] [Created] (OPENJPA-2026) Replace java.util.* or java.util.concurrent.* collections with scalable collection for better performance on multicore platforms

Replace java.util.* or java.util.concurrent.* collections with scalable collection for better performance on multicore platforms - Key: OPENJPA-2026

[jira] [Commented] (OPENJPA-2020) Make some members of StateManagerImpl protected to allow for greater extensability

[ https://issues.apache.org/jira/browse/OPENJPA-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13056727#comment-13056727 ] Pinaki Poddar commented on OPENJPA-2020: The committer is requested to response

[jira] [Commented] (OPENJPA-1999) Optional support for non-sequential positional parameters

[ https://issues.apache.org/jira/browse/OPENJPA-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049237#comment-13049237 ] Pinaki Poddar commented on OPENJPA-1999: The commit shows no tests with

[jira] [Created] (OPENJPA-2017) Improve batch insertion performance

Improve batch insertion performance --- Key: OPENJPA-2017 URL: https://issues.apache.org/jira/browse/OPENJPA-2017 Project: OpenJPA Issue Type: New Feature Components: kernel Affects Versions:

[jira] [Commented] (OPENJPA-2016) OpenJPA sometimes incorrectly complains about wrong number of parameters

[ https://issues.apache.org/jira/browse/OPENJPA-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13048783#comment-13048783 ] Pinaki Poddar commented on OPENJPA-2016: From the patch, +String jpql =

[jira] [Created] (OPENJPA-2012) MAX()/MIN() aggregate operation does not work on non-numeric types

MAX()/MIN() aggregate operation does not work on non-numeric types -- Key: OPENJPA-2012 URL: https://issues.apache.org/jira/browse/OPENJPA-2012 Project: OpenJPA Issue Type: Bug

[jira] [Commented] (OPENJPA-1992) java.lang.ArrayIndexOutOfBoundsException if positional parameter are not started from 1

[ https://issues.apache.org/jira/browse/OPENJPA-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030170#comment-13030170 ] Pinaki Poddar commented on OPENJPA-1992: The binding parameter indexing,

[jira] [Commented] (OPENJPA-655) Class level query filter

[ https://issues.apache.org/jira/browse/OPENJPA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028902#comment-13028902 ] Pinaki Poddar commented on OPENJPA-655: --- I appreciate the support for this feature.

[jira] [Created] (OPENJPA-1979) Regression for non-standard joins with constant column values

Regression for non-standard joins with constant column values -- Key: OPENJPA-1979 URL: https://issues.apache.org/jira/browse/OPENJPA-1979 Project: OpenJPA Issue Type: Bug

[jira] [Updated] (OPENJPA-1979) Regression for non-standard joins with constant column values

[ https://issues.apache.org/jira/browse/OPENJPA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1979: --- Attachment: Test-1979.zip The test case uses non-standard join for schema definition. The

[jira] [Updated] (OPENJPA-1979) Regression for non-standard joins with constant column values

[ https://issues.apache.org/jira/browse/OPENJPA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-1979: --- Attachment: OPENJPA-1979.patch.1.txt This is a patch to fix the problem. WARNING: Only

[jira] [Commented] (OPENJPA-1979) Regression for non-standard joins with constant column values

[ https://issues.apache.org/jira/browse/OPENJPA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019067#comment-13019067 ] Pinaki Poddar commented on OPENJPA-1979: XML mapping parser as well. Yes, of

[jira] [Commented] (OPENJPA-655) Class level query filter

[ https://issues.apache.org/jira/browse/OPENJPA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13010700#comment-13010700 ] Pinaki Poddar commented on OPENJPA-655: --- Please take a look and let me know your

[jira] Commented: (OPENJPA-1935) Informix lock exceptions are not mapped properly by OpenJPA

[ https://issues.apache.org/jira/browse/OPENJPA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12989811#comment-12989811 ] Pinaki Poddar commented on OPENJPA-1935: IX000 is specified as query error for

[jira] Created: (OPENJPA-1931) Support fine-grained data acess control for queries

Support fine-grained data acess control for queries --- Key: OPENJPA-1931 URL: https://issues.apache.org/jira/browse/OPENJPA-1931 Project: OpenJPA Issue Type: New Feature Components:

[jira] Created: (OPENJPA-1927) Add test for JEST

Add test for JEST - Key: OPENJPA-1927 URL: https://issues.apache.org/jira/browse/OPENJPA-1927 Project: OpenJPA Issue Type: Test Reporter: Pinaki Poddar Tests for JEST requires a servlet engine and some

[jira] Created: (OPENJPA-1923) Allow flexible (non-standard) syntax for collection-valued parameters in IN() expresseion of JPQL query

Allow flexible (non-standard) syntax for collection-valued parameters in IN() expresseion of JPQL query Key: OPENJPA-1923 URL:

[jira] Created: (OPENJPA-1907) Exact type of date-valued parameter not preserved during prepared query reparameterization

Exact type of date-valued parameter not preserved during prepared query reparameterization -- Key: OPENJPA-1907 URL: https://issues.apache.org/jira/browse/OPENJPA-1907

[jira] Assigned: (OPENJPA-1903) Some queries only work the first time they are executed

[ https://issues.apache.org/jira/browse/OPENJPA-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reassigned OPENJPA-1903: -- Assignee: Pinaki Poddar Some queries only work the first time they are executed

[jira] Commented: (OPENJPA-1903) Some queries only work the first time they are executed

[ https://issues.apache.org/jira/browse/OPENJPA-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12969059#action_12969059 ] Pinaki Poddar commented on OPENJPA-1903: If your environment permits, try recent

[jira] Resolved: (OPENJPA-1889) Relax query binding parameter type-checking for enum types

[ https://issues.apache.org/jira/browse/OPENJPA-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-1889. Resolution: Fixed Fix Version/s: 2.1.0 Relax query binding parameter

[jira] Assigned: (OPENJPA-1889) Relax query binding parameter type-checking for enum types

[ https://issues.apache.org/jira/browse/OPENJPA-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reassigned OPENJPA-1889: -- Assignee: Pinaki Poddar Relax query binding parameter type-checking for enum types

[jira] Commented: (OPENJPA-1873) EntityManager#merge sometimes passes wrong entity values to @PostLoad EntityListeners

[ https://issues.apache.org/jira/browse/OPENJPA-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932653#action_12932653 ] Pinaki Poddar commented on OPENJPA-1873: Mark, 1. is the attached test in

[jira] Created: (OPENJPA-1859) Create a sample to demonstrate usage of JEST

Create a sample to demonstrate usage of JEST Key: OPENJPA-1859 URL: https://issues.apache.org/jira/browse/OPENJPA-1859 Project: OpenJPA Issue Type: New Feature Components: samples

[jira] Commented: (OPENJPA-1851) RESTful access to Persistence Unit runtime

[ https://issues.apache.org/jira/browse/OPENJPA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924743#action_12924743 ] Pinaki Poddar commented on OPENJPA-1851: The proposed XML schema for Java

[jira] Commented: (OPENJPA-1851) RESTful access to Persistence Unit runtime

[ https://issues.apache.org/jira/browse/OPENJPA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924746#action_12924746 ] Pinaki Poddar commented on OPENJPA-1851: Proposed URI Syntax for REST on OpenJPA

[jira] Commented: (OPENJPA-1844) Create a JConsole plugin to display DataCache statistics and help tune the cache

[ https://issues.apache.org/jira/browse/OPENJPA-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924758#action_12924758 ] Pinaki Poddar commented on OPENJPA-1844: While I like the feature, there must be

[jira] Created: (OPENJPA-1851) RESTful access to Persistence Unit runtime

RESTful access to Persistence Unit runtime --- Key: OPENJPA-1851 URL: https://issues.apache.org/jira/browse/OPENJPA-1851 Project: OpenJPA Issue Type: New Feature Components: competitive,

[jira] Resolved: (OPENJPA-1826) Can we have a new type for ignoring values?

[ https://issues.apache.org/jira/browse/OPENJPA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-1826. Resolution: Fixed Fix Version/s: 2.1.0 2.0.2 Can we have a

[jira] Commented: (OPENJPA-1826) Can we have a new type for ignoring values?

[ https://issues.apache.org/jira/browse/OPENJPA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12920753#action_12920753 ] Pinaki Poddar commented on OPENJPA-1826: Added new action syntax

[jira] Assigned: (OPENJPA-1826) Can we have a new type for ignoring values?

[ https://issues.apache.org/jira/browse/OPENJPA-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reassigned OPENJPA-1826: -- Assignee: Pinaki Poddar Can we have a new type for ignoring values?

[jira] Assigned: (OPENJPA-1825) Replace non-null with nullable instead of optional

[ https://issues.apache.org/jira/browse/OPENJPA-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reassigned OPENJPA-1825: -- Assignee: Pinaki Poddar Replace non-null with nullable instead of optional

[jira] Closed: (OPENJPA-1823) Is merge() seriously broken?

[ https://issues.apache.org/jira/browse/OPENJPA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar closed OPENJPA-1823. -- Resolution: Invalid My silly bad. Ignore. Is merge() seriously broken?

[jira] Commented: (OPENJPA-1801) CacheStatistics misses are improperly calculated.

[ https://issues.apache.org/jira/browse/OPENJPA-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12918238#action_12918238 ] Pinaki Poddar commented on OPENJPA-1801: from JavaDoc of CacheStatistics * All

  1   2   3   4   5   6   7   >