Re: [hibernate-dev] [ORM] Reducing startup log verbosity

See below. On 1/3/19 10:29 AM, Steve Ebersole wrote: > [o.h.d.Dialect] (main) HHH000400: Using dialect: >> org.hibernate.dialect.PostgreSQL95Dialect >> >> -> wondering if it has any value to log the dialect? I mean if you don't >> use the right one, you will definitely have some issues. >> >

Re: [hibernate-dev] inSession / inTransaction

I have no objections to exposing them directly rather than being part of the test infrastructure. On 12/20/18 5:16 PM, Steve Ebersole wrote: > On Thu, Dec 20, 2018 at 1:33 PM Gunnar Morling wrote: > >> Hey, >> >> When discussing this before, there were some doubts about its actual >> usefulness

Re: [hibernate-dev] Wrapping up 5.4.0

Guillaume On the topic of PR #2611, I pushed a commit to fix the test failure a day or two ago that you pointed out.  At this point, the PR is ready for integration unless anyone else wants to review and provide any further input/critique.  What remains for 5.4 which Andrea and I are working on

Re: [hibernate-dev] Getting automatically removed from the list for "excessive bounces"?

I'm also noticing as of today that parts of entire conversations are not being delivered, but yet my account not suspended.  I'm seeing 5-6 messages sent since Friday, November 2nd never made it into gmail.  As of now, the only option I have is to review the archives daily to see what I may I have

Re: [hibernate-dev] JIRA self-registration of users

Sanne - Same here, I haven't changed anything. Chris On 11/2/18 7:14 AM, Yoann Rodiere wrote: > I didn't change the settings recently. > > On Fri, 2 Nov 2018 at 12:03, Sanne Grinovero wrote: > >> Hi all, >> >> I'm receiving requests to approve people who are creating accounts on JIRA. >> >>

Re: [hibernate-dev] Jira - edit comments

Steve - I have the option for my user.  Is the ellipsis button not showing up for you on the comment? On 10/17/18 9:12 AM, Steve Ebersole wrote: > Did someone remove the ability to edit one's comments? I added a comment I > would like to adjust syntax (code fragment), but Jira will not let me

Re: [hibernate-dev] How to enable Javassist when running a WildFly unit test?

Technically the -D parameter should work; however I know a hibernate.properties file works. On 08/24/2018 11:54 PM, Gail Badner wrote: > I tried running: > > mvn clean test -Dtest=HibernateNativeAPINaturalIdTestCase > -Dhibernate.bytecode.provider=javassist -Dsecurity.manager=true > > The result

Re: [hibernate-dev] ORM progress: tricky branch state

+1 from me as well. On 07/02/2018 05:43 PM, andrea boriero wrote: > +1 for 5.3 branch > > On Mon, 2 Jul 2018, 19:05 Gail Badner, wrote: > >> +1 on creating a 5.3 branch, with master being used for 5.4 (or 6.0). >> >> On Mon, Jul 2, 2018 at 9:43 AM, Sanne Grinovero >> wrote: >> >>> On Mon, 2 Jul

Re: [hibernate-dev] Hibernate ORM 5.2.18 to be the last in 5.2 series?

I'm fine postponing the release for another week or 2 if that helps, Christian.  On 06/06/2018 08:26 AM, Guillaume Smet wrote: > On Tue, Jun 5, 2018 at 10:33 PM Gail Badner wrote: > >> Chris mentioned that he is planning to release 5.2.18 on Thursday. >> > It would be nice if we could get >

Re: [hibernate-dev] Health check status API

See inline On 06/01/2018 03:00 AM, Yoann Rodiere wrote: >> We could do it via the Statistics mechanism which can be made available > via > JMX. > > >From what I understand it would be an explicit call from the user > (OpenShift in this case) that would trigger an active check, like a request > to

Re: [hibernate-dev] Hibernate-orm-modules nmartifacts not publish

I believe we renamed it to `hibernate-orm-jbossmodules` in 5.3.0.CR2 as I see that with 5.3.1.Final too. On 05/29/2018 10:59 AM, Vlad Mihalcea wrote: > I checked this forum question: > > https://discourse.hibernate.org/t/org-hibernate-hibernate-orm-modules-no-longer-published/861/2 > > And,

[hibernate-dev] Hibernate ORM 5.3.1.Final has been released

