Hi,

By the way,

This issue goes further than the scope that GenPro covers, but it's important to state it.

In fact, the mapping compiles just fine. When I try to make a Linq to NHibernate sentence, if the **order **of the parent's primary keys on the mapping is not as the compiler would expect. The SQL generated matches different keys, for example:

select *
from son s, parent p

where

s.Id1Parent = p.Id2Parent

I'll be posting this issue to the NHusers group... let see what happens

regards.

Please provide more info to understand your problem. What are the mappings? what is the code you are executing that reproduces the issue? Are you using the latest LLBLGen runtime library version?

Hi Daelmo,

I mean that when you map composite keys they must remain the same order between fields.

I have discussed this issue in more detail on this post:

http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=19141

I think this post is not longer needed

regards