Since the framework is still much in its infancy, I urge you to download, trial it and comment on it in the forums.
IntroductionThe aim of SQLOrm is to set the standard for the next generation ORMs. It is based on the best properties of Ibatis, Toplink, Hibernate, Spring and our experiences using raw SQL.
As an outset, SQLOrm is designed to be simple, easy to learn, and not solve every problem on the planet. The more a framework offers, the longer it takes to learn, and the more you have to fight it should you want to use it in a different way than the framework was envisaged used.
Like the simplicity of Spring revolutionized the EE development, we hope to achieve the same with SQLOrm, no less ;-)
SQLOrm consists of 4 modules all of which can be combined or used in isolation, depending on your needs. These modules are
|SQL Query Builder||ResultSet Object Mapper|
|Simple object reading and
Batch object reading
|JDBC templates and
prepared statement rectification
|Safe and simple Database refactoring
using meta data constants
Quite deliberately, features often found in ORMs such as database connection pooling and transaction handling, has been omitted. You can create your own connection pool in around 200 lines of code, or you can take advantage of any of the 1000s of connection pools already written. Some databases now even has connection pooling in the drivers. Similarly for transaction handling, you can use Spring, or Java's JTS. The most light-weight approach, though, is to use Mr. Persister's connection pool and transaction mechanisms.