Ndo v3.1 released!

The new features include:

1. Oracle Database Support (using the system. Data. oracleclient or ODP. Net driverProgramYes)

2. Oracle is supported in the following ways:

1) Auto-increment PK generated by sequence

2) cud by stored procedure

3) database Paging

3. isqlhelper operation interface covering all ADO. netapi. Integrate sqlhelper and oraclehelper and use session reality.CodeIt can be independent from a specific database.

4. Automatic session management. The session management method in NH is used for reference. Ndo has four built-in management policies:

1). Per Web Request (for a client session and a connection in B/S architecture)
2). Per process (for a Single-threaded c/s program, a process/APP is connected once)
3). per Thread (used for multi-threaded C/S programs, one thread is connected at a time)
4). per unit of work (that is, per call, applicable to various runtime environments, one work unit and one connection)

5. The tool class entityconverter <t> converts ADO. NET data (datareader, datatable, dataset) to an entity class. Supports Ndo attribute and automatic name mapping conversion.

6. A web project, demo how to use the new Ndo

Old feature modification:

1. You are no longer allowed to create simpledao <t> instances to avoid confusion in session management. Change the constructor to internal.

2. configuration. addconnection (connectionnameinconfig) is provided, and a conn string name is provided. Ndo automatically checks dirver.

3. Upgrade postshparp to 1.5.* (for lazyload)

4. Updated the unit test code. added a multi-threaded test program.

5. uppercase Ndo-> lowercase Ndo. Unified name.

 

Current problems:

1. hasmany can only be used when [lazyload] is used, but it does not affect usage.

2. It is useless to set [lazyload] For belonsto.

 

Preview page:

Unit testing uses Oracle's ODP. NET data driver

SQL Server 2005 performance test data:

Note that the bottom layer of activerecord uses nhibernate2.x, so you can regard it as nhib.pdf.

 

Oracle 10 Gb performance test data (note that the server memory is 2 GB, so it is much faster ):

Demo web site

 

Options for Ndo and Nhibernate:

1. for small and medium-sized projects that do not need to be distributed and do not require database migration, use Ndo. to support multiple databases, use nhib.pdf. it is not suitable to Use ORM in distributed architecture, and it will affect the overall performance and scalability. XML + dataset is the best, that is, some APIs with large granularity.

2. If we do not have a deep understanding of Nhibernate and feel that there is a risk in project creation, we suggest using Ndo. How can we say that Ndo is developed by ourselves? Every line of code is well known.

3. to be flexible, you can configure hql and use nhib.pdf for SQL.

4. To improve the performance, use Ndo + sp.

5. For databases not supported by Ndo, such as SQL ce and SQLite (support will be added later), nhib.pdf is used.

6. users who do not want to configure HBM. XML are not sensitive to inheritance and use Ndo

7. If you do not want to process the database connection by yourself, you can use the Ndo Session Manager and isqlhelper operation interfaces, and then use entityconverter to implement a realistic oo

8. Think very Oo, or your class has its own base class, you cannot use ndorecordbase, use nhib.pdf