|

Welcome to the ObjectMapper .NET project - an impressive open source project for object persistence, proven in real-world projects. Object relational mappers aim to bridge the gap between object oriented programming and relational database models. The ObjectMapper .NET offers state-of-the-art object mapping functionality, yet it also provides advanced features that set it apart from other o/r mappers.
Tailored to achieve maximum performance and development ease-of-use this technology will give developers the ability to build business components with unprecedented productivity and optimal runtime performance.
The entity model drives the database layout, thus enabling real model driven development.
The business entity model can be designed using the CASE tool of your choice - it may even be designed by business analysts rather than classical developers. The entities and their properties may then be decorated with declarative attributes - either within the CASE tool or within the generated C# code. These attributes may tell the ObjectMapper .NET simple things, such as the length of a text field, or they may provide more complex information, or to allow fields to be picked from another table. In many cases the default behaviour will suffice - reducing the amount of work efficiently.
The ObjectMapper .NET - and this is really a great part, will use the meta information of the model to create a DDL file to create the database - including all constraints. It also supports database versioning.
No need to maintain a separate DDL. No need to manually synchronize properties and database table columns. All contained in one single source, thus eliminating maintenance hurdles and a whole class of error conditions.
Keywords: NET, Mapper, The, ObjectMapper, AdFactum, Object, SQL, Framework, Query, API, Localization, Persistence, Integrated, Mechanism, Stateless, Extracts, Possible, Provides, Stateful, Supports, Paging, Grids, DBMS, Main, That, With, All, DDL, For, Web
Recent Changes: Changes:
- Added a new Attribute called "View" to identify a class as database view. This has been necessary since database views have to be handled slidly different to database tables.
- If no primary key is defined within a class or interface, aggregated entites or interfaces will always be mapped to a GUID as primary key.
- New SqlFile ExecuteScript Method to enable the user to react on thrown exceptions.
BugFixes:
_ Exposed an empty table set for the With-Clause. This is for preventing the Parent SQL to use the tables of the With-Clause within the own From-Clause. Before fixing this bug, a cartesian product could be possible when using the With-Clause.
For detailed information what changed have a look at the blog at http://blog.objectmapper.net
Install Support: Install and Uninstall
Supported Languages: English
Additional Requirements: Microsoft .NET Framework 1.1
PAD file URL: http://www.objectmapper.net/download/ObjectMapper.xml
|