title: Linq vs. database views
body: <p>Here’s an interesting question. Suppose we have related tables in the database, for example, Instrument and Currency. Instrument table has a currency_id field that is mapped to entry in Currency table. In Linq land what’s the better way:</p>
  
  <p>a) Create Instrument and Currency entities in the DataContext and then create association or simply use join in Linq queries or</p>
  
  <p>b) Create a view in the database that joins Instrument and Currency (thus resolving currency_id to currency code) and use that as an entity in Linq context?</p>