Databases
StackOverflow2013
Postsdbo
POBest pattern to implement Translators between DB type object to Business type object
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest pattern to implement Translators between DB type object to Business type object
    primarykey
    data
    text
    <p>Our project had implemented Entity framework and we were floating the entity object type across all layers. Due to the sheer size of those objects we have decided to have business entities and data entities. Now I am confused as in 1) Where to implement the translation of these objects 2) How i.e any patterns or practices which I should follow to get better results.</p> <p>*<em>Edited *</em> Thanks for all the replies I am looking into Automapper and found it might fit well. But instead of using a library I wanted to create my own translator which would seem like reinventing the wheel. But my thought is I would have a lot more control on things then.</p> <p>So going back to the original quesiton </p> <ol> <li>On which layer should I implement my translation i.e we have an N-tire app and there are two schools of thought one being we should have a business layer and treat it as a facade and implement all translation and other business logic there and treat all others layer as a dumb layer which have no knowledge about the other layers and keep minimum reference of them so the data layer would be throwing out the same data entities and can be reused in another project where the Business object are somewhat different then our current object. The second school of thought is that the data layer should be returning and accepting business entities which would restrict non-database developers from unnecessary call on the db layer to create a business entitie.</li> <li>Any patterns which are there for such kind of translation libraries.</li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNikshep
    1. USNikshep
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest pattern to implement Translators between DB type object to Business type object
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you planing on using WCF?
      singulars
      1. POBest pattern to implement Translators between DB type object to Business type object
      1. USJethro
 

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