Re: [hibernate-dev] 5.0 defaults

I mentioned my concerns about hibernate.implicit_naming_strategy and auto-quoting keywords when I was getting the standalone TCK working with master. Here are my thoughts... On 08/03/2015 02:17 PM, Steve Ebersole wrote: > 1) hibernate.implicit_naming_strategy - by default Hibernate uses its > le

Re: [hibernate-dev] Embedded Composite Identifiers

FWIW, that's one of the mapping patterns I always found awkward, so +1 for deprecating it from me. What would be the strategy, though? Deprecate in 5 and remove in 6? 2015-08-03 17:46 GMT+02:00 Sanne Grinovero : > I remember loving this feature. > Composite keys are very common in databases I wo

Re: [hibernate-dev] ORM Documentation

Well Identifiers in the mapping guide still needs some work. I guess move that into category (b). TBH I do not know how much of "derived identities" I will document this time around. If someone more familiar/comfortable with explaining that stuff wanted to take a shot I would not argue :) On M

Re: [hibernate-dev] ORM Documentation

So the documentation is getting along. If people could start looking it over that would be great. If people are willing to pick up remaining topics, even better! So the 2 old docs (manual and devguide) are now 3 much more focused docs: 1) Hibernate User Guide - much of the information from the

[hibernate-dev] [CI] Shutting down CouchDB

I've stopped and disabled CouchDB on each slave node as it looks like it's conflicting with Byteman ports and making many testsuites fail. We'll need to reconfigure it before enabling again: https://hibernate.atlassian.net/browse/WEBSITE-387 Sorry for the failure notices! If they are Byteman rel

[hibernate-dev] New PostgreSQL users available on ci.hibernate.org

The postgres users as defined in Hibernate ORM's matrix configuration are now setup on each slave for ci.hibernate.org. - https://github.com/hibernate/hibernate-orm/blob/master/databases/pgsql/resources/hibernate.properties They have SUPERUSER privileges, so they can create/drop new databases a

Re: [hibernate-dev] 5.0 defaults

On 08/03/2015 04:00 PM, Steve Ebersole wrote: > On Mon, Aug 3, 2015 at 2:07 PM Scott Marlow > wrote: > > > > On 08/03/2015 02:17 PM, Steve Ebersole wrote: > > Scott has been asking about making some setting defaults > consistent between > > Hibernate

Re: [hibernate-dev] 5.0 defaults

On Mon, Aug 3, 2015 at 2:07 PM Scott Marlow wrote: > > > On 08/03/2015 02:17 PM, Steve Ebersole wrote: > > Scott has been asking about making some setting defaults consistent > between > > Hibernate and WildFly. Most I think WildFly should just use the ORM > > defaults. > > If ORM 5.0 used the

Re: [hibernate-dev] 5.0 defaults

On 08/03/2015 02:17 PM, Steve Ebersole wrote: > Scott has been asking about making some setting defaults consistent between > Hibernate and WildFly. Most I think WildFly should just use the ORM > defaults. If ORM 5.0 used the same defaults as the WildFly (JPA) deployer, then WildFly could sto

[hibernate-dev] 5.0 defaults

Scott has been asking about making some setting defaults consistent between Hibernate and WildFly. Most I think WildFly should just use the ORM defaults. But 3 in particular I thought we should all discuss and decide on.. 1) hibernate.implicit_naming_strategy - by default Hibernate uses its lega

Re: [hibernate-dev] Embedded Composite Identifiers

I remember loving this feature. Composite keys are very common in databases I worked with, while loading by ids seems to be quite uncommon in my coding style as I don't remember knowing how to do that, nor that this ignorance ever bothered me :) +1 anyway, that's just to give some perspective. On

Re: [hibernate-dev] Embedded Composite Identifiers

Here is what I proposes in the documentation in the section discussing composite identifiers: Technically a composite identifier can be made up of just a single persistent attribute. The restriction that a composite identifier has to be represented by a "primary ke

[hibernate-dev] Embedded Composite Identifiers

I am thinking we should start to soft-deprecate[1] the historical feature of embedded composite identifiers. This is the feature that allowed an entity to define a composite identifier without any kind of "pk class" (EmbeddedId/IdClass): @Entity public class MyEntity { @Id public Integer

[hibernate-dev] Hibernate Search branching and an update to 5.4.0.x work

The Lucene 5 related work - which is now almost ready - is not meant to be included in the 5.4 release, but we postponed the release of 5.4.0.Final a bit as we're waiting for a .Final of Hibernate ORM 5. However there are a couple other pull requests which are open and suited to be merged now, so