For details: http://in.relation.to/2018/05/28/hibernate-orm-531-final-release/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Starting 5.3.1 release

Please do not push anything to master branch. Thanks, Chris ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] 6.0 Design Doc

In case anyone tries to locate this file more recently, its now under: https://github.com/sebersole/hibernate-core/blob/wip/6.0-merge/design/sql-engine.adoc On 05/23/2018 01:55 PM, Steve Ebersole wrote: > Andrea and I have spent some time getting the SQL execution design doc > up-to-date. Would

Re: [hibernate-dev] Preparing the 5.3.1 release

I already mentioned to Sanne I'd handle it.  I might run into some publishing issues and might need to recruit some help as needed since it'll be my first attempt, but we'll see. Chris On 05/23/2018 06:25 PM, Sanne Grinovero wrote: > we'll draft a "volunteer" :) > > Thanks! > > On 23 May 2018

Re: [hibernate-dev] Simplify SQL function registration when bootstrapping via JPA

I personally agree with Christian, I don't see the use of the ManagedBeanRegistry being a problem.  The new interface certainly opens the door for a variety of builder settings to be contributed easily and using the registry allows for a versatile way to provide that bean, whether it be through

Re: [hibernate-dev] Analyzing the ORM testsuite

executed tests?  On 04/19/2018 05:20 PM, Sanne Grinovero wrote: > On 19 April 2018 at 21:47, Chris Cranford <ch...@hibernate.org> wrote: >> Sanne - >> >> Are you running the build task or are you executing other more specific >> tasks and noticing the slowness? > Ju

Re: [hibernate-dev] Analyzing the ORM testsuite

Sanne - Are you running the build task or are you executing other more specific tasks and noticing the slowness? On 04/19/2018 04:25 PM, Steve Ebersole wrote: > Nothing off the top of my head. The build time is in normal range on my > machine as of this morning (8 - 10 minutes). > > You

Re: [hibernate-dev] Defaultable service strategies

+1 Makes sense to me. On 03/21/2018 02:42 PM, Steve Ebersole wrote: > Thoughts on allowing certain services to be defaulted to the single > implementor registered with the `StrategySelector` service when there is > just one? > > For example, when resolving the RegionFactory unless both (a) >

Re: [hibernate-dev] HHH-12372 Restore binary compatibility with applications using the legacy Session#getFlushMode() method

Sanne - On 03/07/2018 07:58 PM, Sanne Grinovero wrote: > # Fix some pending problem with Envers: it's no longer compiling as a > non-abstract extension of Session doesn't implement getFlushMode; > might be tricky or not, I've not looked yet. I assume this is due to

Re: [hibernate-dev] ORM - HHH-12332 - Releasing a 5.2.15 quickly?

On 03/05/2018 08:26 AM, Sanne Grinovero wrote: > On 5 March 2018 at 12:27, Guillaume Smet > wrote: >> Hi, So far we had 4 duplicate reports of >> https://hibernate.atlassian.net/browse/HHH-12332 (so not counting the >> users having seen the bug and not opening a new

Re: [hibernate-dev] Removing dom4j?

Another alternative (at least for Envers) might be to incorporate the JAXB work I did into 5.3 rather than wait for 6.0. Steve/Andrea, either of you have a preference one way or another? On 02/21/2018 10:52 AM, Chris Cranford wrote: > See inline > > On 02/20/2018 10:52 AM, Jordan Gi

Re: [hibernate-dev] Removing dom4j?

it more likely to expose an incompatibility. > > On 19 February 2018 at 17:03, Chris Cranford <ch...@hibernate.org > <mailto:ch...@hibernate.org>> wrote: > > See below > > On 02/18/2018 11:38 AM, Steve Ebersole wrote: > > On Sun, Feb

Re: [hibernate-dev] Removing dom4j?

See below On 02/18/2018 11:38 AM, Steve Ebersole wrote: > On Sun, Feb 18, 2018 at 4:52 AM Jordan Gigov wrote: > >> I think transitioning to automatic bindings via JAXB will result in error >> messages on wrong configurations becoming far too vague to be useful to the >>

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

Gunnar - I don't particularly see a reason why we cannot as it seems we're handling the CALLBACK mode with no BV provider present earlier in the code path.  I'm fine changing it. Chris On 02/04/2018 07:21 AM, Gunnar Morling wrote: > Hi, > > If the JPA validation mode is set to CALLBACK, BV

