I have an object that needs to maintain its relationship to another object as a long/key as opposed to an object. In other words, I need for this one relationship to bypass ORM and use the long value of the foreign key directly.

Normally my relationship is like so



But instead of accessing this as the class DBCircuit I want to access the column CircuitID directly. Is this possible?

The solution to this is to have one mapping for schema creation that refers to the class that will generate the foreign constraint.


And another mapping for runtime useage that just uses a property. Something like


So far this is working fine. Just as long as the 'type' used for the foreign key is always a long. I don't know how to enforce that in my DDL mapping, but I'm not going to worry about it just yet.