My views on ORM

Object relationship ing (ORM) provides a conceptual and easy-to-understand Method for modeling data.
The ORM methodology is based on three core principles:
Simple: data is modeled in the most basic form.
Communication: the database structure is documented in a language that anyone can understand.
Accuracy: Create a correctly standardized structure based on the data model.

Typically, modelers collect data from familiar applicationsProgramHowever, people who are not skilled in Data Modeling develop information models. Modelers must be able to communicate with data structures at the conceptual level with terms that non-technical enterprise experts can understand. Modelers must also be able to process sample data with simple unit analysis information. Orm is specially designed to improve this connection.

At present, there are some open-source frameworks in this field. the system construction under the net system is more concerned with the ORM framework in this field. According to my personal experience, I have some opinions on the current situation:

1. First, the ORM tool must be non-relational to the database platform. At the same time, you can quickly and conveniently build database service components through database tables, which can be easily converted into tables and views. objects in the. NET EnvironmentCodeTo facilitate the use of the system;

2. A simple call method should be provided. After simple configuration, the user can connect to the database, specify the database type, and provide a simple call method, implement CRUD (Create/retrieve/update/delete) operations on the database,

3. Low performance loss, common data operations, and complete data access logs.

Considering these factors, VS has proposed some simple implementation of ORM.