Re: [hibernate-dev] 5.3.0 release tomorrow

I have no strong preference either way. On 01/30/2018 05:00 PM, Steve Ebersole wrote: > Wanted to remind everyone that tomorrow is the next time-boxed release for > 5.3. > > I wanted to get everyone's opinions about the version number, whether this > should be Beta2 or CR1. IMO It depends how

Re: [hibernate-dev] HHH-12172 - Bintray v. OSSRH

Fine with me. On 01/24/2018 11:23 AM, Guillaume Smet wrote: > Sure you can get rid of it. > > The only versions of OGM there is a very old one people shouldn't use. > > Thanks! > > On Wed, Jan 24, 2018 at 4:58 PM, andrea boriero > wrote: > >> no objection >> >> On 24

Re: [hibernate-dev] About the WildFly bootstrap errors in Hibernate ORM / master

Thanks Sanne. On 01/24/2018 10:01 AM, Sanne Grinovero wrote: > This is fixed now: HHH-12250 > > You should all be free to remove JBoss Nexus from your settings.xml > again, if you prefer. > > Thanks > > > On 24 January 2018 at 13:33, Sanne Grinovero wrote: >> That's right :(

Re: [hibernate-dev] Realising the JavaDoc jars as well

I agree with Andrea. On 12/29/2017 09:14 AM, andrea boriero wrote: > +1 for filtering out internal packages. > > not a strong opinion on grouping > > On 24 December 2017 at 14:23, Steve Ebersole wrote: > >> Sure, but the question remains :P It just adds another one: >> >>

Re: [hibernate-dev] JPA Compliance

That seems fine to me. On 11/27/2017 04:29 PM, Steve Ebersole wrote: > So then how about the following: > > >1. Add a multi-valued setting to define various categories of JPA >compliance. E.g. `hibernate.jpa.compliance` with multi-selectable values >such as: >1. query (strict

Re: [hibernate-dev] HHH-12125 - @GeneratedValue & 5.3

Sounds reasonable to me. On 11/25/2017 12:45 PM, Steve Ebersole wrote: > I just updated the text for the Jira[1]. > > Specifically, in the section on SEQUENCE and TABLE, at the moment I have > kept the legacy behavior of using "hibernate_sequence" as the name of the > table/sequence - users must

Re: [hibernate-dev] New layout for in.relation.to

Was curious if we would carry the new style to in.relation.to.  It looks superb. Chris On 09/29/2017 01:57 PM, Guillaume Smet wrote: > Hi! > > I converted in.relation.to to the new layout and pushed it to > http://staging.in.relation.to/ . > > Please take a look at it so that we can make

Re: [hibernate-dev] New layout for the website

Guillaume - If we must keep a background color, I think the new color you've changed on staging feels like it flows much more than the gold and is far more appealing to the eye, imo. Chris On 09/28/2017 09:32 AM, Guillaume Smet wrote: > On Thu, Sep 28, 2017 at 3:23 PM, Guillaume Smet

Re: [hibernate-dev] ORM FAQ

I would agree. The performance gain here should highlight caching while the other points more closely align with reduction of development time. On 08/07/2017 02:09 AM, andrea boriero wrote: > it looks really good to me, the only little doubt is related with the > example in the "how Hibernate is

Re: [hibernate-dev] Continue to add 5.2 deprecations for 6.0 work?

Personally I would stick to using @Deprecated and be explicit in the javadoc. On 06/28/2017 05:56 AM, andrea boriero wrote: > In my opinion deprecating something is useful only when we are able to > provide an alternative, not sure about the best approach in case we do not > have a current

Re: [hibernate-dev] Pull request

Vlad / Milo - I've got it on my todo list for today unless Vlad beats me to it :). Chris On 06/07/2017 12:09 AM, Vlad Mihalcea wrote: > Hi, > > If Chris is busy, I can review it for you. > > Vlad > > On Tue, Jun 6, 2017 at 10:36 PM, Milo van der Zee

Re: [hibernate-dev] 6.0 - concept naming

Option 3. On 05/03/2017 10:01 AM, Steve Ebersole wrote: > To circle back to this... I mentioned possibly keeping a reference to the > foreign-key defining the join predicate between the root table and the > secondary table. ATM however we do not model FKs in the runtime > metamodel (either in 6

Re: [hibernate-dev] SQL Server lock hints misunderstanding

Per our discussion on HipChat, +1. On 03/23/2017 06:53 AM, Vlad Mihalcea wrote: > --works > select TOP(?) abstractsk0_.id as id1_0_, abstractsk0_.processed as > processe2_0_ from BatchJob abstractsk0_ with (updlock, rowlock, readpast) > > --fails > select TOP(?) abstractsk0_.id as id1_0_,

Re: [hibernate-dev] 6.0 - Proposed org.hibernate.mapping changes

I don't have a strong lean either way too. Either way, this gives integrators and tooling stability on these contracts while allowing our team to retain some flexibility. As I mentioned on HipChat, I've often seen o.h.mapping as a Hibernate internals only package (even as a user), and so

Re: [hibernate-dev] [hibernate-demos] PR and issues and what to do about it

nnar > > > 2017-02-27 14:22 GMT+01:00 Chris Cranford <ch...@hibernate.org>: >> Emmanuel - >> >> I don't mind. It's simple enough to check the PR tab couple times daily :). >> >> On 02/27/2017 07:39 AM, Emmanuel Bernard wrote: >>> There has

Re: [hibernate-dev] [hibernate-demos] PR and issues and what to do about it

Emmanuel - I don't mind. It's simple enough to check the PR tab couple times daily :). On 02/27/2017 07:39 AM, Emmanuel Bernard wrote: > There has been an effort to collect demos under a single repo. > https://github.com/hibernate/hibernate-demos > > The good news is that people seem to like it

