[hibernate-dev] Hibernate ORM 5.3.23.Final Released

https://in.relation.to/2021/09/29/hibernate-orm-5323-final-out/ ___ hibernate-dev mailing list -- hibernate-dev@lists.jboss.org To unsubscribe send an email to hibernate-dev-le...@lists.jboss.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[hibernate-dev] Re: FetchMode.SELECT

021 at 10:31, Christian Beikov < > christian.bei...@gmail.com> > > wrote: > > > > > I agree that this should be supported. Specifying a fetch mode should > > > IMO not change the fetch type to LAZY or EAGER. > > > > > > Am 06.01.2021 um 04:50 schrie

[hibernate-dev] FetchMode.SELECT

Should it be possible to force an eager association to be loaded by a separate query using @Fetch(FetchMode.SELECT)? I thought that Hibernate supported that for an EAGER association, but I see the documentation for FetchMode.SELECT

[hibernate-dev] Hibernate ORM 5.3.18.Final Released

https://in.relation.to/2020/08/05/hibernate-orm-5318-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Starting release process for ORM 5.3.18

Please don't push anything to 5.3 branch... Thanks, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Can a transient attribute be overridden to be persistent in a subclass?

l, > > based on my understanding of Section 2.2 it seems that it should not be > portable, but I think that it would be nice for Hibernate to support the > feature. > > On Thu, 9 Jul 2020 at 17:40, Gail Badner wrote: > >> Hi Christian, >> >> It actually does wo

Re: [hibernate-dev] Can a transient attribute be overridden to be persistent in a subclass?

ll add a test case to the test suite. Thanks, Gail On Thu, Jul 9, 2020 at 12:47 AM Christian Beikov wrote: > I agree, this should work. Do you have a JIRA ticket describing what the > problem is? > > Am 09.07.2020 um 02:42 schrieb Gail Badner: > > I *think* the following is

[hibernate-dev] Can a transient attribute be overridden to be persistent in a subclass?

I *think* the following is valid, but I need confirmation. This mapping does seem to work for Hibernate. A transient attribute, Employee#title, gets overridden as a persistent attribute, Editor#title, stored in a column named "e_title". Writer#title is also transient, but Writer#group uses the sa

Re: [hibernate-dev] Bytecode enhancement as proxy

+1 On Tue, Jul 7, 2020 at 5:55 AM Sanne Grinovero wrote: > +1 Great idea > > On Tue, 7 Jul 2020 at 13:15, andrea boriero wrote: > > > > Hi all, > > > > Last year the Bytecode enhancement as proxy feature was introduced (see > > https://in.relation.to/2019/07/30/bytecode-proxy/ for details) and

Re: [hibernate-dev] [ORM] Query with condition on subclass attribute

rnate's behavior from the beginning. JPA > says this should use an explicit treat-as operation. > > On Wed, Jul 1, 2020, 4:58 PM Gail Badner wrote: > >> Hi, >> >> Given the following inheritance hierarchy: >> >> @Entity >> public class Person { >

[hibernate-dev] [ORM] Query with condition on subclass attribute

Hi, Given the following inheritance hierarchy: @Entity public class Person { @Id private int id; ... } @Entity public class Employee extends Person { private String title; } Executing a query like the following succeeds. "from Person where title = 'abc'" I thought that it woul

Re: [hibernate-dev] v6 and load-event

I *think* so. On Fri, Jun 5, 2020 at 12:45 PM Steve Ebersole wrote: > Load event handling does not have "anything" parameters. Am I > understanding you correctly? > > On Fri, Jun 5, 2020, 11:42 AM Gail Badner wrote: > >> Hi Steve, >> >> Sorry, I ha

Re: [hibernate-dev] v6 and load-event

Hi Steve, Sorry, I have not read the entire thread carefully, so please disregard if not relevant. Would this provide functionality like what we discussed for an OperationContext? https://hibernate.atlassian.net/browse/HHH-10478 Thanks, Gail On Fri, May 29, 2020 at 4:21 AM Steve Ebersole wrot

Re: [hibernate-dev] Branch protections: enabling selected maintainers on older branches

Thanks for doing that Sanne! On Tue, May 19, 2020 at 11:28 PM Yoann Rodiere wrote: > Sounds like a good idea. > > I took the liberty of renaming the team, since it's specifically about ORM, > and older versions of other projects may not be maintained by the same > people. > > I'll do something s

[hibernate-dev] Hibernate ORM 5.3.17 and 5.4.15.Final has been released

5.3.17: https://in.relation.to/2020/04/30/hibernate-orm-5317-final-out/ 5.4.15: https://in.relation.to/2020/04/30/hibernate-orm-5415-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate

[hibernate-dev] Preparing to release Hibernate ORM 5.3.17 and 5.4.15

Please do not push anything to 5.3 or 5.4 branches until after they are released. Thanks, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] HHH-13916 / WFLY-13259

