Re: [hibernate-dev] [ORM] Make EntityEntry and interface and have a Factory... or not

> +1 to reopen this one, I still want the feature ;) Yes, it'd be nice to have, but do we really need it? For OGM the pluggable extra state is good enough for now I would say. Do you have a specific usage for a custom EE in mind? 2014-12-03 15:48 GMT+01:00 Steve Ebersole : > Well to be fair I ha

Re: [hibernate-dev] Closed pull requests

On 3 December 2014 at 14:46, Steve Ebersole wrote: > Yes and no. The issues are closed *against 6.0*, which is still technically > correct for the current state. The changes are still integrated into the > metamodel branch which correlates to 6.0 in jira. > > The question is more *which* of thos

Re: [hibernate-dev] [ORM] Make EntityEntry and interface and have a Factory... or not

Well to be fair I have been pretty consistent in responding to all of these (on the dev ml, on irc, etc) to reopen the pull request if it was closed due to this and still should be applied. On Wed, Dec 3, 2014 at 6:21 AM, Sanne Grinovero wrote: > I guess that's the same problem as raised by Andr

Re: [hibernate-dev] Closed pull requests

Yes and no. The issues are closed *against 6.0*, which is still technically correct for the current state. The changes are still integrated into the metamodel branch which correlates to 6.0 in jira. The question is more *which* of those changes we want to migrate to master. On Wed, Dec 3, 2014

Re: [hibernate-dev] Closed pull requests

Don't you all think it's very troubling that several issues in JIRA are marked as "resolved" but are not actually integrated in the new master? This query is probably not perfect but I hope it's enough to highlight the problem: https://hibernate.atlassian.net/issues/?filter=15161&jql=project%20%3D

Re: [hibernate-dev] [ORM] Make EntityEntry and interface and have a Factory... or not

I guess that's the same problem as raised by Andrej Golovnin: when master was renamed, all open PRs were automatically closed. +1 to reopen this one, I still want the feature ;) Sanne On 3 December 2014 at 08:33, Emmanuel Bernard wrote: > Back during the EntityEntry improvements, we explored th

Re: [hibernate-dev] [website] Update your environment

For what it's worth the update worked w/o problem for me using ruby-2.0.0 --Hardy On Wed, Dec 03, 2014 at 09:29:07AM +0100, Emmanuel Bernard wrote: > The dependencies for the hibernate.org website have > changed. Make sure to get the latest from the production branch and

[hibernate-dev] [ORM] Make EntityEntry and interface and have a Factory... or not

Back during the EntityEntry improvements, we explored the idea of an EntityEntryFactory and an EntityEntry interface so that one could provide alternative implementations optimized to the specific use case. We did not apply it in the 4.x branch possibly due to backward compatibility concerns. I

Re: [hibernate-dev] Mapping defaults for @OneToOne

In both of the following cases, Hibernate creates a unique key constraint: 1) 2) The documentation is clear that setting unique="true" indicates that a unique key constraint should be created. I only see mappings for in the documentation. Is the combination in 2) valid (unique="true" not-

[hibernate-dev] [website] Update your environment

The dependencies for the hibernate.org website have changed. Make sure to get the latest from the production branch and run rake clean[all] rake setup Tested on Ruby 2.1.5 ___ hibernate-dev mailing list hibernate-dev@lists.jboss