pterodactilus Goto Github PK

c-collection-manager-entity-mapper-

This is a working version of the handwritten mini ORM, working with the database and C # collections. Productivity is quite high, resource consumption is minimal. This ORM works directly with SQL Server stored procedures. The code is accompanied by descriptions and example .Net Console project showing the technique of ORM using. Introduction Data is stored on the SQL server and when a large number of simultaneously connected users access it this creates a serious load on the database server. In addition, often database queries fetch the same data, which is not good in terms of server and applications load. One of ways to optimize the database in ligament with client application is to reduce traffic and to store data already received from the server on the client or in the middle application tier. Or to store already received data on the application server, especially when the database server and client applications are distributed across the network. For this purpose, the collections stored in the Session or at the application level are the best suited. Below is a solution for the data management layer in the combination of MS Sql Server with a C # application, suitable for .Net. In whole this is a loosely bound entity mapper projecting the application's business logics onto database tables using T-SQL stored procedures. In this realization of ORM the tables, procedures, and entity constructors are written by hand. They are not generated automatically by a mapper. At the same time, the entity code and stored procedures can be minimased and simplified and fully control by the developer. As well as a process of data obtaining. All client code is reduced to writing the simplest one string calls to the mappers methods and to creating the simplest constructors for entities by template. The library allows you to implement fairly complex data structures in your application, without bothering about difficult and tedious questions of data acquisition and conversion issue, allowing you to pay more attention to the develop of business logic and UI. There no need to worry about migrations, context, etc. At the same time, ORM completely relieves the developer from direct communicating with ADO - data sets, tables, rows, and other data access components. No need to open or track connections, create commands or operate with adapters. Because ORM works at a higher level of data abstraction with collections of entities and their instances. At the same time you will be completely protected from memory leaks. At the same time you are free for create any complexity application logic at the primary data level.