Re: [hibernate-dev] Oracle12cDialect identity support

I was mistaken when I said that an IDENTITY ID will be created when using @GeneratedValue or @GeneratedValue(strategy= GenerationType.AUTO). With hibernate.id.new_generator_mappings set to true by default in 5.0 and 5.1, a SequenceStyleGenerator will be used instead. Currently, the default for "na

[hibernate-dev] HHH-9548 - stored procedures and null parameter values

HHH-9548[1] presents an interesting conundrum in terms of how to handle null parameter values in regards to stored procedures and specifically in terms of any argument defaults that might be defined on the database. At the moment our support decides to not pass along the null in the desire to not

Re: [hibernate-dev] should immutable entities in the second level cache be invalidated when they are removed from the database?

On 01/05/2016 12:36 PM, Steve Ebersole wrote: > Sorry Scott, I am not sure I understand exactly what you are asking. I > will try to answer what I think you are asking as best I can.. > > > On Tue, Jan 5, 2016 at 9:35 AM Scott Marlow > wrote: > > I missed adding th

Re: [hibernate-dev] Oracle12cDialect identity support

On Tue, Jan 5, 2016 at 12:42 AM Gail Badner wrote: > > >> Native is a Hibernate-only concept and so we can really choose whatever >> we want for native generators. Also native is an outdated concept, >> replaced by AUTO and SequenceStyleGenerator. IMO we should never be >> choosing IDENTITY fo

Re: [hibernate-dev] should immutable entities in the second level cache be invalidated when they are removed from the database?

Sorry Scott, I am not sure I understand exactly what you are asking. I will try to answer what I think you are asking as best I can.. On Tue, Jan 5, 2016 at 9:35 AM Scott Marlow wrote: > I missed adding the WildFly clustering configuration for the Hibernate > immutable-entity cache. I opened

[hibernate-dev] should immutable entities in the second level cache be invalidated when they are removed from the database?

I missed adding the WildFly clustering configuration for the Hibernate immutable-entity cache. I opened WFLY-5923 [1] for adding the cache but am unsure of whether org.hibernate.annotations.Immutable means that the application handles clearing the 2lc of stale immutable entities or if that sho

Re: [hibernate-dev] Not letting Jenkins auto-close PRs upon build failures

+1, but I don’t know how ;) > On 05 Jan 2016, at 13:55, Gunnar Morling wrote: > > Hi, > > Not sure whether that's a new behaviour, but it's super annoying that > the pull request builder automatically closes pull requests if there > is a build failure. Can we change this so the PR stays open, p

[hibernate-dev] Not letting Jenkins auto-close PRs upon build failures

Hi, Not sure whether that's a new behaviour, but it's super annoying that the pull request builder automatically closes pull requests if there is a build failure. Can we change this so the PR stays open, please? The current behaviour is highly frustrating, you need to re-open the PR again after f