[jira] Commented: (OPENJPA-235) SQL reordering to avoid non-nullable foreign key constraint violations

[ https://issues.apache.org/jira/browse/OPENJPA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499200 ] Patrick Linskey commented on OPENJPA-235: - Hi, Attach the patch to the JIRA and one of those of us with

[jira] Commented: (OPENJPA-242) JCache (JSR 107) support in the OpenJPA DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499202 ] Patrick Linskey commented on OPENJPA-242: - With a small amount of work, we could abstract away the needs of

[jira] Commented: (OPENJPA-130) Streaming LOB support

[ https://issues.apache.org/jira/browse/OPENJPA-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497601 ] Patrick Linskey commented on OPENJPA-130: - Ignacio Andreu will be working on this issue for the Google

[jira] Commented: (OPENJPA-243) IntelliJ IDEA plugin to integrate OpenJPA enhancer into build process

[ https://issues.apache.org/jira/browse/OPENJPA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497624 ] Patrick Linskey commented on OPENJPA-243: - The plugin as of r540340 integrates the OpenJPA enhancer with

[jira] Commented: (OPENJPA-243) IntelliJ IDEA plugin to integrate OpenJPA enhancer into build process

[ https://issues.apache.org/jira/browse/OPENJPA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497626 ] Patrick Linskey commented on OPENJPA-243: - One missing instruction from the previous comment: the 0.1

[jira] Commented: (OPENJPA-194) Correct suffixes of build artifacts to elimiate '-all' and '-project'

[ https://issues.apache.org/jira/browse/OPENJPA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493962 ] Patrick Linskey commented on OPENJPA-194: - I think that it's more common to see things like

[jira] Assigned: (OPENJPA-235) SQL reordering to avoid non-nullable foreign key constraint violations

[ https://issues.apache.org/jira/browse/OPENJPA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey reassigned OPENJPA-235: --- Assignee: Patrick Linskey SQL reordering to avoid non-nullable foreign key

[jira] Resolved: (OPENJPA-235) SQL reordering to avoid non-nullable foreign key constraint violations

[ https://issues.apache.org/jira/browse/OPENJPA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-235. - Resolution: Fixed SQL reordering to avoid non-nullable foreign key constraint

[jira] Resolved: (OPENJPA-226) Change openjpa.DetachState 'fgs' setting to 'fetch-groups'

[ https://issues.apache.org/jira/browse/OPENJPA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-226. - Resolution: Fixed Change openjpa.DetachState 'fgs' setting to 'fetch-groups'

[jira] Updated: (OPENJPA-230) Handle guaranteed delivery of Data Cache events on normal JVM termination using TCPRemoteCommitProvider

[ https://issues.apache.org/jira/browse/OPENJPA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-230: Attachment: OPENJPA-230.patch It'd be nice to not have to synchronize. What about if we

[jira] Updated: (OPENJPA-230) Handle guaranteed delivery of Data Cache events on normal JVM termination using TCPRemoteCommitProvider

[ https://issues.apache.org/jira/browse/OPENJPA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-230: Attachment: OPENJPA-230.patch Good point -- _keepRunning is a bit too abrupt. How does

[jira] Resolved: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

[ https://issues.apache.org/jira/browse/OPENJPA-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-229. - Resolution: Fixed OpenJPA fails with MappedSuperclasses and Entities with the same

[jira] Commented: (OPENJPA-228) Could not locate metadata for the class using alias

[ https://issues.apache.org/jira/browse/OPENJPA-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491537 ] Patrick Linskey commented on OPENJPA-228: - I haven't run it yet, but a couple of things look suspicious:

[jira] Closed: (OPENJPA-228) Could not locate metadata for the class using alias

[ https://issues.apache.org/jira/browse/OPENJPA-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey closed OPENJPA-228. --- Resolution: Fixed Persistent classes were not enhanced prior to use. Added a better error

[jira] Created: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

OpenJPA fails with MappedSuperclasses and Entities with the same short names Key: OPENJPA-229 URL: https://issues.apache.org/jira/browse/OPENJPA-229 Project: OpenJPA

[jira] Updated: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

[ https://issues.apache.org/jira/browse/OPENJPA-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-229: Component/s: kernel Fix Version/s: 0.9.8 Description: When

[jira] Updated: (OPENJPA-229) OpenJPA fails with MappedSuperclasses and Entities with the same short names

[ https://issues.apache.org/jira/browse/OPENJPA-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-229: Attachment: OPENJPA-229.patch This fixes the problem by changing the enhancer to not

[jira] Commented: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491316 ] Patrick Linskey commented on OPENJPA-219: - another way to approach this would be not to cache at all, and

[jira] Assigned: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey reassigned OPENJPA-219: --- Assignee: Patrick Linskey Reflection: negative caching would be beneficial in

[jira] Commented: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491458 ] Patrick Linskey commented on OPENJPA-219: - How does this compare to the leaky-patch version? Reflection:

[jira] Created: (OPENJPA-226) Change openjpa.DetachState 'fgs' setting to 'fetch-groups'

Change openjpa.DetachState 'fgs' setting to 'fetch-groups' -- Key: OPENJPA-226 URL: https://issues.apache.org/jira/browse/OPENJPA-226 Project: OpenJPA Issue Type: Improvement

[jira] Updated: (OPENJPA-226) Change openjpa.DetachState 'fgs' setting to 'fetch-groups'

[ https://issues.apache.org/jira/browse/OPENJPA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-226: Attachment: OPENJPA-226.patch Here's a patch that does this. Thoughts? Change

[jira] Commented: (OPENJPA-221) DerbyDictionary doesn't describe a working mapping for char fields.

[ https://issues.apache.org/jira/browse/OPENJPA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489761 ] Patrick Linskey commented on OPENJPA-221: - What happens if, without your patch, you set the DBDictionary

[jira] Commented: (OPENJPA-221) DerbyDictionary doesn't describe a working mapping for char fields.

[ https://issues.apache.org/jira/browse/OPENJPA-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489820 ] Patrick Linskey commented on OPENJPA-221: - It's not surprising that the OpenJPA tests storeCharsAsNumbers

[jira] Updated: (OPENJPA-219) Reflection: negative caching would be beneficial in redeployment scenarios

[ https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-219: Attachment: OPENJPA-219.patch I think that this patch should fix the issue, but haven't

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489558 ] Patrick Linskey commented on OPENJPA-182: - Some comments: 1. I don't think that we should be doing work on

[jira] Commented: (OPENJPA-212) Constructor expression permits no other expressions in SELECT clause

[ https://issues.apache.org/jira/browse/OPENJPA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487948 ] Patrick Linskey commented on OPENJPA-212: - You don't have a test case handy for this by any chance, do you?

[jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload

[ https://issues.apache.org/jira/browse/OPENJPA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487950 ] Patrick Linskey commented on OPENJPA-91: Hi, Patrick, what kind of DB2 driver info we should put into the

[jira] Commented: (OPENJPA-211) CLONE -java.lang.VerifyError on websphere 6.1 with Spring 2.0.3 and OpenJpa 0.96/0.97

[ https://issues.apache.org/jira/browse/OPENJPA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487650 ] Patrick Linskey commented on OPENJPA-211: - Provided that meth is a static method, this method should run

[jira] Updated: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-182: Attachment: OPENJPA-182.patch Remove forUpdate from DBDictionary.toOperation()'s

[jira] Resolved: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-182. - Resolution: Fixed Assignee: (was: David Wisneski) I think that, aside from

[jira] Commented: (OPENJPA-184) use DB2 Diagnostic interface to report extended error diagnostics on SQL Exception

[ https://issues.apache.org/jira/browse/OPENJPA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487365 ] Patrick Linskey commented on OPENJPA-184: - Is this issue still open? use DB2 Diagnostic interface to

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ 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

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ 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

[jira] Resolved: (OPENJPA-204) Nesting of Emebedded in Embeddable element

[ 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:

[jira] Created: (OPENJPA-205) JPA2 Follow-Up

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

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ 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

[jira] Updated: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-182: Attachment: OPENJPA-182.patch For the sake of discussion, I've attached an alternate

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486819 ] Patrick Linskey commented on OPENJPA-182: - In the hint-based approach, you could set the hints on a

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486821 ] Patrick Linskey commented on OPENJPA-182: - It's probably worth noting that everything in the FetchPlan is

[jira] Commented: (OPENJPA-197) @Version property doesn't ensure integrity when performing the merge operation

[ 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

[jira] Commented: (OPENJPA-197) @Version property doesn't ensure integrity when performing the merge operation

[ 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

[jira] Resolved: (OPENJPA-57) persistence_1_0.xsd is missing

[ 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

[jira] Commented: (OPENJPA-182) db2 update lock syntax WITH isolation USE AND KEEP UPDATE LOCKS

[ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485103 ] Patrick Linskey commented on OPENJPA-182: - Wow... that's a lot more DB2 locking knowledge than I've ever

[jira] Resolved: (OPENJPA-186) Build failure of OpenJPA sources from trunk

[ https://issues.apache.org/jira/browse/OPENJPA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-186. - Resolution: Fixed Sorry about that -- I don't think that many of us run 'mvn install'

[jira] Updated: (OPENJPA-184) use DB2 Diagnostic interface to report extended error diagnostics on SQL Exception

[ https://issues.apache.org/jira/browse/OPENJPA-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-184: This message will be appended to the persistence exception error message already created

[jira] Commented: (OPENJPA-168) sql optimize n rows query hint

[ https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484288 ] Patrick Linskey commented on OPENJPA-168: - 2. I don't think we need a FetchConfiguration instance

[jira] Created: (OPENJPA-183) OpenJPAEntityManager large transaction APIs should take class arguments to narrow behavior

OpenJPAEntityManager large transaction APIs should take class arguments to narrow behavior -- Key: OPENJPA-183 URL: https://issues.apache.org/jira/browse/OPENJPA-183

[jira] Updated: (OPENJPA-172) DSRA9250E: Operation setTransactionIsolation is not allowed during a global transaction for Shareable Connections.

[ https://issues.apache.org/jira/browse/OPENJPA-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-172: Fix Version/s: (was: 0.9.6) 0.9.7 0.9.6 is released; moving the

[jira] Created: (OPENJPA-169) Queries against dirty extents and flushing: should provide an option to set savepoint, flush, query, rollback to savepoint

Queries against dirty extents and flushing: should provide an option to set savepoint, flush, query, rollback to savepoint -- Key: OPENJPA-169

[jira] Created: (OPENJPA-170) Constrain types to be flushed

Constrain types to be flushed - Key: OPENJPA-170 URL: https://issues.apache.org/jira/browse/OPENJPA-170 Project: OpenJPA Issue Type: Improvement Reporter: Patrick Linskey When invoking

[jira] Created: (OPENJPA-167) Named queries and no listed entities: bad error message

Named queries and no listed entities: bad error message --- Key: OPENJPA-167 URL: https://issues.apache.org/jira/browse/OPENJPA-167 Project: OpenJPA Issue Type: Bug Components:

[jira] Resolved: (OPENJPA-35) In-memory Delete operation fails with active DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-35. Resolution: Fixed Fix Version/s: (was: 0.9.7) In-memory Delete operation fails

[jira] Updated: (OPENJPA-35) In-memory Delete operation fails with active DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-35: --- Fix Version/s: 0.9.7 In-memory Delete operation fails with active DataCache

[jira] Updated: (OPENJPA-71) Caching primitive array types consumes excessive memory

[ https://issues.apache.org/jira/browse/OPENJPA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-71: --- Fix Version/s: 0.9.7 Affects Version/s: 0.9.0 0.9.6 Caching

[jira] Resolved: (OPENJPA-71) Caching primitive array types consumes excessive memory

[ https://issues.apache.org/jira/browse/OPENJPA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-71. Resolution: Fixed Fix Version/s: (was: 0.9.7) Caching primitive array types

[jira] Resolved: (OPENJPA-46) true, false not case insensitive, gets null pointer exception

[ https://issues.apache.org/jira/browse/OPENJPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-46. Resolution: Fixed Fix Version/s: (was: 0.9.7) Assignee: (was:

[jira] Resolved: (OPENJPA-80) Bad Escaping for LIKE in MySQL

[ https://issues.apache.org/jira/browse/OPENJPA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-80. Resolution: Fixed Bad Escaping for LIKE in MySQL --

[jira] Created: (OPENJPA-163) @OneToOne should not be legal as back-pointer of @OneToMany

@OneToOne should not be legal as back-pointer of @OneToMany --- Key: OPENJPA-163 URL: https://issues.apache.org/jira/browse/OPENJPA-163 Project: OpenJPA Issue Type: Improvement

[jira] Updated: (OPENJPA-164) Need better logging on Java field type to SQL type mapping and exceptions

[ https://issues.apache.org/jira/browse/OPENJPA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-164: Component/s: jdbc diagnostics Fix Version/s: 0.9.7

[jira] Commented: (OPENJPA-162) @OrderBy on @OneToMany does not allow ordering by @Id value

[ https://issues.apache.org/jira/browse/OPENJPA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478122 ] Patrick Linskey commented on OPENJPA-162: - I believe that the issue is that the field is not in the current

[jira] Commented: (OPENJPA-160) Reuse BrokerImpl objects

[ https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476629 ] Patrick Linskey commented on OPENJPA-160: - K... IMO, we should get rid of the finalizer in the default

[jira] Updated: (OPENJPA-160) Reuse BrokerImpl objects

[ https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-160: Attachment: openjpa-160-finalization-and-cloning-patch.txt - moved BrokerImpl.finalize()

[jira] Resolved: (OPENJPA-160) Reuse BrokerImpl objects

[ https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-160. - Resolution: Fixed Hopefully, we can put this to rest now. Reuse BrokerImpl objects

[jira] Commented: (OPENJPA-160) Reuse BrokerImpl objects

[ https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476736 ] Patrick Linskey commented on OPENJPA-160: - 1. I really think we're going just a bit too fast here. I

[jira] Commented: (OPENJPA-160) Reuse BrokerImpl objects

[ https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476749 ] Patrick Linskey commented on OPENJPA-160: - The extra day would have allowed Abe to get his comments

[jira] Updated: (OPENJPA-125) OpenJPA-specific metadata cannot be specified in XML descriptors

[ https://issues.apache.org/jira/browse/OPENJPA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-125: Affects Version/s: 1.0.0 OpenJPA-specific metadata cannot be specified in XML

[jira] Updated: (OPENJPA-35) In-memory Delete operation fails with active DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-35: --- Fix Version/s: 0.9.7 Affects Version/s: 0.9.6 In-memory Delete operation fails with

[jira] Updated: (OPENJPA-125) OpenJPA-specific metadata cannot be specified in XML descriptors

[ https://issues.apache.org/jira/browse/OPENJPA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-125: Fix Version/s: 1.0.0 Affects Version/s: (was: 1.0.0)

[jira] Updated: (OPENJPA-35) In-memory Delete operation fails with active DataCache

[ https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-35: --- Affects Version/s: 0.9.0 In-memory Delete operation fails with active DataCache

[jira] Updated: (OPENJPA-89) Bulk delete fails to delete owned many-to-many relationship (entry remains in join table)

[ https://issues.apache.org/jira/browse/OPENJPA-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-89: --- Fix Version/s: 0.9.7 Bulk delete fails to delete owned many-to-many relationship (entry

[jira] Updated: (OPENJPA-135) join fetch not returning duplicate references which not conforming to ejb3.0 spec

[ https://issues.apache.org/jira/browse/OPENJPA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-135: Fix Version/s: 0.9.7 join fetch not returning duplicate references which not conforming

[jira] Updated: (OPENJPA-17) bad sql with missing subquery produced with query with nested subqueries

[ https://issues.apache.org/jira/browse/OPENJPA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-17: --- Fix Version/s: 0.9.7 bad sql with missing subquery produced with query with nested

[jira] Updated: (OPENJPA-148) Parsing exception while using an exploded archive

[ https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-148: Fix Version/s: 0.9.7 Parsing exception while using an exploded archive

[jira] Updated: (OPENJPA-134) Extra unneeded SQL joins for OneToMany relationship with fetch type EAGER

[ https://issues.apache.org/jira/browse/OPENJPA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-134: Fix Version/s: 0.9.7 Extra unneeded SQL joins for OneToMany relationship with fetch type

[jira] Updated: (OPENJPA-49) bad sql pushdown, should use inner joins but has no joins, just uses first entity

[ https://issues.apache.org/jira/browse/OPENJPA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-49: --- Fix Version/s: 0.9.7 bad sql pushdown, should use inner joins but has no joins, just uses

[jira] Updated: (OPENJPA-142) Entity name is ignored when specified in the orm.xml file

[ https://issues.apache.org/jira/browse/OPENJPA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-142: Fix Version/s: 0.9.7 Entity name is ignored when specified in the orm.xml file

[jira] Updated: (OPENJPA-26) JPQL parser failed to handle unary operations in arithmetic comparisons, eg. where -(e.salary+10) -10

[ https://issues.apache.org/jira/browse/OPENJPA-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-26: --- Fix Version/s: 0.9.7 JPQL parser failed to handle unary operations in arithmetic

[jira] Updated: (OPENJPA-152) Warn or throw an exception when a persistence unit has multiple named queries with the same name

[ https://issues.apache.org/jira/browse/OPENJPA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-152: Fix Version/s: 0.9.7 Warn or throw an exception when a persistence unit has multiple

[jira] Updated: (OPENJPA-75) error message for missing query id var needs improvement

[ https://issues.apache.org/jira/browse/OPENJPA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-75: --- Fix Version/s: 0.9.7 error message for missing query id var needs improvement

[jira] Updated: (OPENJPA-113) when you specify columm table=empbean in the xml file entity id or basic type when empbean is the default table name, the mapping tool generates extra foreign key fiel

[ https://issues.apache.org/jira/browse/OPENJPA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-113: Fix Version/s: 0.9.7 when you specify columm table=empbean in the xml file entity id or

[jira] Updated: (OPENJPA-18) bulk update to Entity with secondary table mapping produces BAD SQL

[ https://issues.apache.org/jira/browse/OPENJPA-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-18: --- Fix Version/s: 0.9.7 bulk update to Entity with secondary table mapping produces BAD SQL

[jira] Updated: (OPENJPA-28) groupby clause of a subquery incorrectly duplicated in the main query in the generated SQL

[ https://issues.apache.org/jira/browse/OPENJPA-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-28: --- Fix Version/s: 0.9.7 groupby clause of a subquery incorrectly duplicated in the main query

[jira] Updated: (OPENJPA-51) bad sql pushdown, sub select is missing from clause

[ https://issues.apache.org/jira/browse/OPENJPA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-51: --- Fix Version/s: 0.9.7 bad sql pushdown, sub select is missing from clause

[jira] Updated: (OPENJPA-80) Bad Escaping for LIKE in MySQL

[ https://issues.apache.org/jira/browse/OPENJPA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-80: --- Fix Version/s: 0.9.7 Bad Escaping for LIKE in MySQL --

[jira] Updated: (OPENJPA-78) Automatic runtime enhancement only works when the class is listed in the first persistence-unit

[ https://issues.apache.org/jira/browse/OPENJPA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-78: --- Fix Version/s: 0.9.7 Automatic runtime enhancement only works when the class is listed in

[jira] Updated: (OPENJPA-9) PCEnhancer not processing multiple PU's defined within a single persistence.xml file

[ https://issues.apache.org/jira/browse/OPENJPA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-9: -- Fix Version/s: 0.9.7 PCEnhancer not processing multiple PU's defined within a single

[jira] Updated: (OPENJPA-46) true, false not case insensitive, gets null pointer exception

[ https://issues.apache.org/jira/browse/OPENJPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-46: --- Fix Version/s: 0.9.7 true, false not case insensitive, gets null pointer exception

[jira] Updated: (OPENJPA-143) Problems with Single Table Inheritance Strategy (and Discriminator Type of Integer)

[ https://issues.apache.org/jira/browse/OPENJPA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-143: Fix Version/s: 0.9.7 Problems with Single Table Inheritance Strategy (and Discriminator

[jira] Updated: (OPENJPA-112) Native queries and named parameters: poor error message

[ https://issues.apache.org/jira/browse/OPENJPA-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-112: Fix Version/s: 0.9.7 Native queries and named parameters: poor error message

[jira] Updated: (OPENJPA-83) Bad SQL for Subselect BETWEEN

[ https://issues.apache.org/jira/browse/OPENJPA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-83: --- Fix Version/s: 0.9.7 Bad SQL for Subselect BETWEEN -

[jira] Updated: (OPENJPA-57) persistence_1_0.xsd is missing

[ https://issues.apache.org/jira/browse/OPENJPA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-57: --- Fix Version/s: 0.9.7 persistence_1_0.xsd is missing --

[jira] Updated: (OPENJPA-132) java.lang.NoSuchMethodError for entity with ID of type java.sql.Date

[ https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-132: Fix Version/s: 0.9.7 java.lang.NoSuchMethodError for entity with ID of type

[jira] Updated: (OPENJPA-22) locate substring queries fail both db2 derby, cannot use parameter markers in expression ?-?

[ https://issues.apache.org/jira/browse/OPENJPA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-22: --- Fix Version/s: 0.9.7 locate substring queries fail both db2 derby, cannot use parameter

[jira] Resolved: (OPENJPA-153) WebSphere and non-jta-data-source and default ManagedRuntime

[ https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-153. - Resolution: Fixed I believe that the only remaining issue here is captured in

[jira] Updated: (OPENJPA-147) T T OpenJPAEntityManager.createInstance(ClassT cls) fails when T is interface

[ https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-147: Fix Version/s: 1.0.0 T T OpenJPAEntityManager.createInstance(ClassT cls) fails when T is

[jira] Updated: (OPENJPA-145) support Java5 wildcard on OpenJPA

[ https://issues.apache.org/jira/browse/OPENJPA-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-145: Fix Version/s: 1.0.0 support Java5 wildcard on OpenJPA

[jira] Resolved: (OPENJPA-93) Sequence generation in a JTA environment should not require non-JTA datasource

[ https://issues.apache.org/jira/browse/OPENJPA-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey resolved OPENJPA-93. Resolution: Fixed The feature works, but OPENJPA-149 currently prevents it from working in

[jira] Updated: (OPENJPA-84) Escape sql reserved words in column names

[ https://issues.apache.org/jira/browse/OPENJPA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-84: --- Fix Version/s: 1.0.0 Escape sql reserved words in column names

[jira] Updated: (OPENJPA-71) Caching primitive array types consumes excessive memory

[ https://issues.apache.org/jira/browse/OPENJPA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey updated OPENJPA-71: --- Fix Version/s: 0.9.7 What happens if openjpa.DynamicDataStructs is enabled? Caching

  1   2   3   >