ever put Inverse() on the HasMany-side.
>>
>> Den ons 16 dec. 2020 kl 10:08 skrev Venkata Krishna Reddy Sangu <
>> svkreddy...@gmail.com>:
>>
>>> Team, Any idea on this issue?
>>> Default left outer join is not getting created for Hasmany() mapping.
&g
n?
>
> Den ons 16 dec. 2020 kl 11:27 skrev Oskar Berggren <
> oskar.bergg...@gmail.com>:
>
>> Where is the HasMany() mapping?
>>
>> Also, you have put Inverse on the References() mapping. I don't think
>> I've ever tried that, I've only ever put Inverse()
think
>> I've ever tried that, I've only ever put Inverse() on the HasMany-side.
>>
>> Den ons 16 dec. 2020 kl 10:08 skrev Venkata Krishna Reddy Sangu <
>> svkre...@gmail.com>:
>>
>>> Team, Any idea on this issue?
>>> Default left outer join is
Team, Any idea on this issue?
Default left outer join is not getting created for Hasmany() mapping.
Previous version prior to NH 5.3 is working fine.
On Monday, December 14, 2020 at 11:08:12 PM UTC+5:30 Venkata Krishna Reddy
Sangu wrote:
> Hi Team,
> I have a mapping like below. And J
Hi Team,
I have a mapping like below. And Job has 'Department' as property.
References(x => x.Job)
.Column(tableMeta.Job_id)
.Not.LazyLoad().Inverse()
.Cascade.None();
Query as:
empIds - input integer ids
var jobs = _session.Query() .Where(e =>