cache provider for ORM. Maybe ORM6 > offers a good opportunity to rework the provider and make it easy to > maintain a local/remote provider. > > Galder > > > On Wed, Apr 15, 2020 at 1:42 PM Sanne Grinovero > wrote: > >> On Wed, 15 Apr 2020 at 02:16, Gail Badner

Re: [hibernate-dev] HHH-13916 / WFLY-13259

FWIW, there's no point in fixing HHH-13916 unless we hear that Infinispan is going to use the fix. Radim/Galder, WDYT? Thanks, Gail On Tue, Apr 14, 2020 at 3:25 PM Gail Badner wrote: > Hi Sanne, > > I've reworked HHH-13916 <https://hibernate.atlassian.net/browse/HH

Re: [hibernate-dev] HHH-13916 / WFLY-13259

for ORM 6 and avoid spending > your precious time on a v5 improvement - especially if it's going to > require coordination with both the Infinispan and WildFly teams. > > Thanks > > On Fri, 10 Apr 2020 at 00:56, Gail Badner wrote: > > > > I&#x

[hibernate-dev] HHH-13916 / WFLY-13259

I've been looking into how to fix this issue: https://hibernate.atlassian.net/browse/HHH-13916 https://issues.redhat.com/browse/WFLY-13259 The crux of the matter is when Hibernate calls CacheHelper.fromSharedCache( session, cacheKey, cachAccess ), and the entity is not found in the cache, Infinis

[hibernate-dev] Hibernate ORM 5.3.16.Final released

For details: https://in.relation.to/2020/03/27/hibernate-orm-5316-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

We've released Hibernate ORM version 5.4.11.Final ! For details: https://in.relation.to/2020/03/26/hibernate-orm-5413-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Preparing to release Hibernate ORM 5.4.13

Please don't push to master until the release is announced. Thanks, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Jakarta EE: JPA 3.0 is coming

I'm unsure of the merit of supporting both JPA 2.2 and JPA 3.0 using the exact same source code and jars. I have not thought too much about the ramifications of this, but what about dealing with this by having the gradle build generate JPA 3.0-compatible source/test code, then changing the release

Re: [hibernate-dev] Property using field access and has final getter/setter method

Here's the PR: https://github.com/hibernate/hibernate-orm/pull/3286 On Thu, Mar 5, 2020 at 10:21 PM Gail Badner wrote: > I created https://hibernate.atlassian.net/browse/HHH-13891. > > IIUC, a ProxyFactory should not be created if any ID, version, or property > method gette

Re: [hibernate-dev] Property using field access and has final getter/setter method

re final then the ProxyFactory cannot be used > and imo should not get built, especially moving forward as we could use > bytecode-based proxies > > On Wed, Mar 4, 2020 at 2:11 PM Gail Badner wrote: > >> This commit [1] for HHH-11838 [2] causes an error to get lo

Re: [hibernate-dev] Custom EventType and listeners

high level it seems a reasonable idea to me. >> >> In more detail, let's make sure the `registeredEventListeners` >> initialization is not affected by data races, but we can defer >> discussing such details on a PR as that would probably be clearer. >>

[hibernate-dev] Custom EventType and listeners

There has been some discussion that it may be useful for hibernate-rx to be able to define RX-specific event types and listeners. I've created a POC [1] that adds this support. I still need to do some testing, but I would like some feedback before I spend too much time on this. Please let me know

[hibernate-dev] Property using field access and has final getter/setter method

This commit [1] for HHH-11838 [2] causes an error to get logged by ProxyFactoryHelper#validateProxyability [3] for a property that uses field access and has a corresponding final getter/setter method. The logged error does not cause any failure, and the ByteBuddyProxyFactory gets built. Should th

Re: [hibernate-dev] Hibernate ORM : format of the version logged on boot

+1 to changing it. The name was changed from "core" to "ORM" some years back. Can "core" just be dropped now? On Fri, Feb 7, 2020 at 6:20 AM Yoann Rodiere wrote: > +1 > > > Yoann Rodière > Hibernate Team > yo...@hibernate.org > > > On Fri, 7 Feb 2020 at 14:58, Sanne Grinovero wrote: > > > It's

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

It was actually released 07/Jan/2020. Apologies for the late announcement! https://in.relation.to/2020/01/23/hibernate-orm-5315-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Bidirectional one-to-one, both sides are owners, using @PrimaryKeyJoinColumn

tlassian.net/browse/HHH-13814 for that case. I believe the fix for HHH-13814 could also apply when bytecode enhancement is not enabled. Regards, Gail > > > Kind regards, > > Jan-Willem > > > [1] https://github.com/hibernate/hibernate-orm/pull/2612 > > > On 15 Jan 20

[hibernate-dev] Bidirectional one-to-one, both sides are owners, using @PrimaryKeyJoinColumn

