Thanks for the quick update James!
On 4 Lut, 23:45, James Gregory wrote:
> Yep, this is a known bug. Until we fix it you need to explicitly specify the
> table name for both sides of the relationship.
>
> On Wed, Feb 4, 2009 at 10:42 PM, wrote:
>
> > I have exactly the same issue ... something
No problem, I actually encountered this while writing some recent
documentation.
If you're interested as to a reason why this is more difficult to fix than
it may seem: our mappings are currently completely separate, and for things
like collections only the types of the properties are analysed, not
Yep, this is a known bug. Until we fix it you need to explicitly specify the
table name for both sides of the relationship.
On Wed, Feb 4, 2009 at 10:42 PM, wrote:
>
> I have exactly the same issue ... something seems to be not correct.
>
> I think on one side there should be inverse="true" whic
I have exactly the same issue ... something seems to be not correct.
I think on one side there should be inverse="true" which fluent-nh
should use to detect real parent
--
Cheers, Marek
On 9 Gru 2008, 06:13, karron wrote:
> I configure the ManyToMany table name as the following.
>
> persistenc
