Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't know if it's considered a good practice by others but personally this is how i handled this in the past:</p> <p>The classes generated by EF are your DAL, and then for BL create a complementary set of classes in which you will have the structure you require (like maybe merging data from related entities in a one to one relationship) and other business logic concerns are handled (custom validation like implementing IDataErrorInfo to make it play nice with the UI in WPF for instance) and also create classes that would contain all the business layer methods relating to a type of entity, that use the BL instances and convert to and from EF entities to the BL objects.</p> <p>So, for instance, you have Customer in your db. EF will generate a class Customer, and in the BL there will be a Customer (prefix, suffix, etc.) class and a CustomerLogic class. In the BL Customer class you can do whatever is needed to satisfy requirements without having to tamper with the EF entities and in the CustomerLogic class you would have BL methods (load most valued customers, save customer with extra data, etc.).</p> <p>Now, this enables you to be loosely coupled to the datasource implementation. Another example of why this has benefited me in the past (in a WPF project) is that you can do stuff like implement IDataErrorInfo and implement validation logic in the CustomerBL classes so that when you bind the entity to a create/edit form on the UI you will benefit from the built in functionality provided by WPF. </p> <p>...My 2 cents, i am also curious to find out what is the best practice or what other solutions/points of view are.</p> <hr> <p>Also perhaps related to this topic - <a href="https://stackoverflow.com/questions/5446316/ef-4-1-code-first-vs-model-database-first">Code-first vs Model/Database-first</a></p>
    singulars
    1. This table or related slice is empty.
    1. POConfusion about where to put business logic when using Entity framework
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USdutzu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow would you handle the fields that are generated by the EF and are needed in the BL class? Can you provide a bit of a sample of your method?
      singulars
      1. PO
      1. USobb-taurus
    2. COWell, all that is missing from what i wrote it the fact that you need methods that will copy data to/from BL/DAL entities, and you isolate yourself further from the DAL by implementing a repository pattern so that you don't access the ObjectSets themselves directly, but instead you call the repositories for CRUD operations
      singulars
      1. PO
      1. USdutzu
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload