SPL
3.0 officially released,
Rise
Level description
After a period of modification, SPL finally rose to 3.0, and the reason why it is to rise to 3.0, mainly because adding two ways: ODP.NET and ODBC
ODP.NET greatly enhances the accessibility of the SPL to the Oracle database. Currently using ODP.NET to connect to Oracle is the best choice. Related articles can find it online, quite a lot.
ODBC is a new feature of .NET Framework1.1, you can use ODBC connection methods to other types of databases.
Therefore, the above two connection methods are enhanced, so that SPL can support multiple databases more stronger.
SPL3.0 is basically revised in the previous version 2.0 and mainly adds some new features.
SPL3.0 revised BUG:
1. Date-comparison Times in the Oracle Database, because Oracle's date is not like SQL, you can use the string mode directly, but use to_date () conversion, currently for the Oracle database connection, this is automatic conversion Support connection type: Oracle and ODP
2. Repair the deletion error of the multi-master key, 3.0 will not report any more when using Entity.Delete ().
3. AddMatch (), addMatchPrefix () in SPL2, the system will report an error, 3.0 has been fixed, all Match operations in 3.0 are also effective.
SPL3 new features:
1. Added a connection to ODP.NET to Oracle, which is currently .NET Connect Oracle's best connection, just install ODP.NET92, use type = "ODP" in the SPL database configuration DatabaseMap .
2. Added Query's TOP function, which is the same as RETRIEVECRITERIA, mainly acting on SQL environment, as current SPL uses TOP to generate "Select Top N" effect statements, so this method is not supported for Oracle.
3. The condition condition class adds a suffix matching function addMatchSuffix, which will generate similar to the Like '% aa' effect.
4. ConditionT conditions Add a suffix mismatch function AddNotMatchSuffix, which will generate similar to the Not Like '% aa' effect
5. Added support for OBDC connection, where you can use System.Data.OBDC connection mode, as long as you configure to type = 'odbc' when the database connection is configured, you can use an OBDC connection method. About the connection method will be described separately.
6. Extend the connection method, so that the SPL is no longer limited to the connection method: setting.instance (). DatabaseMapFile = Server.MAppath (DatabaseXML);
However, you can manually increase the data connection, manually configure ClassMap loading, which will facilitate the integration of SPL and other systems. Regarding the data connection, a single chapter will be described.
7. Add CommandTimeout control on the storage process. Since the stored procedure is time consuming during the execution of the stored procedure, you need to manually control the CommandTimeout, and the default is 30 seconds, 0 is unlimited. Covering Runprocedure is as follows:
Query.RunProcedure (string storeProcName, IDataParameter [] ps, string dbName, int commandTimeout) Query.RunProcedure (string storeProcName, IDataParameter [] param, out int affected, string dbName, int commandTimeout)
The release method is the same as the last 2.0, as long as you download my sample source code, there is a detailed instructions:
SmartPersistencelayer 3.0 Example Source Code Download:
http://www.cnblogs.com/files/tintown/SPL_Webtest3.0.rar
Thank you very much for 2.0 release, everyone supports SPL.
