[hibernate-dev] [website] Update your environment

[Emmanuel Bernard]

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.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Gail Badner]

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-null="false")?

- Original Message -
> From: "Gail Badner" 
> To: "hibernate-dev" 
> Sent: Tuesday, December 2, 2014 9:34:24 PM
> Subject: [hibernate-dev] Mapping defaults for @OneToOne
> 
> I'm a bit confused by the mapping defaults for @OneToOne defined in JPA 2.1.
> 
> Sections 2.10.1 and 2.10.3.1 (Bidirectional and Unidirectional OneToOne
> Relationships) says, "The foreign key column has the same type as the
> primary key of table B and there is a unique key constraint on it."
> 
> Section 11.1.41 (OneToOne Annotation) says that, by default, optional=true,
> which translates into nullable foreign key column(s).
> 
> IIUC, the default mapping is not supported by many (all?) databases, because
> a constraint violation exception will be thrown if a column has a unique key
> constraint and there is more than one null value for that column.
> 
> Currently, Hibernate does not create a unique key unless @OneToOne(
> optional=false ) is defined. I believe Hibernate is doing the right thing
> here, but it is not consistent with the spec.
> 
> Is the spec wrong in this case, or am I missing something? Please let me
> know...
> 
> Thanks,
> Gail
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> 
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Emmanuel Bernard]

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 did work on a version for master back in the days 
https://github.com/hibernate/hibernate-orm/pull/768 
 which got closed without 
being applied.
So the question is, do we want that feature for ORM 5.0 or do we not want that 
feature?
https://hibernate.atlassian.net/browse/HHH-9265 


Emmanuel
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Hardy Ferentschik]

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 run
> 
> rake clean[all]
> rake setup
> 
> Tested on Ruby 2.1.5
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev


pgpfgerS5mQx9.pgp
Description: PGP signature
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Sanne Grinovero]

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 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 did work on a version for master back in the days 
> https://github.com/hibernate/hibernate-orm/pull/768 
>  which got closed 
> without being applied.
> So the question is, do we want that feature for ORM 5.0 or do we not want 
> that feature?
> https://hibernate.atlassian.net/browse/HHH-9265 
> 
>
> Emmanuel
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Closed pull requests

[Sanne Grinovero]

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%20%22Hibernate%20ORM%22%20AND%20fixVersion%20%3D%206.0.0%20AND%20fixVersion%20not%20in%20(4.3.7%2C%204.3.6%2C%204.3.5%2C%204.3.4%2C%204.3.3%2C%204.3.2%2C%204.3.1)%20and%20status%20!%3D%20Open



On 1 December 2014 at 23:31, Steve Ebersole  wrote:
> I am finishing up the initial 5.0 work for master right now.  I will work
> on these next.  Ping me at the end of the week so I dont forget :)
>
> On Mon, Dec 1, 2014 at 3:07 PM, Andrej Golovnin  wrote:
>
>>
>> > They should get moved to the 4.3-based master.  I think I found the
>> relevant issues:
>> >
>> > * Oracle12cDialect - https://hibernate.atlassian.net/browse/HHH-9044
>> > * PostgreSQL92Dialect & PostgreSQL94Dialect -
>> https://hibernate.atlassian.net/browse/HHH-9167
>> >
>> > I have reopened them and targeted them for 5.0
>>
>> Do you already know when they will get moved to the 4.3-based master?
>> I think I should wait with my pull request until they get moved.
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Closed pull requests

[Steve Ebersole]

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 at 6:30 AM, Sanne Grinovero  wrote:

> 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%20%22Hibernate%20ORM%22%20AND%20fixVersion%20%3D%206.0.0%20AND%20fixVersion%20not%20in%20(4.3.7%2C%204.3.6%2C%204.3.5%2C%204.3.4%2C%204.3.3%2C%204.3.2%2C%204.3.1)%20and%20status%20!%3D%20Open
>
>
>
> On 1 December 2014 at 23:31, Steve Ebersole  wrote:
> > I am finishing up the initial 5.0 work for master right now.  I will work
> > on these next.  Ping me at the end of the week so I dont forget :)
> >
> > On Mon, Dec 1, 2014 at 3:07 PM, Andrej Golovnin 
> wrote:
> >
> >>
> >> > They should get moved to the 4.3-based master.  I think I found the
> >> relevant issues:
> >> >
> >> > * Oracle12cDialect - https://hibernate.atlassian.net/browse/HHH-9044
> >> > * PostgreSQL92Dialect & PostgreSQL94Dialect -
> >> https://hibernate.atlassian.net/browse/HHH-9167
> >> >
> >> > I have reopened them and targeted them for 5.0
> >>
> >> Do you already know when they will get moved to the 4.3-based master?
> >> I think I should wait with my pull request until they get moved.
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Steve Ebersole]

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 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 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 did work on a version for master back in the days
> https://github.com/hibernate/hibernate-orm/pull/768 <
> https://github.com/hibernate/hibernate-orm/pull/768> which got closed
> without being applied.
> > So the question is, do we want that feature for ORM 5.0 or do we not
> want that feature?
> > https://hibernate.atlassian.net/browse/HHH-9265 <
> https://hibernate.atlassian.net/browse/HHH-9265>
> >
> > Emmanuel
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Closed pull requests

[Sanne Grinovero]

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 those changes we want to migrate to master.

Ah thanks that clarifies. I was afraid you had plans to delete than branch.

>
> On Wed, Dec 3, 2014 at 6:30 AM, Sanne Grinovero  wrote:
>>
>> 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%20%22Hibernate%20ORM%22%20AND%20fixVersion%20%3D%206.0.0%20AND%20fixVersion%20not%20in%20(4.3.7%2C%204.3.6%2C%204.3.5%2C%204.3.4%2C%204.3.3%2C%204.3.2%2C%204.3.1)%20and%20status%20!%3D%20Open
>>
>>
>>
>> On 1 December 2014 at 23:31, Steve Ebersole  wrote:
>> > I am finishing up the initial 5.0 work for master right now.  I will
>> > work
>> > on these next.  Ping me at the end of the week so I dont forget :)
>> >
>> > On Mon, Dec 1, 2014 at 3:07 PM, Andrej Golovnin 
>> > wrote:
>> >
>> >>
>> >> > They should get moved to the 4.3-based master.  I think I found the
>> >> relevant issues:
>> >> >
>> >> > * Oracle12cDialect - https://hibernate.atlassian.net/browse/HHH-9044
>> >> > * PostgreSQL92Dialect & PostgreSQL94Dialect -
>> >> https://hibernate.atlassian.net/browse/HHH-9167
>> >> >
>> >> > I have reopened them and targeted them for 5.0
>> >>
>> >> Do you already know when they will get moved to the 4.3-based master?
>> >> I think I should wait with my pull request until they get moved.
>> > ___
>> > hibernate-dev mailing list
>> > hibernate-dev@lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Gunnar Morling]

> +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 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 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 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 did work on a version for master back in the days
> > https://github.com/hibernate/hibernate-orm/pull/768 <
> > https://github.com/hibernate/hibernate-orm/pull/768> which got closed
> > without being applied.
> > > So the question is, do we want that feature for ORM 5.0 or do we not
> > want that feature?
> > > https://hibernate.atlassian.net/browse/HHH-9265 <
> > https://hibernate.atlassian.net/browse/HHH-9265>
> > >
> > > Emmanuel
> > > ___
> > > hibernate-dev mailing list
> > > hibernate-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev