Re: [hibernate-dev] @db.dialect@ - yet again

Hi Steve, Had the same issue. https://youtrack.jetbrains.com/issue/IDEA-175172 I solved it by running the processTestResources task and copying the properties file from the build folder to the out folder. Hope it helps! Best, Arnold On Thu, Oct 12, 2017 at 2:22 PM, Steve Ebersole wrote: > I

Re: [hibernate-dev] DTO Projection support for native queries?

n Fri, Aug 18, 2017 at 10:21 AM Arnold Gálovics > wrote: > >> Hey Steve, >> >> Thanks for the answer. >> >> I was aware of these two solutions but there are definitely projects >> which want to use DTO projections and cannot (don't) want to utilize

Re: [hibernate-dev] DTO Projection support for native queries?

Mapping). You'd specify a javax.persistence.ConstructorResult. Hibernate has an alternative means to support this using a org.hibernate.transform.ResultTransformer On Fri, Aug 18, 2017 at 9:47 AM Arnold Gálovics wrote: > Hi all, > > I'm particularly interested in the usecase whe

[hibernate-dev] DTO Projection support for native queries?

Hi all, I'm particularly interested in the usecase when you want to have a DTO projection from a native query. Currently as far as I know this is not supported through the JPA API. If I say entityManager.createNativeQuery("...", SomeDTO.class) Hibernate says SomeDTO is not an entity, at least tha

Re: [hibernate-dev] PESSIMISTIC_FORCE_INCREMENT lock mode

e "exclusive", etc. - just describe the > outcomes/phenomena. > > On Tue, Aug 1, 2017 at 9:23 AM Vlad Mihalcea > wrote: > >> Sure. Send me a Pull Request and I'll integrate it. >> >> Vlad >> >> On Tue, Aug 1, 2017 at 2:29 PM, Arnold

Re: [hibernate-dev] PESSIMISTIC_FORCE_INCREMENT lock mode

at will offer no advantage for > the PESSIMISTIC_FORCE_INCREMENT over its optimistic alternative. > > So, I suppose the lock should always be exclusive so that other lock > requests are blocked until the lock is released. > > Vlad > > On Fri, Jul 28, 2017 at 9:35 AM, Arnold

Re: [hibernate-dev] PESSIMISTIC_FORCE_INCREMENT lock mode

it's no longer relevant to the > current behavior. > > Vlad > > On Thu, Jul 27, 2017 at 4:46 PM, Arnold Gálovics > wrote: > >> Hi all, >> >> I'm a bit confused with the mentioned lock mode. >> >> *The doc says the following:* >> *"T

[hibernate-dev] PESSIMISTIC_FORCE_INCREMENT lock mode

Hi all, I'm a bit confused with the mentioned lock mode. *The doc says the following:* *"The entity is locked pessimistically and its version is incremented automatically even if the entity has not changed."* I'm checking this with an H2 DB and the current behavior is the following: - the versio

Re: [hibernate-dev] 6.0 - procedure/function calls via NativeQuery

Hey, @Vlad: if they eventually have to adjust their code, why is it so hard to use the proper API for calling stored procedures? I'm supporting Steve's idea to remove this complexity and force the users to use the proper API. I think for 6.0 this change can be acceptable and should be mentioned i

Re: [hibernate-dev] Hibernate Extras module

, wouldn't it be > better to have two extra modules? > > Thanks! > Sanne > > > > > Vlad > > > > On Sat, Jul 1, 2017 at 7:48 PM, Arnold Gálovics < > galovicsarn...@gmail.com> > > wrote: > > > >> Hi Vlad, > >> > >>

Re: [hibernate-dev] Hibernate Extras module

Hi Vlad, "any other features that cannot be added into the hibernate-core because they are DB-specific." Aren't Dialects in Hibernate DB specific? Why is there a reason not to support some DB specific feature in Hibernate core? Isn't it possible to have DB specific Hibernate modules? For example

[hibernate-dev] Hibernate development in Eclipse IDE?

Hi all, Does anyone have issues with the hibernate-core module in Eclipse? *I'm getting the following errors there:* The method doInHibernate(Supplier, TransactionUtil.HibernateTransactionFunction) is ambiguous for the type AbstractBulkCompositeIdTest The method doInHibernate(Supplier, Transactio