[jira] Commented: (OPENJPA-1508) ArrayIndexOutOfBoundsException being thrown from ClassMetaData.getExtraFieldDataIndex()

[ https://issues.apache.org/jira/browse/OPENJPA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833153#action_12833153 ] B.J. Reed commented on OPENJPA-1508: Forgot to mention that one work around we found

[jira] Created: (OPENJPA-1508) ArrayIndexOutOfBoundsException being thrown from ClassMetaData.getExtraFieldDataIndex()

ArrayIndexOutOfBoundsException being thrown from ClassMetaData.getExtraFieldDataIndex() --- Key: OPENJPA-1508 URL: https://issues.apache.org/jira/browse/OPENJPA-1508

[jira] Updated: (OPENJPA-1508) ArrayIndexOutOfBoundsException being thrown from ClassMetaData.getExtraFieldDataIndex()

[ https://issues.apache.org/jira/browse/OPENJPA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1508: --- Attachment: tc.zip has the test case to demonstrate the exception. > ArrayIndexOutOfBoundsExceptio

[jira] Updated: (OPENJPA-1480) time zone info lost when using timestamp field

[ https://issues.apache.org/jira/browse/OPENJPA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1480: --- Attachment: OPENJPA-1480-TestCalendarField.patch > time zone info lost when using timestamp field >

[jira] Updated: (OPENJPA-1480) time zone info lost when using timestamp field

[ https://issues.apache.org/jira/browse/OPENJPA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1480: --- Attachment: (was: OPENJPA-1480-TestCalendarField.patch) > time zone info lost when using timest

[jira] Updated: (OPENJPA-1480) time zone info lost when using timestamp field

[ https://issues.apache.org/jira/browse/OPENJPA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1480: --- Attachment: 1280-1.2.x.patch Uploading 1280-1.2.x.patch. This patch contains a one line code chang

[jira] Updated: (OPENJPA-1480) time zone info lost when using timestamp field

[ https://issues.apache.org/jira/browse/OPENJPA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1480: --- Attachment: OPENJPA-1480-TestCalendarField.patch improvement for the TestCalendarField test case.

[jira] Commented: (OPENJPA-1480) time zone info lost when using timestamp field

[ https://issues.apache.org/jira/browse/OPENJPA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805654#action_12805654 ] B.J. Reed commented on OPENJPA-1480: DBDictionary.getCalendarI() is used to get the C

[jira] Commented: (OPENJPA-1480) time zone info lost when using timestamp field

[ https://issues.apache.org/jira/browse/OPENJPA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803869#action_12803869 ] B.J. Reed commented on OPENJPA-1480: In DB2, it's stored as TIMESTAMP. > time zone i

[jira] Updated: (OPENJPA-1480) time zone info lost when using timestamp field

[ https://issues.apache.org/jira/browse/OPENJPA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1480: --- Attachment: TZDataModel.java TestTimeZone.java > time zone info lost when using tim

[jira] Created: (OPENJPA-1480) time zone info lost when using timestamp field

time zone info lost when using timestamp field -- Key: OPENJPA-1480 URL: https://issues.apache.org/jira/browse/OPENJPA-1480 Project: OpenJPA Issue Type: Bug Components: jdbc Affects V

[jira] Updated: (OPENJPA-1001) java.lang.IndexOutOfBoundsException when executing attached test case

[ https://issues.apache.org/jira/browse/OPENJPA-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1001: --- Attachment: OPENJPA-1001.patch This issue has been fixed in trunk with OPENJPA-703 revision 739123.

[jira] Updated: (OPENJPA-1384) ClassNotFoundException for custom DBDictionary used by EJB

[ https://issues.apache.org/jira/browse/OPENJPA-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1384: --- Attachment: OPENJPA-1384.patch In the DBDictionaryFactory.newDBDictionary method, OpenJPA tries to

[jira] Created: (OPENJPA-1384) ClassNotFoundException for custom DBDictionary used by EJB

ClassNotFoundException for custom DBDictionary used by EJB -- Key: OPENJPA-1384 URL: https://issues.apache.org/jira/browse/OPENJPA-1384 Project: OpenJPA Issue Type: Bug Compon

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: OPENJPA-1308-trunk.patch OPENJPA-1308-1.2.x.patch OPENJP

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: (was: OPENJPA-1308-1.0.x.patch) > shouldn't always use CAST with UPPER and LOWER fo

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: (was: OPENJPA-1308-1.2.x.patch) > shouldn't always use CAST with UPPER and LOWER fo

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: (was: OPENJPA-1308-trunk.patch) > shouldn't always use CAST with UPPER and LOWER fo

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: (was: OPENJPA-1308-1.0.x.patch) > shouldn't always use CAST with UPPER and LOWER fo

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: (was: OPENJPA-1308-trunk.patch) > shouldn't always use CAST with UPPER and LOWER fo

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: (was: OPENJPA-1308-1.2.x.patch) > shouldn't always use CAST with UPPER and LOWER fo

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: OPENJPA-1308-1.0.x.patch OPENJPA-1308-1.2.x.patch OPENJP

[jira] Updated: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

[ https://issues.apache.org/jira/browse/OPENJPA-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1308: --- Attachment: OPENJPA-1308-trunk.patch OPENJPA-1308-1.2.x.patch OPENJP

[jira] Commented: (OPENJPA-1326) ReverseMappingTool and SchemaTool failing for Sybase

[ https://issues.apache.org/jira/browse/OPENJPA-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759185#action_12759185 ] B.J. Reed commented on OPENJPA-1326: Thanks for the suggestions. We already had BE_A

[jira] Commented: (OPENJPA-1326) ReverseMappingTool and SchemaTool failing for Sybase

[ https://issues.apache.org/jira/browse/OPENJPA-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758742#action_12758742 ] B.J. Reed commented on OPENJPA-1326: Forgot to mention, I have not tried this on trun

[jira] Updated: (OPENJPA-1326) ReverseMappingTool and SchemaTool failing for Sybase

[ https://issues.apache.org/jira/browse/OPENJPA-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1326: --- Attachment: OPENJPA-1326.patch > ReverseMappingTool and SchemaTool failing for Sybase > ---

[jira] Created: (OPENJPA-1326) ReverseMappingTool and SchemaTool failing for Sybase

ReverseMappingTool and SchemaTool failing for Sybase Key: OPENJPA-1326 URL: https://issues.apache.org/jira/browse/OPENJPA-1326 Project: OpenJPA Issue Type: Bug Components: sql

[jira] Created: (OPENJPA-1308) shouldn't always use CAST with UPPER and LOWER for DB2

shouldn't always use CAST with UPPER and LOWER for DB2 -- Key: OPENJPA-1308 URL: https://issues.apache.org/jira/browse/OPENJPA-1308 Project: OpenJPA Issue Type: Improvement Compon

[jira] Updated: (OPENJPA-466) Primary key constraint violated using (Oracle) sequence to generate ID in multithreaded app

[ https://issues.apache.org/jira/browse/OPENJPA-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-466: -- Attachment: OPENJPA-466-1.2.x.patch OPENJPA-466-1.0.x.patch Attached 2 patches to port

[jira] Updated: (OPENJPA-645) Date millisecond precision lost for Informix IDS and SQLServer

[ https://issues.apache.org/jira/browse/OPENJPA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-645: -- Attachment: OPENJPA-645-1.0.x.patch In 1.0.x, SQL Server has already been updated to allow the fractio

[jira] Assigned: (OPENJPA-1141) NPE at org.apache.openjpa.jdbc.meta.MappingInfo.mergeJoinColumn(MappingInfo.java:1400)

[ https://issues.apache.org/jira/browse/OPENJPA-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed reassigned OPENJPA-1141: -- Assignee: (was: B.J. Reed) Can someone else take a look at this? I had only agreed origi

[jira] Updated: (OPENJPA-1243) migrate Informix functionality from 1.2 to 1.0.x

[ https://issues.apache.org/jira/browse/OPENJPA-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1243: --- Attachment: OPENJPA-1243.patch.patch > migrate Informix functionality from 1.2 to 1.0.x > -

[jira] Created: (OPENJPA-1243) migrate Informix functionality from 1.2 to 1.0.x

migrate Informix functionality from 1.2 to 1.0.x Key: OPENJPA-1243 URL: https://issues.apache.org/jira/browse/OPENJPA-1243 Project: OpenJPA Issue Type: Bug Components: jdbc Affec

[jira] Commented: (OPENJPA-1141) NPE at org.apache.openjpa.jdbc.meta.MappingInfo.mergeJoinColumn(MappingInfo.java:1400)

[ https://issues.apache.org/jira/browse/OPENJPA-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734159#action_12734159 ] B.J. Reed commented on OPENJPA-1141: One thing I tried was playing around with the en

[jira] Updated: (OPENJPA-732) Updates to entities via Lifecycle callback methods

[ https://issues.apache.org/jira/browse/OPENJPA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-732: -- Attachment: (was: OPENJPA-732-1.2.patch) > Updates to entities via Lifecycle callback methods > -

[jira] Updated: (OPENJPA-732) Updates to entities via Lifecycle callback methods

[ https://issues.apache.org/jira/browse/OPENJPA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-732: -- Attachment: (was: OPENJPA-732-1.0.patch) > Updates to entities via Lifecycle callback methods > -

[jira] Updated: (OPENJPA-732) Updates to entities via Lifecycle callback methods

[ https://issues.apache.org/jira/browse/OPENJPA-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-732: -- Attachment: OPENJPA-732-1.2.patch OPENJPA-732-1.0.patch Patches broke some other test

[jira] Updated: (OPENJPA-327) EntityListener that modify property value of a entity, causes invalid state exception

[ https://issues.apache.org/jira/browse/OPENJPA-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-327: -- Attachment: OPENJPA327-1.0.patch OPENJPA327-1.2.patch This test case is working in tru

[jira] Updated: (OPENJPA-1154) use of getFetchPlan().setMaxDepth(x) puts DISTINCT in the SQL

[ https://issues.apache.org/jira/browse/OPENJPA-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1154: --- Attachment: TestFetchPlanDepth.java > use of getFetchPlan().setMaxDepth(x) puts DISTINCT in the SQL

[jira] Created: (OPENJPA-1154) use of getFetchPlan().setMaxDepth(x) puts DISTINCT in the SQL

use of getFetchPlan().setMaxDepth(x) puts DISTINCT in the SQL - Key: OPENJPA-1154 URL: https://issues.apache.org/jira/browse/OPENJPA-1154 Project: OpenJPA Issue Type: Improvement

[jira] Updated: (OPENJPA-976) Research the need for escape charaters for LIKE in various DB's

[ https://issues.apache.org/jira/browse/OPENJPA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-976: -- Patch Info: [Patch Available] > Research the need for escape charaters for LIKE in various DB's >

[jira] Updated: (OPENJPA-247) new-delete-new-find doesn't work

[ https://issues.apache.org/jira/browse/OPENJPA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-247: -- Patch Info: [Patch Available] > new-delete-new-find doesn't work > >

[jira] Updated: (OPENJPA-1026) Ensure newlines at end of fie

[ https://issues.apache.org/jira/browse/OPENJPA-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1026: --- Patch Info: [Patch Available] > Ensure newlines at end of fie > - > >

[jira] Updated: (OPENJPA-526) Insert text more than 4K bytes to Clob column causes SQLException: Exhausted Resultset

[ https://issues.apache.org/jira/browse/OPENJPA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-526: -- Patch Info: [Patch Available] > Insert text more than 4K bytes to Clob column causes SQLException: Exh

[jira] Updated: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

[ https://issues.apache.org/jira/browse/OPENJPA-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-922: -- Patch Info: [Patch Available] > setByteArrayInputStream being used in stead of setBytes >

[jira] Updated: (OPENJPA-1066) Generated ID starting with 0 can cause unexpected results

[ https://issues.apache.org/jira/browse/OPENJPA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1066: --- Attachment: GeneratedIDStartsWith0.ZIP > Generated ID starting with 0 can cause unexpected results

[jira] Created: (OPENJPA-1066) Generated ID starting with 0 can cause unexpected results

Generated ID starting with 0 can cause unexpected results - Key: OPENJPA-1066 URL: https://issues.apache.org/jira/browse/OPENJPA-1066 Project: OpenJPA Issue Type: Improvement

[jira] Updated: (OPENJPA-1058) Duplicate rows in DB when UniqueConstraint set

[ https://issues.apache.org/jira/browse/OPENJPA-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1058: --- Attachment: DupRowsInDB.ZIP > Duplicate rows in DB when UniqueConstraint set >

[jira] Created: (OPENJPA-1058) Duplicate rows in DB when UniqueConstraint set

Duplicate rows in DB when UniqueConstraint set -- Key: OPENJPA-1058 URL: https://issues.apache.org/jira/browse/OPENJPA-1058 Project: OpenJPA Issue Type: Bug Components: jdbc Affects V

[jira] Commented: (OPENJPA-1018) @PreUpdate raised for new entities annotated with @EntityListeners

[ https://issues.apache.org/jira/browse/OPENJPA-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703325#action_12703325 ] B.J. Reed commented on OPENJPA-1018: I made the suggested code change, but that has b

[jira] Updated: (OPENJPA-1025) AbstractResultList.subList throws UnsupportedOperationException

[ https://issues.apache.org/jira/browse/OPENJPA-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1025: --- Attachment: OPENJPA-1025-withTest.patch OPENJPA-1025-withTest.patch includes the code changes from

[jira] Updated: (OPENJPA-1025) AbstractResultList.subList throws UnsupportedOperationException

[ https://issues.apache.org/jira/browse/OPENJPA-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1025: --- Attachment: OPENJPA-1025b.patch Thanks for the quick review Julien. Attaching OPENJPA-1025b.patch.

[jira] Updated: (OPENJPA-1025) AbstractResultList.subList throws UnsupportedOperationException

[ https://issues.apache.org/jira/browse/OPENJPA-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1025: --- Attachment: OPENJPA-1025.patch Attaching patch OPENJPA-1025.patch. Update AbstractResultList to no

[jira] Commented: (OPENJPA-206) Key column does not cascade multiple joins.

[ https://issues.apache.org/jira/browse/OPENJPA-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700164#action_12700164 ] B.J. Reed commented on OPENJPA-206: --- I've been able to reproduce this on the current tru

[jira] Updated: (OPENJPA-1026) Ensure newlines at end of fie

[ https://issues.apache.org/jira/browse/OPENJPA-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1026: --- Attachment: OPENJPA-1026-newlineendoffile.patch attaching new patch for trunk. This includes src/ma

[jira] Updated: (OPENJPA-1015) Enforce 80-column line width for source code

[ https://issues.apache.org/jira/browse/OPENJPA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1015: --- Attachment: OPENJPA-1015-test.patch Attaching very large OPENJPA-1015-test patch. patch fixes all

[jira] Commented: (OPENJPA-976) Research the need for escape charaters for LIKE in various DB's

[ https://issues.apache.org/jira/browse/OPENJPA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696070#action_12696070 ] B.J. Reed commented on OPENJPA-976: --- Thanks Milosz, I went through 4 DBs when testing t

[jira] Updated: (OPENJPA-976) Research the need for escape charaters for LIKE in various DB's

[ https://issues.apache.org/jira/browse/OPENJPA-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-976: -- Attachment: OPENJPA-976.patch Attaching patch to get the escape string from each database in stead of

[jira] Updated: (OPENJPA-1015) Enforce 80-column line width for source code

[ https://issues.apache.org/jira/browse/OPENJPA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1015: --- Attachment: OPENJPA-1015-newlineendoffile.patch The OPENJPA-1015-newlineendoffile.patch file is to

[jira] Updated: (OPENJPA-1015) Enforce 80-column line width for source code

[ https://issues.apache.org/jira/browse/OPENJPA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-1015: --- Attachment: OPENJPA-1015-max80chars.patch Attaching OPENJPA-1015-max80chars.patch. This is the fir

[jira] Assigned: (OPENJPA-1015) Enforce 80-column line width for source code

[ https://issues.apache.org/jira/browse/OPENJPA-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed reassigned OPENJPA-1015: -- Assignee: B.J. Reed I don't mind taking a crack at this using the maven-checkstyle-plugin. I

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: OPENJPA-975-trunk.patch trunk patch contains document change and code change. Does not al

[jira] Resolved: (OPENJPA-354) DB2 casts might not incorporate VARCHAR lengths often enough

[ https://issues.apache.org/jira/browse/OPENJPA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed resolved OPENJPA-354. --- Resolution: Fixed Fix Version/s: 1.1.0 I've looked through the patch and it looks like this c

[jira] Closed: (OPENJPA-289) Setting a parameter in a bulk update with a value of type Enum throws an exception

[ https://issues.apache.org/jira/browse/OPENJPA-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed closed OPENJPA-289. - Resolution: Fixed Fix Version/s: 1.1.0 This issue was fixed for the 1.1 release of OpenJPA. A te

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: (was: OPENJPA-975b.patch) > Oracle needs ability to not have an escape character for s

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: OPENJPA-975c.patch It appears that most DB's do want the escape character by default, Orac

[jira] Updated: (OPENJPA-526) Insert text more than 4K bytes to Clob column causes SQLException: Exhausted Resultset

[ https://issues.apache.org/jira/browse/OPENJPA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-526: -- Attachment: OPENJPA-526.patch The code that is changed fixes 2 Oracle test problems with non nullable

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: (was: OPENJPA-975b.patch) > Oracle needs ability to not have an escape character for s

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: OPENJPA-975b.patch > Oracle needs ability to not have an escape character for search strin

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: OPENJPA-975doc.patch OPENJPA-975doc.patch is the update to the documentation for this new

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: (was: OPENJPA-975.patch) > Oracle needs ability to not have an escape character for se

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: OPENJPA-975b.patch Thanks Milosz for the review. I had noticed all the "required" propert

[jira] Created: (OPENJPA-976) Research the need for escape charaters for LIKE in various DB's

Research the need for escape charaters for LIKE in various DB's --- Key: OPENJPA-976 URL: https://issues.apache.org/jira/browse/OPENJPA-976 Project: OpenJPA Issue Type: Improvement

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: (was: OPENJPA-975.patch) > Oracle needs ability to not have an escape character for se

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: OPENJPA-975.patch > Oracle needs ability to not have an escape character for search string

[jira] Updated: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

[ https://issues.apache.org/jira/browse/OPENJPA-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-975: -- Attachment: OPENJPA-975.patch Attached patch has a new field in the DBDictionary: alwaysAddSearchStrin

[jira] Created: (OPENJPA-975) Oracle needs ability to not have an escape character for search strings.

Oracle needs ability to not have an escape character for search strings. Key: OPENJPA-975 URL: https://issues.apache.org/jira/browse/OPENJPA-975 Project: OpenJPA Issue

[jira] Updated: (OPENJPA-247) new-delete-new-find doesn't work

[ https://issues.apache.org/jira/browse/OPENJPA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-247: -- Attachment: OPENJPA-247.patch Patch contains a new test case for org.apache.openjpa.persistence.simpl

[jira] Updated: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

[ https://issues.apache.org/jira/browse/OPENJPA-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-922: -- Attachment: (was: OPENJPA-922-B.patch) > setByteArrayInputStream being used in stead of setBytes >

[jira] Updated: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

[ https://issues.apache.org/jira/browse/OPENJPA-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-922: -- Attachment: OPENJPA-922-C.patch Thanks Milosz. I was so worried about the fix not breaking other DBs

[jira] Updated: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

[ https://issues.apache.org/jira/browse/OPENJPA-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-922: -- Attachment: (was: OPENJPA-922.patch) > setByteArrayInputStream being used in stead of setBytes > -

[jira] Updated: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

[ https://issues.apache.org/jira/browse/OPENJPA-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-922: -- Attachment: OPENJPA-922-B.patch I have attached OPENJPA-922-B.patch as a second attempt to fix this pr

[jira] Resolved: (OPENJPA-247) new-delete-new-find doesn't work

[ https://issues.apache.org/jira/browse/OPENJPA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed resolved OPENJPA-247. --- Resolution: Cannot Reproduce I have tried re-creating this problem on trunk (2.0) and 1.2, so it loo

[jira] Commented: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

[ https://issues.apache.org/jira/browse/OPENJPA-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676403#action_12676403 ] B.J. Reed commented on OPENJPA-922: --- Was premature with the patch. The "fix" breaks BLO

[jira] Updated: (OPENJPA-918) Stored procedures not handling returns properly

[ https://issues.apache.org/jira/browse/OPENJPA-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-918: -- Attachment: TORC.patch I've narrowed the problem down a little further. Not sure if this is something

[jira] Commented: (OPENJPA-918) Stored procedures not handling returns properly

[ https://issues.apache.org/jira/browse/OPENJPA-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674218#action_12674218 ] B.J. Reed commented on OPENJPA-918: --- Thanks Craig for the info. I'll remove the last tw

[jira] Updated: (OPENJPA-918) Stored procedures not handling returns properly

[ https://issues.apache.org/jira/browse/OPENJPA-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-918: -- Attachment: OPENJPA-918-test.patch After futher testing... It appears that procedures that return no

[jira] Updated: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

[ https://issues.apache.org/jira/browse/OPENJPA-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-922: -- Attachment: OPENJPA-922.patch For DB2, the DBDictionary useSetBytesForBlobs field is set to false. Wi

[jira] Created: (OPENJPA-922) setByteArrayInputStream being used in stead of setBytes

setByteArrayInputStream being used in stead of setBytes --- Key: OPENJPA-922 URL: https://issues.apache.org/jira/browse/OPENJPA-922 Project: OpenJPA Issue Type: Bug Affects Versions: 1.

[jira] Commented: (OPENJPA-895) InternalException when querying entity that participates in both inheritance and relationships

[ https://issues.apache.org/jira/browse/OPENJPA-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673400#action_12673400 ] B.J. Reed commented on OPENJPA-895: --- I haven't figured the root cause yet, but one way a

[jira] Created: (OPENJPA-918) Stored procedures not handling returns properly

Stored procedures not handling returns properly --- Key: OPENJPA-918 URL: https://issues.apache.org/jira/browse/OPENJPA-918 Project: OpenJPA Issue Type: New Feature Components: query

[jira] Updated: (OPENJPA-917) stored procedures throw InvalidStateException when using getSingleResult() or getResultList()

[ https://issues.apache.org/jira/browse/OPENJPA-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated OPENJPA-917: -- Attachment: OPENJPA-917.patch This patch updates QueryImpl.java to bypass the InvalidStateException wh

[jira] Created: (OPENJPA-917) stored procedures throw InvalidStateException when using getSingleResult() or getResultList()

stored procedures throw InvalidStateException when using getSingleResult() or getResultList() - Key: OPENJPA-917 URL: https://issues.apache.org/jira/browse/OPENJPA-917