Re: [hibernate-dev] MariaDB-specific Dialects

+1 for both On 02/06/2017 08:19 AM, Steve Ebersole wrote: > Fwiw Dialect discovery is far and away the preferred solution for > "specifying" Dialect. That said, I am ok with splitting off Dialect(s) > specific to MariaDB. > > Relatedly, I wonder if we should begin to remove the Dialects we have

Re: [hibernate-dev] Extended KEY expression support

My thoughts On 01/28/2017 06:00 AM, Christian Beikov wrote: > I created an issue for this feature: > https://hibernate.atlassian.net/browse/HHH-11433 > > > Am 27.01.2017 um 23:58 schrieb Steve Ebersole >> I personally would vote to *not* make this change in 5.x even in terms >> of making it

Re: [hibernate-dev] Query#iterate

+1 to remove as well On 01/27/2017 01:50 PM, Sanne Grinovero wrote: > +1 to remove > > On 27 January 2017 at 18:34, Vlad Mihalcea wrote: >> I'm for removing it even if it didn't complicate the query parser. >> >> Vlad >> >> On Fri, Jan 27, 2017 at 8:26 PM, Steve

Re: [hibernate-dev] 6.0 - Session#createFilter

+1 On 01/03/2017 10:02 AM, andrea boriero wrote: > +1 for removing createFilter() > > On 3 January 2017 at 15:54, Gunnar Morling wrote: > >> 2017-01-03 15:28 GMT+01:00 Steve Ebersole : >> >>> On Tue, Jan 3, 2017 at 5:31 AM Gunnar Morling

Re: [hibernate-dev] ScrollableResults and 6.0

Steve - I'm inclined to agree that changing signatures makes the most sense at this point. Chris On 12/27/2016 04:02 PM, Steve Ebersole wrote: > FWIW my inclination is to just change the existing signatures. 6.0 is a > major release with major changes already wrt querying. > > > On Tue, Dec

Re: [hibernate-dev] RH Summit 2017 CFP

gt; > - What's new in Hibernate 6.0 > - Hibernate Performance Tuning Tips > > Vlad > > On Mon, Nov 28, 2016 at 4:40 PM, Chris Cranford <ch...@hibernate.org > <mailto:ch...@hibernate.org>> wrote: > > The Red Hat Summit 2017 CFP is closing on December 16th an

[hibernate-dev] RH Summit 2017 CFP

The Red Hat Summit 2017 CFP is closing on December 16th and I would recommend we try and submit our abstracts this week if we could. From the ORM side, is there any particular topics we'd care to present or anyone who would like to present? Chris

Re: [hibernate-dev] NativeQuery and parameters

+1 On 09/20/2016 08:59 PM, Steve Ebersole wrote: > In the interest of questioning everything, just to make sure we are all on > the same page, Hibernate's support for native SQL queries currently > recognizes named parameters, positional parameters as well as JDBC-style > parameters. > > JPA

