NHibernate foreign key set

Question

I have a:

class Garage {
    int garageID;
    ISet<Car> cars
}

should the cars class have garageID as one of its properties, as in:

class Car {
   int carID;
   int garageID;
   String name;
}

That is how it appears in the database, but wondering if the classes on the many side are supposed to have the foreign key as a property or if the ORM just adds that in when performing the SQL (assuming you can specify it in the mappings file).

Mark Perry · Accepted Answer · 2011-07-01 10:39:35Z

1

In short: No. (and yes the ORM will take care of FK based on your mapping files)

The "Car" table will have the GarageId in it but you should not add it to the Car class.

You can have a bi-directional relationship (although opinions vary on whether these are a good idea).

A bi-directional relationship would make the Car class look like this:

public class Car {
     public virtual int Id {get; set;}
     public virtual Garage Garage {get; set;}  //You can traverse back up to Garage
     public virtual string Name {get; set;}
}

If you would like me to post the Fluent/XML maps let me know.

answered Jul 1, 2011 at 10:39

Mark Perry

1,73310 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

NHibernate foreign key set

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related