Databases
StackOverflow2013
Postsdbo
POReflection performance for Data Access Layer
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReflection performance for Data Access Layer
    primarykey
    data
    text
    <p>I had created a framework for a project in the past that one of it’s functionalities was to load the Database info into my business entity classes (only properties no methods) and from the Business entity classes to the database loading the parameters collection of the stored procedure to be executed. To this on that project I decorated the Business Entity Classes with the DB Filed info and SP Parameters like the sample below and let the framework load the entity or the Parameters collection using reflection so I didn’t had to generate new code for the maintenances.<br/> But now I am creating a new and much bigger project, of course much more code to maintain, but where performance is critical and was wondering if it’s worth using reflection for all the load and kept the code much simpler or actually generate all the code and maintain all the changes?<br/> I had did some search, read some of the documentation on MSDN, but still found lots of different opinions, people that liked reflection showing numbers that the overhead is not that bad, and others saying that it’s actually better to keep away from reflection <br/><br/> Technical specs for the new app:<br/> Language: C#<br/> .Net Version: 3.5<br/> Application Type: Classic Web Forms accessing Logic components and Data Access Tier also in C#<br/> Database: SQL Server 2008<br/> Database Abstraction Layer: All access to the DB is made via Stored Procedures and User Defined Functions.<br/> <br/><br/> Sample Code:<br/></p> <pre><code> // Decorated class [System.Serializable()] public class bMyBusinessEntity{ private Int64 _MyEntityID; private string _MyEntityName; private string _MyEntityDescription; [aFieldDataSource(DataColumn = "MyEntityID")] [aRequiredField(ErrorMessage = "The field My Entity ID is mandatory!")] [aFieldSPParameter(ParameterName="MyEntityID")] public Int64 MyEntityID{ get { return _MyEntityID; } set { _MyEntityID = value; } } [aFieldDataSource(DataColumn = "MyEntityName")] [aFieldSPParameter(ParameterName = "MyEntityName")] public string MyEntityName{ get { return _MyEntityName; } set { _MyEntityName = value; } } [aFieldDataSource(DataColumn = "MyEntityDescription")] [aFieldSPParameter(ParameterName = "MyEntityDescription")] public string MyEntityDescription{ get { return _MyEntityDescription; } set { _MyEntityDescription = value; } } } // To Load from DB to the Object: using (DataTable dtblMyEntities = objDataSource.ExecuteProcedure(strSPName, objParams)) { if (dtblMyEntities.Rows.Count &gt; 0) { DataRow drw = dtblMyEntities.Rows[0]; oFieldDataSource.LoadInfo(ref objMyEntity, drw); return objMyEntity; } else throw new Exception(“Row not found!”); } // To Load from the Object to the DB oDataSource objDataSource = new oDataSource(); IDbDataParameter[] objParams = objDataSource.GetProcedureParameters(strSPName); oFieldSPParameter.LoadInfo(objParams, objMyEntity); objDataSource.ExecuteNonQuery(strSPName, objParams); </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USClaiton Lovato
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    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
    1. VO
      singulars
      1. POReflection performance for Data Access Layer
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POReflection performance for Data Access Layer
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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