Hi, Does Hibernate support having both entities involved in a one-to-one association own its side of the association when using @PrimaryKeyJoinColumn? My guess is that this is not supported by Hibernate. I just want to confirm. For example: @Entity public class Employee { @EmbeddedId p

Re: [hibernate-dev] Composite IDs with a null property/field

M Steve Ebersole wrote: > I've already chimed in ;) > > I don't think this is something we should do. > > On Wed, Dec 18, 2019, 3:44 PM Gail Badner wrote: > >> The main obstacle I see is that Hibernate assumes that ID columns are >> non-nullable, even if ID co

Re: [hibernate-dev] Composite IDs with a null property/field

tps://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/type/ComponentType.java#L671-L675 On Tue, Dec 17, 2019 at 10:41 AM Gail Badner wrote: > Jan-Willem, thanks very much for your feedback! > > You may be right about Hibernate not allowing a formula

Re: [hibernate-dev] Composite IDs with a null property/field

and I think correctly so . > Maybe it is allowed for compound keys however. I think its safe to only > allow null properties in an compound identifier if none of the identifier > properties is a formula. > > Kind regards, > > Jan-Willem > > > > > > >

Re: [hibernate-dev] Composite IDs with a null property/field

Test at the same time as allowing a composite ID to have a null property at the same time. I suppose we could allow a composite ID to have a null property only when it has no properties that are formulas. WDYT? Thanks, Gail On Thu, Dec 12, 2019 at 10:26 AM Gail Badner wrote: > Thi

Re: [hibernate-dev] Composite IDs with a null property/field

allow the column to be nullable >>> (if the DB even allows that), I don't think Hibernate allows null to be >>> a valid id value. Because null means I don't know or not applicable. >>> I think in the past we argued the same for attributes of a composite id, >&

[hibernate-dev] Composite IDs with a null property/field

Currently, there is no way to load an entity that exists in the database with a composite ID, if one of the composite ID columns is null. This behavior is due to this code in ComponentType#hydrate: https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/ty

Re: [hibernate-dev] IdClass superclasses

t picked up. >> >> Maybe I'm misunderstanding you? >> >> On Mon, Dec 9, 2019 at 1:58 PM Gail Badner wrote: >> >>> Hi, >>> >>> Suppose we have the following: >>> >>> public class CompositeKey implements Serializable { >

[hibernate-dev] IdClass superclasses

Hi, Suppose we have the following: public class CompositeKey implements Serializable { private Long id1; private Long id2; public CompositeKey(Long id1, Long id2) { super(); this.id1 = id1; this.id2 = id2; } ... } public class InheritedKey extends CompositeKey { private

Re: [hibernate-dev] Cache key containing composite ID with a many-to-one

Hi Steve, I like your ideas about loading an entity with multiple ID attributes without @IdClass. It's much nicer than passing an instance of the entity with ID attributes initialized to Session#get. Getting back to the cache issue -- it sounds like disassembling the ID is worth pursuing. Please

Re: [hibernate-dev] Cache key containing composite ID with a many-to-one

equals, but ignore them and > apply "the obvious one" consistently. > > Thanks, > Sanne > > > > On Wed, 4 Dec 2019 at 19:40, Gail Badner wrote: > > > > When an entity is cached with a composite ID containing a many-to-one > > association, the

[hibernate-dev] Cache key containing composite ID with a many-to-one

When an entity is cached with a composite ID containing a many-to-one association, the cache key will contain the many-to-one associated entity. If the associated entity is not enhanced, then it could be an uninitialized proxy. I've created a test case [1] that illustrates this using Infinispan. T

[hibernate-dev] Hibernate ORM 5.3.14 Released

https://in.relation.to/2019/11/08/hibernate-orm-5314-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Preparing to release Hibernate ORM 5.3.14

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

[hibernate-dev] Narrowed HibernateProxy and Uninitialized bytecode-enhanced entities do not get detached

Hi, I seem to remember this topic came when we were working on the enhancement-as-proxy feature. Basically, EnhancementAsProxyLazinessInterceptor#session does not get nullified when the PersistenceContext gets cleared. As a result, such an entity can still get initialized if the SharedSessionCon

Re: [hibernate-dev] "JDK: oraclejdk8 Java" check is failing for a PR

It passed this time. :) On Tue, Oct 15, 2019 at 2:51 PM Gail Badner wrote: > OK, I see it now. > > Thanks! > Gail > > On Tue, Oct 15, 2019 at 2:24 PM Steve Ebersole > wrote: > >> Yes, in the upper right end corner there is a "Restart Job" link... >&g

Re: [hibernate-dev] "JDK: oraclejdk8 Java" check is failing for a PR

OK, I see it now. Thanks! Gail On Tue, Oct 15, 2019 at 2:24 PM Steve Ebersole wrote: > Yes, in the upper right end corner there is a "Restart Job" link... > That's for any Travis job > > On Tue, Oct 15, 2019 at 1:20 PM Gail Badner wrote: > >> "JDK: ora

[hibernate-dev] "JDK: oraclejdk8 Java" check is failing for a PR

"JDK: oraclejdk8 Java" check is failing [1] for PR: https://github.com/hibernate/hibernate-orm/pull/3066 It's showing that OsgiIntegrationTest is failing. I can't reproduce this locally, but maybe I'm not using the same version of Has anyone else seen this before? Is there a way to repeat the jo

[hibernate-dev] Hibernate ORM 5.3.12.Final Released

https://in.relation.to/2019/09/11/hibernate-orm-5312-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Starting Hibernate ORM 5.3.12 release

Please don't push anything to 5.3 branch. Thanks, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] HHH-13317

dirty tracking. > > Regards, > > Luis Barreiro > > Middleware Performance Team > <https://red.ht/sig> > On 9/9/19 10:55 PM, Gail Badner wrote: > > Hi Luis, > > IIUC, HHH-13446 deals with a mappedBy="" value that is invalid. I'm > confused

[hibernate-dev] Hibernate ORM 5.3.12 needs to support JDK13

Hi, WildFly 18 supports JDK 13, so Hibernate ORM 5.3.12 will also need to support JDK 13. We know that ByteBuddy needs to be upgraded to 1.9.11. That will be covered by HHH-13504 [1] Andrea mentioned HHH-13415 [2] should be backported as well. Grepping through the log for jdk, I see these other

Re: [hibernate-dev] HHH-13317

e does not support a lazy association in an embeddable with bytecode enhancement. IIRC, we expect the association in the embeddable will not be lazy. It shouldn't thrown an exception though. Luis, could you please shed some light on this? Thanks, Gail On Thu, Sep 5, 2019 at 5:14 PM Gail Badn

Re: [hibernate-dev] HHH-13317

ll/2919 > > If it's the same issue, it should be fixed. While Javassist fails when > enhancing the classes, ByteBuddy succeeds but the resulting classes are > invalid. > > Regards, > > Luis Barreiro > > Middleware Performance Team > <https://red.ht/sig> >

[hibernate-dev] HHH-13317

HHH-13317 is specifically a bug with bytecode enhancement using Javassist. It showed up when running a test added for HHH-13241. I've verified that the same issue affected 5.1, so this is not a regression. Is it worthwhile to fix this issue in 5.3/5.4? Will Javassist continue to be supported in

Re: [hibernate-dev] No default implementation for PersistenceContext#addEnhancedProxy

sure is useful > > On Mon, Sep 2, 2019 at 4:19 PM Gail Badner wrote: > >> HHH-11147 added PersistenceContext#addEnhancedProxy without a default >> implementation. >> >> Would an application implement PersistenceContext? If so, this would be a >&g

Re: [hibernate-dev] EntityMetamodel

Ok, thanks. On Tue, Sep 3, 2019 at 6:09 AM Steve Ebersole wrote: > Seems like we dropped the need for the subclass checking here but did not > remove passing that Function. Technically it could be removed and the > EntityMetamodel > constructor reverted > > On Mon, Sep 2, 20

[hibernate-dev] EntityMetamodel

HHH-11147 changed a EntityMetamodel constructor argument from a SessionFactoryImplementor to a PersisterCreationContext. Would a custom EntityPersister break due to calling the constructor with the new argument type? >From what I can tell, the argument was changed to PersisterCreationContext go g

[hibernate-dev] Property#isLazy

HHH-11147 changed Property#isLazy as shown in [1]. The part that concerns me is: + // For a many-to-one, this is always false. Whether the + // association is EAGER, PROXY or NO-PROXY we want the fk + // selected + return false; I don't think this is correct when enhancement-as-proxy is disable

[hibernate-dev] No default implementation for PersistenceContext#addEnhancedProxy

HHH-11147 added PersistenceContext#addEnhancedProxy without a default implementation. Would an application implement PersistenceContext? If so, this would be a breaking change. Please let me know... Thanks, Gail ___ hibernate-dev mailing list hibernate

Re: [hibernate-dev] hibernate.id.optimizer.pooled.preferred=hilo or legacy-hilo

just left there to allow these > legacy databases keep working > > On Wed, Aug 28, 2019, 12:08 AM Gail Badner wrote: > >> Hi, >> >> The documentation for hibernate.id.optimizer.pooled.preferred says the >> following: >> >> hilo; legacy-hilo >&g

[hibernate-dev] hibernate.id.optimizer.pooled.preferred=hilo or legacy-hilo

Hi, The documentation for hibernate.id.optimizer.pooled.preferred says the following: hilo; legacy-hilo Define a custom algorithm for generating pools of values based on a single value from a table or sequence. These optimizers are not recommended for use. They are maintained (and mentioned) he

Re: [hibernate-dev] Entity implementation of equals()

ail > > > However, this is a case with a MappedSuperclass and specifically a > > MappedSupperclass that is I guess shared amongst multiple root entities. > > So here the allowance of subclasses is not really feasible and relying on > > any kind of equality checking defined

[hibernate-dev] Entity implementation of equals()

Hi, I'm looking into the impact of HHH-13590. In the test for HHH-13590, I see that the mapped superclass entity defines equals() as: @Override public boolean equals(Object o) { if (this == o) return true; if (o == null || getClass() != o.getClass()) return false; ... } Due to the bu

Re: [hibernate-dev] ConnectionObserver

In 4.2 and 4.3, it was possible to add a ConnectionObserver using org.hibernate.engine.jdbc.spi.LogicalConnectionImplementor#addObserver(ConnectionObserver observer). Starting in 5.0, LogicalConnectionImplementor was moved to org.hibernate.resource.jdbc.spi, and it's no longer possible to add a C

Re: [hibernate-dev] API removal proposal: org.hibernate.resource.jdbc.ResourceRegistry#cancelLastQuery

Hi Sanne, I've confirmed that current versions of WildFly and EAP do not call that ResourceRegistry#cancelLastQuery. ResourceRegistry was introduced in 5.0. As of 5.0.16, cancelLastQuery() is not used by Hibernate ORM. At least as far back as 4.2, SessionImpl#cancelQuery called JdbcCoordinator#c

[hibernate-dev] Hibernate ORM 5.3.11.Final released

For details: https://in.relation.to/2019/08/15/hibernate-orm-5311-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Starting release process for ORM 5.3.11.Final

Please don't push anything to 5.3 branch. Thanks, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Suggestions for fixing HHH-13570?

I chatted with Andrea about this. I'll skip the test using @RequiresDialectFeature( value = DialectChecks.SupportsLockTimeouts.class ) On Tue, Aug 13, 2019 at 6:45 PM Gail Badner wrote: > An alternative is to mark the tests with: > > @RequiresDialect

Re: [hibernate-dev] Suggestions for fixing HHH-13570?

An alternative is to mark the tests with: @RequiresDialectFeature( value = DialectChecks.SupportsLockTimeouts.class ) since SybaseASE15Dialect#supportsLockTimeouts returns false. On Tue, Aug 13, 2019 at 6:29 PM Gail Badner wrote: > LockModeTest executes the following SQL for Sybase and

[hibernate-dev] Suggestions for fixing HHH-13570?

LockModeTest executes the following SQL for Sybase and SQL Server: UPDATE T_LOCK_A WITH(NOWAIT) SET a_value = :value where id = :id"; This fails on Sybase, because it doesn't recognize WITH(NOWAIT). If I remove WITH(NOWAIT), the statement blocks until Junit times out. I'm having trouble finding

[hibernate-dev] Preparing to release Hibernate ORM 5.4.4

Please do not push anything to master until the release is finished. Regards, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] How to add Weblinks w/ new HHH Jira view?

