On 25 July 2016 at 19:55, Steve Ebersole wrote:
> See inline...
>
>
> On Mon, Jul 25, 2016 at 1:06 PM Sanne Grinovero wrote:
>>
>> some comments inline:
>>
>> On 25 July 2016 at 18:27, Steve Ebersole wrote:
>> > I wanted to start a consolidated discussion about multi-load support.
>> > This
>> >
See inline...
On Mon, Jul 25, 2016 at 1:06 PM Sanne Grinovero wrote:
> some comments inline:
>
> On 25 July 2016 at 18:27, Steve Ebersole wrote:
> > I wanted to start a consolidated discussion about multi-load support.
> This
> > relates to a few Jiras, questioning a few different aspects of i
some comments inline:
On 25 July 2016 at 18:27, Steve Ebersole wrote:
> I wanted to start a consolidated discussion about multi-load support. This
> relates to a few Jiras, questioning a few different aspects of its current
> behavior:
>
> https://hibernate.atlassian.net/browse/HHH-10984
> https
On 25 Jul 2016 19:29, "Steve Ebersole" wrote:
>
> I wanted to start a consolidated discussion about multi-load support.
This
> relates to a few Jiras, questioning a few different aspects of its current
> behavior:
>
> https://hibernate.atlassian.net/browse/HHH-10984
> https://hibernate.atlassian.n
I wanted to start a consolidated discussion about multi-load support. This
relates to a few Jiras, questioning a few different aspects of its current
behavior:
https://hibernate.atlassian.net/browse/HHH-10984
https://hibernate.atlassian.net/browse/HHH-10617
Basically this comes down to the follo
On Sat 2016-07-23 1:55, Guillaume Smet wrote:
> Hi all,
>
> So after having discussed this issue with Emmanuel:
>
> 1/ is correct. It's the behavior we expect considering the ORM behavior. If
> we want the postal_code to be nested in homeAddress, we need to use
> @Column(name = "homeAddress.po
