[jira] [Resolved] (OPENJPA-2922) disable JNDI lookup in OpenJPAPersistence by default

[ https://issues.apache.org/jira/browse/OPENJPA-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2922. Resolution: Fixed > disable JNDI lookup in OpenJPAPersistence by default >

[jira] [Created] (OPENJPA-2922) disable JNDI lookup in OpenJPAPersistence by default

Mark Struberg created OPENJPA-2922: -- Summary: disable JNDI lookup in OpenJPAPersistence by default Key: OPENJPA-2922 URL: https://issues.apache.org/jira/browse/OPENJPA-2922 Project: OpenJPA

[jira] [Resolved] (OPENJPA-2921) upgrade bundle and karaf plugins to fix java17 build

[ https://issues.apache.org/jira/browse/OPENJPA-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2921. Resolution: Fixed > upgrade bundle and karaf plugins to fix java17 build >

[jira] [Created] (OPENJPA-2921) upgrade bundle and karaf plugins to fix java17 build

Mark Struberg created OPENJPA-2921: -- Summary: upgrade bundle and karaf plugins to fix java17 build Key: OPENJPA-2921 URL: https://issues.apache.org/jira/browse/OPENJPA-2921 Project: OpenJPA

[jira] [Resolved] (OPENJPA-2917) Subclass enhancement might fail on long fields

[ https://issues.apache.org/jira/browse/OPENJPA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2917. Resolution: Fixed > Subclass enhancement might fail on long fields >

[jira] [Created] (OPENJPA-2917) Subclass enhancement might fail on long fields

Mark Struberg created OPENJPA-2917: -- Summary: Subclass enhancement might fail on long fields Key: OPENJPA-2917 URL: https://issues.apache.org/jira/browse/OPENJPA-2917 Project: OpenJPA Issue

[jira] [Assigned] (OPENJPA-2915) commons-dbcp2 2.10.0 breaks OpenJPA because of changed configuration methods

[ https://issues.apache.org/jira/browse/OPENJPA-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2915: -- Assignee: Mark Struberg > commons-dbcp2 2.10.0 breaks OpenJPA because of changed

[jira] [Resolved] (OPENJPA-2914) upgrade xbean to 4.23

[ https://issues.apache.org/jira/browse/OPENJPA-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2914. Resolution: Fixed > upgrade xbean to 4.23 > - > >

[jira] [Created] (OPENJPA-2914) upgrade xbean to 4.23

Mark Struberg created OPENJPA-2914: -- Summary: upgrade xbean to 4.23 Key: OPENJPA-2914 URL: https://issues.apache.org/jira/browse/OPENJPA-2914 Project: OpenJPA Issue Type: Improvement

[jira] [Resolved] (OPENJPA-2911) Replace Serp with native ASM code

[ https://issues.apache.org/jira/browse/OPENJPA-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2911. Resolution: Fixed We finally got rid of Serp and moved all the parts to Geronimo

[jira] [Created] (OPENJPA-2912) Support jdk.attach.jmod in InstrumentationFactory

Mark Struberg created OPENJPA-2912: -- Summary: Support jdk.attach.jmod in InstrumentationFactory Key: OPENJPA-2912 URL: https://issues.apache.org/jira/browse/OPENJPA-2912 Project: OpenJPA

[jira] [Created] (OPENJPA-2911) Replace Serp with native ASM code

Mark Struberg created OPENJPA-2911: -- Summary: Replace Serp with native ASM code Key: OPENJPA-2911 URL: https://issues.apache.org/jira/browse/OPENJPA-2911 Project: OpenJPA Issue Type:

[jira] [Resolved] (OPENJPA-2909) implement field proxies with ASM instead Serp

[ https://issues.apache.org/jira/browse/OPENJPA-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2909. Resolution: Fixed > implement field proxies with ASM instead Serp >

[jira] [Resolved] (OPENJPA-2910) implement WASManagedRuntime witout Serp

[ https://issues.apache.org/jira/browse/OPENJPA-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2910. Resolution: Fixed > implement WASManagedRuntime witout Serp >

[jira] [Created] (OPENJPA-2910) implement WASManagedRuntime witout Serp

Mark Struberg created OPENJPA-2910: -- Summary: implement WASManagedRuntime witout Serp Key: OPENJPA-2910 URL: https://issues.apache.org/jira/browse/OPENJPA-2910 Project: OpenJPA Issue Type:

[jira] [Created] (OPENJPA-2909) implement field proxies with ASM instead Serp

Mark Struberg created OPENJPA-2909: -- Summary: implement field proxies with ASM instead Serp Key: OPENJPA-2909 URL: https://issues.apache.org/jira/browse/OPENJPA-2909 Project: OpenJPA Issue

[jira] [Created] (OPENJPA-2908) implement Jakarta JPA 3.1

Mark Struberg created OPENJPA-2908: -- Summary: implement Jakarta JPA 3.1 Key: OPENJPA-2908 URL: https://issues.apache.org/jira/browse/OPENJPA-2908 Project: OpenJPA Issue Type: Improvement

[jira] [Resolved] (OPENJPA-2614) First rollback after application start does not work under certain circumstances

[ https://issues.apache.org/jira/browse/OPENJPA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2614. Fix Version/s: 3.2.1 Assignee: Mark Struberg Resolution: Fixed We now do

[jira] [Resolved] (OPENJPA-2869) Specification-Version still in v2

[ https://issues.apache.org/jira/browse/OPENJPA-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2869. Fix Version/s: 3.2.0 Assignee: Mark Struberg Resolution: Fixed fixed

[jira] [Closed] (OPENJPA-2869) Specification-Version still in v2

[ https://issues.apache.org/jira/browse/OPENJPA-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed OPENJPA-2869. -- > Specification-Version still in v2 > - > > Key:

[jira] [Resolved] (OPENJPA-2876) running 'refresh' schema action creates wrong SQL output

[ https://issues.apache.org/jira/browse/OPENJPA-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2876. Resolution: Fixed > running 'refresh' schema action creates wrong SQL output >

[jira] [Commented] (OPENJPA-2876) running 'refresh' schema action creates wrong SQL output

[ https://issues.apache.org/jira/browse/OPENJPA-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361204#comment-17361204 ] Mark Struberg commented on OPENJPA-2876: git-bisect tells us it was commit

[jira] [Created] (OPENJPA-2876) running 'refresh' schema action creates wrong SQL output

Mark Struberg created OPENJPA-2876: -- Summary: running 'refresh' schema action creates wrong SQL output Key: OPENJPA-2876 URL: https://issues.apache.org/jira/browse/OPENJPA-2876 Project: OpenJPA

[jira] [Resolved] (OPENJPA-2873) Add ProductDerivation for persistence_2_2.xsd

[ https://issues.apache.org/jira/browse/OPENJPA-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2873. Resolution: Fixed > Add ProductDerivation for persistence_2_2.xsd >

[jira] [Resolved] (OPENJPA-2765) Fix documentation of JPA spec compliance

[ https://issues.apache.org/jira/browse/OPENJPA-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2765. Resolution: Fixed > Fix documentation of JPA spec compliance >

[jira] [Updated] (OPENJPA-2873) Add ProductDerivation for persistence_2_2.xsd

[ https://issues.apache.org/jira/browse/OPENJPA-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2873: --- Description: Add ProductDerivation for persistence_2_2.xsd. Right now we only support

[jira] [Created] (OPENJPA-2873) Add ProductDerivation for persistence_2_2.xsd

Mark Struberg created OPENJPA-2873: -- Summary: Add ProductDerivation for persistence_2_2.xsd Key: OPENJPA-2873 URL: https://issues.apache.org/jira/browse/OPENJPA-2873 Project: OpenJPA Issue

[jira] [Updated] (OPENJPA-2873) Add ProductDerivation for persistence_2_2.xsd

[ https://issues.apache.org/jira/browse/OPENJPA-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2873: --- Fix Version/s: 3.2.0 > Add ProductDerivation for persistence_2_2.xsd >

[jira] [Updated] (OPENJPA-2873) Add ProductDerivation for persistence_2_2.xsd

[ https://issues.apache.org/jira/browse/OPENJPA-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2873: --- Affects Version/s: (was: 3.1.2) > Add ProductDerivation for persistence_2_2.xsd >

[jira] [Resolved] (OPENJPA-2872) provide Jakarta EE artifacts

[ https://issues.apache.org/jira/browse/OPENJPA-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2872. Fix Version/s: (was: 3.2.0) 3.1.2 Resolution: Duplicate

[jira] [Created] (OPENJPA-2872) provide Jakarta EE artifacts

Mark Struberg created OPENJPA-2872: -- Summary: provide Jakarta EE artifacts Key: OPENJPA-2872 URL: https://issues.apache.org/jira/browse/OPENJPA-2872 Project: OpenJPA Issue Type: New Feature

[jira] [Assigned] (OPENJPA-2765) Fix documentation of JPA spec compliance

[ https://issues.apache.org/jira/browse/OPENJPA-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2765: -- Assignee: Mark Struberg > Fix documentation of JPA spec compliance >

[jira] [Updated] (OPENJPA-2765) Fix documentation of JPA spec compliance

[ https://issues.apache.org/jira/browse/OPENJPA-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2765: --- Fix Version/s: 3.2.0 > Fix documentation of JPA spec compliance >

[jira] [Resolved] (OPENJPA-2868) update reserved column names list for various of our DBDictionaries

[ https://issues.apache.org/jira/browse/OPENJPA-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2868. Resolution: Fixed > update reserved column names list for various of our DBDictionaries

[jira] [Updated] (OPENJPA-2837) HerdDBDictionary does not work with 'native' SchemaFactory (LazySchemaFactory) - set useSchemaName=false by default

[ https://issues.apache.org/jira/browse/OPENJPA-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2837: --- Fix Version/s: (was: 3.2.0) 3.2.1 > HerdDBDictionary does not work

[jira] [Resolved] (OPENJPA-2871) upgrade to xbean-4.20 to remove transitive ASM dependency

[ https://issues.apache.org/jira/browse/OPENJPA-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2871. Resolution: Fixed > upgrade to xbean-4.20 to remove transitive ASM dependency >

[jira] [Created] (OPENJPA-2871) upgrade to xbean-4.20 to remove transitive ASM dependency

Mark Struberg created OPENJPA-2871: -- Summary: upgrade to xbean-4.20 to remove transitive ASM dependency Key: OPENJPA-2871 URL: https://issues.apache.org/jira/browse/OPENJPA-2871 Project: OpenJPA

[jira] [Resolved] (OPENJPA-2870) update specification-version to 2.2

[ https://issues.apache.org/jira/browse/OPENJPA-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2870. Resolution: Fixed > update specification-version to 2.2 >

[jira] [Created] (OPENJPA-2870) update specification-version to 2.2

Mark Struberg created OPENJPA-2870: -- Summary: update specification-version to 2.2 Key: OPENJPA-2870 URL: https://issues.apache.org/jira/browse/OPENJPA-2870 Project: OpenJPA Issue Type:

[jira] [Resolved] (OPENJPA-2867) generate list of reserved Words via unit test

[ https://issues.apache.org/jira/browse/OPENJPA-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2867. Resolution: Fixed > generate list of reserved Words via unit test >

[jira] [Created] (OPENJPA-2868) update reserved column names list for various of our DBDictionaries

Mark Struberg created OPENJPA-2868: -- Summary: update reserved column names list for various of our DBDictionaries Key: OPENJPA-2868 URL: https://issues.apache.org/jira/browse/OPENJPA-2868 Project:

[jira] [Created] (OPENJPA-2867) generate list of reserved Words via unit test

Mark Struberg created OPENJPA-2867: -- Summary: generate list of reserved Words via unit test Key: OPENJPA-2867 URL: https://issues.apache.org/jira/browse/OPENJPA-2867 Project: OpenJPA Issue

[jira] [Commented] (OPENJPA-2808) SchemaTool action DROP doesn't drop Indexes created with @Index

[ https://issues.apache.org/jira/browse/OPENJPA-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330072#comment-17330072 ] Mark Struberg commented on OPENJPA-2808: Is it ok to move this to 3.2.1? We need to take a

[jira] [Commented] (OPENJPA-2808) SchemaTool action DROP doesn't drop Indexes created with @Index

[ https://issues.apache.org/jira/browse/OPENJPA-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329451#comment-17329451 ] Mark Struberg commented on OPENJPA-2808: Hi [~solomax] ! While creating a unit test for this

[jira] [Assigned] (OPENJPA-2841) Broken superfluous joins with subqueries

[ https://issues.apache.org/jira/browse/OPENJPA-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2841: -- Assignee: Mark Struberg > Broken superfluous joins with subqueries >

[jira] [Resolved] (OPENJPA-2800) StateManager field in enhanced entities are not "synthetic"

[ https://issues.apache.org/jira/browse/OPENJPA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2800. Resolution: Fixed > StateManager field in enhanced entities are not "synthetic" >

[jira] [Updated] (OPENJPA-2800) StateManager field in enhanced entities are not "synthetic"

[ https://issues.apache.org/jira/browse/OPENJPA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2800: --- Fix Version/s: 3.1.3 > StateManager field in enhanced entities are not "synthetic" >

[jira] [Work started] (OPENJPA-2800) StateManager field in enhanced entities are not "synthetic"

[ https://issues.apache.org/jira/browse/OPENJPA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OPENJPA-2800 started by Mark Struberg. -- > StateManager field in enhanced entities are not "synthetic" >

[jira] [Comment Edited] (OPENJPA-2789) JDBC connection not closed when running named query in explicitly opened connection

[ https://issues.apache.org/jira/browse/OPENJPA-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17324608#comment-17324608 ] Mark Struberg edited comment on OPENJPA-2789 at 4/18/21, 9:17 PM: -- txs

[jira] [Resolved] (OPENJPA-2789) JDBC connection not closed when running named query in explicitly opened connection

[ https://issues.apache.org/jira/browse/OPENJPA-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2789. Resolution: Fixed txs for the report! I did enable the 'old' behaviour which closed the

[jira] [Commented] (OPENJPA-2865) [Oracle] use native java.time JDBC features

[ https://issues.apache.org/jira/browse/OPENJPA-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17324554#comment-17324554 ] Mark Struberg commented on OPENJPA-2865: fine, closing it then. > [Oracle] use native

[jira] [Resolved] (OPENJPA-2865) [Oracle] use native java.time JDBC features

[ https://issues.apache.org/jira/browse/OPENJPA-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2865. Resolution: Fixed > [Oracle] use native java.time JDBC features >

[jira] [Commented] (OPENJPA-2865) [Oracle] use native java.time JDBC features

[ https://issues.apache.org/jira/browse/OPENJPA-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17324473#comment-17324473 ] Mark Struberg commented on OPENJPA-2865: [~rmannibucau] [~ilgrosso] wdyt? should we change the

[jira] [Resolved] (OPENJPA-2866) [Oracle] add GenerationType#IDENTITY support for Oracle

[ https://issues.apache.org/jira/browse/OPENJPA-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2866. Resolution: Fixed > [Oracle] add GenerationType#IDENTITY support for Oracle >

[jira] [Commented] (OPENJPA-2865) [Oracle] use native java.time JDBC features

[ https://issues.apache.org/jira/browse/OPENJPA-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17318550#comment-17318550 ] Mark Struberg commented on OPENJPA-2865: the only question left is how to treat

[jira] [Created] (OPENJPA-2866) [Oracle] add GenerationType#IDENTITY support for Oracle

Mark Struberg created OPENJPA-2866: -- Summary: [Oracle] add GenerationType#IDENTITY support for Oracle Key: OPENJPA-2866 URL: https://issues.apache.org/jira/browse/OPENJPA-2866 Project: OpenJPA

[jira] [Created] (OPENJPA-2865) [Oracle] use native java.time JDBC features

Mark Struberg created OPENJPA-2865: -- Summary: [Oracle] use native java.time JDBC features Key: OPENJPA-2865 URL: https://issues.apache.org/jira/browse/OPENJPA-2865 Project: OpenJPA Issue

[jira] [Resolved] (OPENJPA-2864) respect the Columns precision when persisting a java.sql.Timestamp value

[ https://issues.apache.org/jira/browse/OPENJPA-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2864. Resolution: Fixed > respect the Columns precision when persisting a java.sql.Timestamp

[jira] [Resolved] (OPENJPA-2863) java.time.LocalDateTime in Oracle gets rounded to just 3 digits

[ https://issues.apache.org/jira/browse/OPENJPA-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2863. Fix Version/s: 3.1.3 Resolution: Fixed > java.time.LocalDateTime in Oracle gets

[jira] [Created] (OPENJPA-2864) respect the Columns precision when persisting a java.sql.Timestamp value

Mark Struberg created OPENJPA-2864: -- Summary: respect the Columns precision when persisting a java.sql.Timestamp value Key: OPENJPA-2864 URL: https://issues.apache.org/jira/browse/OPENJPA-2864

[jira] [Commented] (OPENJPA-2863) java.time.LocalDateTime in Oracle gets rounded to just 3 digits

[ https://issues.apache.org/jira/browse/OPENJPA-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317158#comment-17317158 ] Mark Struberg commented on OPENJPA-2863: The constant {{LocalTime.MAX}} uses {{9}} for

[jira] [Updated] (OPENJPA-2863) java.time.LocalDateTime in Oracle gets rounded to just 3 digits

[ https://issues.apache.org/jira/browse/OPENJPA-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2863: --- Summary: java.time.LocalDateTime in Oracle gets rounded to just 3 digits (was:

[jira] [Assigned] (OPENJPA-2863) java.time.LocalDateTime at LocalTime.MAX in Oracle gets rounded to the next day atStartOfDay

[ https://issues.apache.org/jira/browse/OPENJPA-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2863: -- Assignee: Mark Struberg > java.time.LocalDateTime at LocalTime.MAX in Oracle gets

[jira] [Commented] (OPENJPA-2797) SynchronizedMapping does not detect existing sequence

[ https://issues.apache.org/jira/browse/OPENJPA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315983#comment-17315983 ] Mark Struberg commented on OPENJPA-2797: hi! does that sequence exist in another schema? we

[jira] [Updated] (OPENJPA-2789) JDBC connection not closed when running named query in explicitly opened connection

[ https://issues.apache.org/jira/browse/OPENJPA-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2789: --- Fix Version/s: 3.1.3 > JDBC connection not closed when running named query in explicitly

[jira] [Assigned] (OPENJPA-2789) JDBC connection not closed when running named query in explicitly opened connection

[ https://issues.apache.org/jira/browse/OPENJPA-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2789: -- Assignee: Mark Struberg > JDBC connection not closed when running named query in

[jira] [Commented] (OPENJPA-2800) StateManager field in enhanced entities are not "synthetic"

[ https://issues.apache.org/jira/browse/OPENJPA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315982#comment-17315982 ] Mark Struberg commented on OPENJPA-2800: [~elexx] do you want to try to ship a patch for it?

[jira] [Commented] (OPENJPA-2806) PESSIMISTIC_READ takes out exclusive lock on Postgres

[ https://issues.apache.org/jira/browse/OPENJPA-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315980#comment-17315980 ] Mark Struberg commented on OPENJPA-2806: Hi [~pveselov] That could have something to do that

[jira] [Updated] (OPENJPA-2806) PESSIMISTIC_READ takes out exclusive lock on Postgres

[ https://issues.apache.org/jira/browse/OPENJPA-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2806: --- Fix Version/s: 3.1.3 > PESSIMISTIC_READ takes out exclusive lock on Postgres >

[jira] [Assigned] (OPENJPA-2806) PESSIMISTIC_READ takes out exclusive lock on Postgres

[ https://issues.apache.org/jira/browse/OPENJPA-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2806: -- Assignee: Mark Struberg > PESSIMISTIC_READ takes out exclusive lock on Postgres >

[jira] [Resolved] (OPENJPA-2731) Problems with Boolean Representation with Postgres

[ https://issues.apache.org/jira/browse/OPENJPA-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2731. Fix Version/s: 3.1.3 Resolution: Fixed > Problems with Boolean Representation

[jira] [Resolved] (OPENJPA-2861) select sum(CASE x WHEN x THEN 1 ELSE 0 ) returns String instead of Long.

[ https://issues.apache.org/jira/browse/OPENJPA-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2861. Resolution: Fixed This was quite a nasty bug. I changed a lot of the Raw handling and

[jira] [Resolved] (OPENJPA-2862) select SUM doesn't return spec defined types

[ https://issues.apache.org/jira/browse/OPENJPA-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2862. Resolution: Fixed > select SUM doesn't return spec defined types >

[jira] [Created] (OPENJPA-2862) select SUM doesn't return spec defined types

Mark Struberg created OPENJPA-2862: -- Summary: select SUM doesn't return spec defined types Key: OPENJPA-2862 URL: https://issues.apache.org/jira/browse/OPENJPA-2862 Project: OpenJPA Issue

[jira] [Created] (OPENJPA-2861) select sum(CASE x WHEN x THEN 1 ELSE 0 ) returns String instead of Long.

Mark Struberg created OPENJPA-2861: -- Summary: select sum(CASE x WHEN x THEN 1 ELSE 0 ) returns String instead of Long. Key: OPENJPA-2861 URL: https://issues.apache.org/jira/browse/OPENJPA-2861

[jira] [Commented] (OPENJPA-2767) Incomplete ValueMapDiscriminatorStrategy cache

[ https://issues.apache.org/jira/browse/OPENJPA-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315102#comment-17315102 ] Mark Struberg commented on OPENJPA-2767: Hi [~dazeydev] I think this is finally resolved,

[jira] [Resolved] (OPENJPA-2860) [Postgres] use setQueryTimeout for PostgreSQL >= 10

[ https://issues.apache.org/jira/browse/OPENJPA-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2860. Resolution: Fixed {{supportsQueryTimeout}} is now enabled by default for PostgreSQL 10

[jira] [Created] (OPENJPA-2860) [Postgres] use setQueryTimeout for PostgreSQL >= 10

Mark Struberg created OPENJPA-2860: -- Summary: [Postgres] use setQueryTimeout for PostgreSQL >= 10 Key: OPENJPA-2860 URL: https://issues.apache.org/jira/browse/OPENJPA-2860 Project: OpenJPA

[jira] [Resolved] (OPENJPA-1594) Tests not handling new QueryTimeOut and LockTimeOut exceptions correctly

[ https://issues.apache.org/jira/browse/OPENJPA-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-1594. Fix Version/s: 3.1.3 Resolution: Fixed The tests do run for all Databases who has

[jira] [Assigned] (OPENJPA-1594) Tests not handling new QueryTimeOut and LockTimeOut exceptions correctly

[ https://issues.apache.org/jira/browse/OPENJPA-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-1594: -- Assignee: Mark Struberg > Tests not handling new QueryTimeOut and LockTimeOut

[jira] [Commented] (OPENJPA-2808) SchemaTool action DROP doesn't drop Indexes created with @Index

[ https://issues.apache.org/jira/browse/OPENJPA-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314689#comment-17314689 ] Mark Struberg commented on OPENJPA-2808: Hi [~solomax] I'd like to include this patch in

[jira] [Resolved] (OPENJPA-2665) refactore code to use more Java7 features.

[ https://issues.apache.org/jira/browse/OPENJPA-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2665. Resolution: Fixed > refactore code to use more Java7 features. >

[jira] [Resolved] (OPENJPA-2648) hsqldb @Id long create table as interger instead of bigint

[ https://issues.apache.org/jira/browse/OPENJPA-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2648. Fix Version/s: 3.1.3 Resolution: Fixed > hsqldb @Id long create table as interger

[jira] [Commented] (OPENJPA-2648) hsqldb @Id long create table as interger instead of bigint

[ https://issues.apache.org/jira/browse/OPENJPA-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314492#comment-17314492 ] Mark Struberg commented on OPENJPA-2648: there was indeed a mapping in the HSQLDictionary which

[jira] [Assigned] (OPENJPA-2648) hsqldb @Id long create table as interger instead of bigint

[ https://issues.apache.org/jira/browse/OPENJPA-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2648: -- Assignee: Mark Struberg > hsqldb @Id long create table as interger instead of

[jira] [Resolved] (OPENJPA-2859) [HSQLDB] HSQLDictionary wrongly maps double to NUMERIC without precision

[ https://issues.apache.org/jira/browse/OPENJPA-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2859. Resolution: Fixed > [HSQLDB] HSQLDictionary wrongly maps double to NUMERIC without

[jira] [Updated] (OPENJPA-2859) [HSQLDB] HSQLDictionary wrongly maps double to NUMERIC without precision

[ https://issues.apache.org/jira/browse/OPENJPA-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2859: --- Summary: [HSQLDB] HSQLDictionary wrongly maps double to NUMERIC without precision (was:

[jira] [Created] (OPENJPA-2859) [HSQLDB] HSQLDictionary wrongly maps double to NUMBER without precision

Mark Struberg created OPENJPA-2859: -- Summary: [HSQLDB] HSQLDictionary wrongly maps double to NUMBER without precision Key: OPENJPA-2859 URL: https://issues.apache.org/jira/browse/OPENJPA-2859

[jira] [Resolved] (OPENJPA-345) "openjpa" maven module has unnecessary dependencies on other openjpa modules

[ https://issues.apache.org/jira/browse/OPENJPA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-345. --- Resolution: Fixed resolved ages ago > "openjpa" maven module has unnecessary dependencies

[jira] [Resolved] (OPENJPA-2858) update dbcp2 to 2.8.0

[ https://issues.apache.org/jira/browse/OPENJPA-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2858. Resolution: Fixed > update dbcp2 to 2.8.0 > - > >

[jira] [Created] (OPENJPA-2858) update dbcp2 to 2.8.0

Mark Struberg created OPENJPA-2858: -- Summary: update dbcp2 to 2.8.0 Key: OPENJPA-2858 URL: https://issues.apache.org/jira/browse/OPENJPA-2858 Project: OpenJPA Issue Type: Bug

[jira] [Resolved] (OPENJPA-2857) [MariaDB] locking in some cases gets handled via sqlState 70100

[ https://issues.apache.org/jira/browse/OPENJPA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2857. Resolution: Fixed > [MariaDB] locking in some cases gets handled via sqlState 70100 >

[jira] [Resolved] (OPENJPA-2856) [MariaDB] improve TIME handling

[ https://issues.apache.org/jira/browse/OPENJPA-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2856. Resolution: Fixed > [MariaDB] improve TIME handling > --- >

[jira] [Created] (OPENJPA-2856) [MariaDB] improve TIME handling

Mark Struberg created OPENJPA-2856: -- Summary: [MariaDB] improve TIME handling Key: OPENJPA-2856 URL: https://issues.apache.org/jira/browse/OPENJPA-2856 Project: OpenJPA Issue Type: Bug

[jira] [Resolved] (OPENJPA-2851) argument CURRENT_DATE cannot handle java.time.LocalDateTime entity fields

[ https://issues.apache.org/jira/browse/OPENJPA-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2851. Fix Version/s: 3.1.3 Resolution: Fixed Hi Karl, please test with the latest

[jira] [Assigned] (OPENJPA-2851) argument CURRENT_DATE cannot handle java.time.LocalDateTime entity fields

[ https://issues.apache.org/jira/browse/OPENJPA-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned OPENJPA-2851: -- Assignee: Mark Struberg > argument CURRENT_DATE cannot handle

[jira] [Updated] (OPENJPA-2855) primary keys do no respect naming rules

[ https://issues.apache.org/jira/browse/OPENJPA-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated OPENJPA-2855: --- Description: Seems we broke primary key column naming when adding support for HerdDB.

[jira] [Created] (OPENJPA-2855) primary keys do no respect naming rules

Mark Struberg created OPENJPA-2855: -- Summary: primary keys do no respect naming rules Key: OPENJPA-2855 URL: https://issues.apache.org/jira/browse/OPENJPA-2855 Project: OpenJPA Issue Type:

[jira] [Resolved] (OPENJPA-2854) fix OffsetTime handling for PostgreSQL

[ https://issues.apache.org/jira/browse/OPENJPA-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2854. Resolution: Fixed > fix OffsetTime handling for PostgreSQL >

[jira] [Created] (OPENJPA-2854) fix OffsetTime handling for PostgreSQL

Mark Struberg created OPENJPA-2854: -- Summary: fix OffsetTime handling for PostgreSQL Key: OPENJPA-2854 URL: https://issues.apache.org/jira/browse/OPENJPA-2854 Project: OpenJPA Issue Type:

  1   2   3   4   5   6   7   >