vise you to > do just that, so that hopefully they improve the new view before removing > the old one. > > > Yoann Rodière > Hibernate NoORM Team > yo...@hibernate.org > > > On Sat, 13 Jul 2019 at 02:15, Gail Badner wrote: > >> I see that the new Jira view al

[hibernate-dev] How to add Weblinks w/ new HHH Jira view?

I see that the new Jira view allows issue links to be added easily. With the old view, I could add a Weblink (basically just a generic hyperlink). I don't see how to do that with the new view. Does something need to be added to provide that functionality? For now, I can go back to the old view to

[hibernate-dev] hibernate.jpa.compliance.caching and nullable secondary tables

The Javadoc for JpaCompliance#isJpaCacheComplianceEnabled says: * @implNote Effects include marking all secondary tables as non-optional. The reason * being that optional secondary tables can lead to entity cache being invalidated rather * than updated. But, the way it's used is the opposite (ma

Re: [hibernate-dev] HHH-11147 - bytecode based "proxies"

Hi Steve, We had discussed releasing in 5.4, and possibly 5.3, with the default for hibernate.bytecode.allow_enhancement_as_proxy=false. I am in favor of this. Are you suggesting that the default behavior would effectively be to set hibernate.bytecode.allow_enhancement_as_proxy=true in 5.5? Do y

