Share the just-released ORM framework XLinq and orm framework xlinq
Vomit
After being busy for more than a month, XLinq was "usable", and the BUG was "few points". Now it is ready to replace EF. It has been initially used in its own project.
EF has many advantages and many disadvantages. I will introduce some of the biggest disadvantages (maybe this is because I won't use it)
Deleted
Performance, in fact, the performance does not seem so bad. I tested and queried 0.16 million data records and nearly one hundred fields. Nima was able to handle it in 16 seconds ····
Cannot remember for now
Share
There are also a lot of people who vomit EF, so I have nothing to look for if I have done things again ···
So, for the above pitfalls, I have found a lot of ORM (in fact, it seems that there are not many), tried alinq, dbentry.net, alinq not to mention, paid, and I can't afford it, at that time, it was too much pitfall, And it was useless. By the way, there was SOD, written by Dr. deep blue ···
However, I have also written An ORM that supports LINQ, but the code is good enough, but I have finally written it, and I know some principles. In fact, it is more to exercise, after all, it is quite difficult to support LINQ, so this time I write it myself again. The following functions are available for the sake of simplicity:
Usage notes
It looks like a simple basic function, but it is really a tear. There are still performance tests in the plan, but let's take a look at how many people are interested!
If you want to discuss the related technologies or obtain the source code, please contact QQ Group 74522853.
Test source code: http://files.cnblogs.com/files/wzxinchen/XlinqDemo.zip