Moon. ORM3.9 released, full technical strategy. The fastest ORM release.

Moon. ORM

I. Introduction

This article focuses on Moon. ORM technology and usage instructions. if you have other questions, please leave a message. this article focuses on Moon. in ORM3.9, a technical preview will be made for version 4.0. this article analyzes Moon from the actual situation. ORM. (Technical Group: 21696534)

Ii. features and advantages of Moon. ORM

---- All wisdom is simple, but not known. It is also the main feature of Moon. ORM: the greatest truths to simplicity.

1. high performance is Moon. one of the advantages of ORM is also one of the main purposes of my architecture. As I said before, it was designed to compensate for performance problems encountered in the project. it can be said that the entire framework data processing adopts the pure ADO. NET is encapsulated and combined with EMIT to quickly generate entities (of course, you can also use 4.0 of the Code Generator to complete pure ADO. NET Development ). I have to admit the elegance brought by the linq and lambda statements, but at the same time, we need to acknowledge the limitations of linq. some people may say that they can make up for it by means. For example, some people write articles to Improve the Performance of linq, but we need to acknowledge the two facts that they can be optimized only after they identify the linq system. That is to say, the nature of linq determines performance loss. the second time that we use linq, it is not a silver bullet, because it is almost impossible for the responsible scenario to do so. What's more, the SQL statements generated by linq are not necessarily what you really want. (Note: I am not a competitor to linq, but to tell the truth, as I once said: in actual development, there is no silver bullet, and there is only a balance point. It is enough for an architecture that can meet the needs to solve the actual situation) in addition, I do not need to write another framework to create something similar to nhib.pdf or an Entity Framework. I always think that we need to develop a unique feature and advantage.

2. ease of use. I think Moon. ORM should be used to know this. It is easy to configure, SMART awareness, and code generator assistance. Moon can be used for SQL.

3. supports multiple databases and multiple data sources. moon. ORM is your best choice. for example, if your system uses MSSQL by default and you want to use MYSQL at the same time, you only need to instantiate an engine. DBFactory. getEntity <Person> (pjy_AdminRoleTable.RoleID.BiggerThan (0), new MYSQL ("connection string"); of course, you can make the engine global.

4. Syntax sugar function. The result of my personal use is about 70% of my actual needs.

5. native support for. NET 2.0.

6. database transformation problems, if you find that one day your database needs to be changed from mysql to mssql, you only need to change your configuration file. (Of course, you need to pay attention to the SQL syntax difference, if you are using native SQL for operations ).

Iii. maintenance problems.

Someone once said, 'No source code, so I can't use'. I can't beat Microsoft, but we can change to another location: Do you know the bug in. net framework 3.5 sp1? Is there any bug message in Microsoft's library? Moon. ORM Standard Edition, free of charge (including API documentation) and group technical support. for enterprise users, I will provide specialized services and technical support as well as a more elegant and powerful Enterprise Edition Moon. orm code generator tools and technical training materials.

Iv. Comparison of similar products.

Http://www.cnblogs.com/humble/archive/2012/05/20/2510756.html

V. 4.0 feature Preview

4.0 oracle will be supported on the basis of 3.9. for data query operations, the second-level cache processing will further prompt the performance. provides more powerful transaction functions. in fact, in the version to be released, I have improved the query performance to the ultimate performance of pure SQL queries. see the figure below.