Re: [hibernate-dev] Hibernate ORM 5.3.10.Final released

Sorry, I referenced the incorrect release announcement in my previous email. It should have been: http://in.relation.to/2019/04/22/hibernate-orm-5310-final-out/ On Mon, Apr 22, 2019 at 2:27 PM Gail Badner wrote: > http://in.relation.to/2019/02/19/hibernate-orm-538-final-

[hibernate-dev] Hibernate ORM 5.3.10.Final released

http://in.relation.to/2019/02/19/hibernate-orm-538-final-out/ ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] HHH-13364

Thanks Andrea! On Fri, Apr 12, 2019 at 3:43 AM andrea boriero wrote: > I gave a look at your PR and the change makes sense to me > > Andrea > > On Fri, 12 Apr 2019 at 03:54, Gail Badner wrote: > >> EntityManager#find and Query#getResultList / #getSingleResult do not &

[hibernate-dev] HHH-13364

EntityManager#find and Query#getResultList / #getSingleResult do not behave consistently when failing to get a pessimistic lock with a timeout provided. I think EntityManager#find is working correctly, and I think Query#getResultList / #getSingleResult should be consistent with EntityManager#find.

[hibernate-dev] Make Gradle plugin available on plugins.gradle.org? (HHH-13354)

An issue was opened to make Gradle plugin available on plugins.gradle.org. Should this be done? If so, how? Regards, Gail ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] WildFly tests with ByteBuddy enhancement are failing

