[ P R O F E S S I O N A L ]

__[ M O T I V A T I O N ]

Object oriented development has been around for about 20 years and today it is a main programming paradigm. But when it comes to persistence there are still a lot of problems. Often we are confronted with DBMS based on the relational paradigm. The fundamental difference between the relational and the object-oriented paradigm leads to object-relational mapping of object graphs to tables and relations in the database (called impedance mismatch).

The task of mapping can be costly, error-prone and time consuming. But even worse: a relational model has to be kept in mind when designing an object oriented model. Having made the annoying experience of mapping complex class hierarchies, interfaces, circular references or predefined collection classes like dictionaries often leads to modifications in the object oriented model to avoid mapping problems.

Use Persistor.NET® based on a revolutionary new technology - and you can forget about it! Pure object oriented design and no limitations to your object graphs. Spend five minutes to have a try and see what we mean.

__[ B E N E F I T ]

Pure object oriented modelling without trade-off: Use inheritance, polymorphism and interfaces without any restrictions or special treatment.

Database carefree: Persistence provided is completely transparent - no database setup, scheme definition or access specification.

Persistence for all classes: Persistence is not restricted to specialized classes but incorporates also .NET Framework classes or 3rd party clases.

Zero Configuration: Start without any previous configuration or mapping definition.

Native Queries: Queries are stated in your programming language.

Ready for .NET Framework 3.5: All new features are supported.

Supports Agile/eXtreme Techniques: The use of non-intrusive Persistor.NET® makes it easy to develop, evolve, and maintain software code in an agile manner.

__[ W H A T_ M A K E S_ T H E_ D I F F E R E N C E ]

There are already some tools around that deal with OO/Relational Mapping. What makes the difference?

Many of those tools generate business classes out of a given DB scheme. Such classes are just wrappers of tables. They miss inheritance and polymorphism as these features cannot be expressed in a relational model.

> Persistor.NET® uses sophisticated algorithms to generate the DB scheme from the Meta Data of the stored classes. There is full support of inheritance, polymorphism and interfaces.

Any of those tools need some mapping information. Often there is some (visual) editor that supports the writing of mapping information.

> Persistor.NET® does all mapping internally. No additional information has to be provided.

Most of those tools assume the business classes to be derived from some "persistence" type or to implement some "persistence" interface or be tagged with some “persistence” attribute. This impacts the business classes heavily and reduces reuse of these classes. This approach also reduces persistence to classes written by you.

> Persistor.NET® extends the Serialization mechanism of the .NET Framework. So business classes are completely unaware of persistence and .NET Framework classes or classes provided by 3rd party assemblies can be used without a glitch.

Most of those tools use their own query language that may be based on some standards. But any of them comes with severe drawbacks: the criteria are defined as strings that will be parsed at runtime. So there is no syntax check at compile time. Even worse: the query has to be stated by means of database or class internals like table names, column names or names of private fields.

> Persistor.NET® provides Native Queries: the queries are stated in the programming language you are using. So the query code is 100% typesafe, 100% compile-time checked and 100% refactorable. It is even possible to call methods from within queries.