I have a composite key for my lookup tables that lets me store the language that the lookup is rendered in. I then have the key and the language as a composite pk. In order to use it else where I have to store the key and language as a composite foriegn key. I map the language to a language column and I also map a property Language to that same column. The problem is that I now have the Language column apearing twice in my SQL statements which SQL Server doesn't like. How can I avoid saving one of these languages?

Um, I got lost in all those languages a bit :) but the general solution is to use insert="false" update="false" attributes of <property> tag.

Here is a snippet of my class mapping file.

Since this isn't a property there is no update="false" option. The language is there to keep track of what language is used in the object and for all related objects. So ideally the language column is shared by the class and its children.

Let me know if you need more information.

Ok, another solution: don't map the separate Language property, just declare it like this:

property Language Language
{
get { return Sector.Language; }
}

But this will of course cause Sector to be loaded when accessing the property, I don't know if it matters for you.

sergey,

The object that has a Sector object needs to have the semantic of having a Language object. It is that property that determines all of the other language options for the most part. It seems that I may be unable to use my method with nhibernate. This is a bummer. I will keep thinking about it. Hopefully in the future nhibernate will be able to handle such requests.

dru

hmmm I wonder if there is a way to tell nhibernate if there are repeated columns to collapse them to one. I doubt it as that doesn't make much sense. hmm.....