PR: https://github.com/hibernate/hibernate-orm/pull/2825 On Thu, Mar 28, 2019 at 1:49 PM Gail Badner wrote: > Hi Guillaume, > > I've confirmed that my fix gets the WildFly tests to pass. I've created > https://hibernate.atlassian.net/browse/HHH-13343. > > I'm n

Re: [hibernate-dev] WildFly tests with ByteBuddy enhancement are failing

rce" to > consider. > > I wonder if what you did (i.e. considering the provided bytes) should be > the default behavior. > > On Thu, Mar 28, 2019 at 7:13 AM Gail Badner wrote: > >> Hi Guillaume, >> >> Unfortunately, it is not so easy. >> >&g

Re: [hibernate-dev] WildFly tests with ByteBuddy enhancement are failing

Comments are welcome. Regards, Gail [1] https://github.com/gbadner/hibernate-core/tree/WFLY-11891-5.3 [2] https://github.com/gbadner/hibernate-core/commit/ef1687807def94a4465d6cf2372f9235dc559bd1 On Tue, Mar 26, 2019 at 10:11 AM Gail Badner wrote: > Guillaume, thanks for the suggestion. I'l

Re: [hibernate-dev] WildFly tests with ByteBuddy enhancement are failing

/github.com/jbossas/jboss-classfilewriter for generating > > >> the EJB > > >> stub classes like > > >> > > >> > > > org/jboss/as/test/integration/jpa/basic/SLSBPersistenceContexts$$$view5.class. > > > > >> > > >

Re: [hibernate-dev] WildFly tests with ByteBuddy enhancement are failing

Should dynamically generated classes be possible to load from a ClassLoader by a name like org/jboss/as/test/integration/jpa/basic/SLSBPersistenceContexts$$$view5.class ? On Fri, Mar 22, 2019 at 12:34 PM Scott Marlow wrote: > > On 3/22/19 1:53 PM, Gail Badner wrote: > > I just wante

Re: [hibernate-dev] WildFly tests with ByteBuddy enhancement are failing

I just wanted to clarify that sometimes I was seeing problems with SerializationProxyHackImplementation. When debugging, I usually saw a failure on SLSBPersistenceContexts$$$viewX, where (IIRC) X was between 1 and 9. On Fri, Mar 22, 2019 at 7:22 AM Scott Marlow wrote: > > > On 3/22/19 10:08 AM,

