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

[DISCUSS] next up 3.1.3 or 3.2.0?

Hi folks! We fixed a lot of tickets since the last release. Some of them also change/fix the behaviour slightly. There are a few main tickets which do not introduce a big change, but might very subtly break existing apps in very rare edge cases: * UnaryOp now respects the target type. For doing

[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&focusedCommentId=17324473#comment-17324473 ] Mark Struberg commented on OPENJPA-2865: [~rmannibucau] [~ilgrosso] wdyt? shoul

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

Mark, Il giorno dom 18 apr 2021 alle ore 12:31 Mark Struberg ha scritto: > > Hi folks! > > We fixed a lot of tickets since the last release. Some of them also > change/fix the behaviour slightly. There are a few main tickets which do not > introduce a big change, but might very subtly break exi

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

I dont care much of this bundle naming (which looks like 3.1 since there is no real breaking change or arch for end users) but 3.1.3 is due so if it goes in 3.2.0 we should do a corelease of 3.1.3 with at least asm upgrade IMHO. Le dim. 18 avr. 2021 à 13:08, Enrico Olivelli a écrit : > Mark, >

[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&focusedCommentId=17324485#comment-17324485 ] Romain Manni-Bucau commented on OPENJPA-2865: - While represented value is c

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

I would release 3.2.0 :) from mobile (sorry for typos ;) On Sun, Apr 18, 2021, 18:49 Romain Manni-Bucau wrote: > I dont care much of this bundle naming (which looks like 3.1 since there is > no real breaking change or arch for end users) but 3.1.3 is due so if it > goes in 3.2.0 we should do

[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&focusedCommentId=17324554#comment-17324554 ] Mark Struberg commented on OPENJPA-2865: fine, closing it then. > [Oracle] use

[jira] [Commented] (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&focusedCommentId=17324607#comment-17324607 ] ASF subversion and git services commented on OPENJPA-2789: -- Co

[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] [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&focusedCommentId=17324608#comment-17324608 ] Mark Struberg edited comment on OPENJPA-2789 at 4/18/21, 9:17 PM: ---

[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&focusedCommentId=17324730#comment-17324730 ] Francesco Chicchiriccò commented on OPENJPA-2865: - [~struberg] sorry, b

Re: [DISCUSS] next up 3.1.3 or 3.2.0?

On 18/04/21 12:31, Mark Struberg wrote: Hi folks! We fixed a lot of tickets since the last release. Some of them also change/fix the behaviour slightly. There are a few main tickets which do not introduce a big change, but might very subtly break existing apps in very rare edge cases: * Unary