Re: [hibernate-dev] Hibernate Envers > link between to auditable entities

able = false, updatable = false) private Product product; ... } We want to do this to take advantage of Envers' REVISION_ON_COLLECTION_CHANGE. See below in your point 2 as to why. > Thanks, > Tarek > > 2016-09-01 15:55 GMT+02:00 Chris Cranford <cranc...@gmail.com > <mailto

Re: [hibernate-dev] Hibernate Envers > link between to auditable entities

Tarek - There are a few ways we can tackle what you want all within the scope of Envers, but some of it highly depends upon details specific to the relationship between Product (P) and Offer (O). 1. What is the collection type used in Product for the related offers? If this happens to be a

Re: [hibernate-dev] Needing and ORM 5.1.1.Final

Sanne - I'm under the impression that Gail has plans to do a 5.0.10 / 5.1.1 late this week if all goes according to plan. Chris On 07/20/2016 04:36 AM, Sanne Grinovero wrote: > Hi all, > we're still needing a release of Hibernate ORM 5.1.1 for Hibernate OGM.. > > could we plan for one soon

Re: [hibernate-dev] "Awaiting Testcase" transition

+1 On 07/17/2016 05:52 PM, Brett Meyer wrote: > +1! > > On 07/17/2016 10:54 AM, Steve Ebersole wrote: >> I see folks using a generic "template" for the comment added to an issue >> when they transition it to the "Awaiting Testcase" status. If we all >> agree, we could make that a post-function of

Re: [hibernate-dev] HIbernate ORM CI builds

+1 I think (1) and (2) on each push still makes sense with (3) being nightly. Chris On 06/18/2016 11:33 AM, Steve Ebersole wrote: > We have been having a lot of timeouts on the ORM CI builds. Mainly this is > due to ancillary tasks. Currently the ORM jobs execute: > > 1. clean > 2.

Re: [hibernate-dev] Regarding release versioning

+1 for the hybrid approach if we feel we need minor release CRs. On 06/08/2016 09:06 AM, Steve Ebersole wrote: > back to this then I vote that we also go for a hybrid approach to this > where Final is an approximation of the "approved CR", likely with > additional fixes. >

Re: [hibernate-dev] Various expectation changes in hibernate-core after consolidating hibernate-entitymanager

On 04/25/2016 10:34 AM, Steve Ebersole wrote: > I'd add this as well... > > I believe that in most of the cases here we are talking about (passing in a > bad query, closing a closed Session, etc) these exceptions are of the > "checked" sort, meaning they are easily identifiable prior to

Re: [hibernate-dev] Various expectation changes in hibernate-core after consolidating hibernate-entitymanager

On 04/25/2016 12:04 AM, Vlad Mihalcea wrote: > 1. "calling EntityManager#close on a closed EntityManager should result in an > exception;" - that's a reasonable default and shouldn't cause too much > trouble. > 2. "Another change in expectation is in regards to operations outside of a >

Re: [hibernate-dev] GSoC 2016: Congratulations, your proposal with JBoss Community has been accepted!

Welcome aboard, Mincong!! On Sat, Apr 23, 2016 at 3:39 AM, Gunnar Morling wrote: > Hi Mincong, > > Congrats and welcome to this year's GSoC! Looking forward to the project > and your contributions very much! > > @Everyone: Please join me in welcoming Mincong to the team!

Re: [hibernate-dev] Master

d >> >> On Thu, Apr 7, 2016 at 5:57 PM, Steve Ebersole <st...@hibernate.org> >> wrote: >> >>> I agree that would be best. If everyone agrees to stop pushing to master >>> for the time being to allow me to finish this consolidation then I can >>

Re: [hibernate-dev] Master

I have to concur with Sanne, a hold on master pushes until this merge of artifacts is complete makes the most sense from an all around logistics perspective. On Wed, Apr 6, 2016 at 4:04 PM, Sanne Grinovero wrote: > Sounds reasonable. Do you think it will be unstable, i.e.

Re: [hibernate-dev] Java 8 default methods as a refactoring tool

+1 Echo the same as others have said. On Mar 30, 2016 5:52 AM, "andrea boriero" wrote: > +1 > > in my opinion at some point we will have to move to java8 and Hibernate 6.0 > for me is a good candidate. > > On 30 March 2016 at 12:40, Vlad Mihalcea