[hibernate-dev] WildFly tests with ByteBuddy enhancement are failing

Scott added bytecode enhancement to some WildFly tests for WFLY-11891 [1], which are failing. Here is Scott's PR with the updated tests: [2] When I stepped into org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase, I can see that they are failing in ByteBuddy cod

Re: [hibernate-dev] [ORM] Converging on 5.4.2

On Mon, Mar 4, 2019 at 2:31 AM Guillaume Smet wrote: > Hi, > > I'm busy on other things these days but I would like to release a 5.4.2 > soon anyway as we already have fixed 28 issues, some of them quite > annoying. > > Gail, I think most of the remaining open PRs need your attention. > > If you

Re: [hibernate-dev] Upgrading Hibernate Causes null index column for collection error for List

Hi Amit, This mailing list is for people working on Hibernate development. If you think you have found a bug, then please create a jira issue ( https://hibernate.atlassian.net/) and attach a test case that reproduces your issue. Regards, Gail On Fri, Feb 15, 2019 at 6:05 AM Amit Shah wrote: >

[hibernate-dev] HHH-13076

I was looking into backporting HHH-13076 for 5.3.8. Looking at the fix [1], I see that starting a JDBC transaction that is already started will fail, even if hibernate.jpa.compliance.transaction=false. AFAICT, this didn't happen in 5.1. Was there a reason in particular why this was done? Thanks,

[hibernate-dev] hibernate-tools-maven-plugin 5.4 snapshots are not being uploaded to Nexus

Someone mentioned in a jira that hibernate-tools-maven-plugin is not available for 5.4. snapshots. [1] Should it be? Regards, Gail [1] https://repository.jboss.org/nexus/content/groups/public-jboss/org/hibernate/hibernate-tools-maven-plugin/ ___ hibern

Re: [hibernate-dev] Should the TransactionSynchronizationRegistry be cached by the JtaPlatform or perhaps at the SessionFactory level?

Hi Scott, I see that the issue is resolved and your commit is merged. Is this no longer an issue? Thanks, Gail On Wed, Nov 28, 2018 at 1:12 PM Scott Marlow wrote: > Hi, > > I started working on a WildFly change WFLY-11243 [1] to cache the > TransactionSynchronizationRegistry inside of the Wild

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

This is the final release of the 5.1 series. For details see http://in.relation.to/2018/11/28/hibernate-orm-5117-final-release/. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Can't build Hibernate ORM 5.1 documentation

ould remove them from 5.1 as well. > > Vlad > > On Wed, Nov 28, 2018 at 11:37 AM Gail Badner wrote: > >> Andrea found a solution that works. :) >> >> On Tue, Nov 27, 2018 at 10:49 PM Gail Badner wrote: >> >>> I'm getting ready to release 5.1.17

Re: [hibernate-dev] Can't build Hibernate ORM 5.1 documentation

Andrea found a solution that works. :) On Tue, Nov 27, 2018 at 10:49 PM Gail Badner wrote: > I'm getting ready to release 5.1.17, but I'm having trouble building the > documentation. > > I can't even build the documentation using 5.1.16 tag. It worked fine when &

[hibernate-dev] Can't build Hibernate ORM 5.1 documentation

I'm getting ready to release 5.1.17, but I'm having trouble building the documentation. I can't even build the documentation using 5.1.16 tag. It worked fine when I released 5.1.16.Final in August. A new property was added for HHH-13011, and I need to get that documented in the user guide for 5.1

Re: [hibernate-dev] ORM 6 branch

That's fine with me. On Mon, Nov 26, 2018 at 11:29 AM Steve Ebersole wrote: > This Wednesday we plan to release 6.0 Alpha1 and I thought it best to start > discussing how to best handle the 6.0 and master branches. > > I think we should keep 6.0 a little while longer in my fork and 5.4 as > mast

  1   2   3   4   5   6   7   >