[ANN] O/R Broker 3.0.0 final released

I'm happy to announce the release of O/R Broker 3.0.0 final for Scala 2.8.

• O/R Broker is a JDBC framework that simplifies access to any JDBC database using type safe[*] declarative Scala configuration with external SQL statements.
• It's designed to ensure explicit transactional boundaries and supports, but does not enforce nor provide, external transaction management.
• Supports stored procedure calls and generally suitable for legacy database access, where tables, indices, procedures, etc cannot be modified to satisfy the ORM du jour.
• O/R Broker supports immutable domain classes, something no other JDBC framework (to my knowledge) allows. In fact, there are no limitations on how you choose to design your class, other than what is inherent in object-relational mapping. There are no annotations to apply, no traits or interfaces to extend.
• Full support for auto-generated keys and batch processing.

Check out the API, and the wiki.

---
[*] JDBC is inherently not type safe, so O/R Broker cannot improve on that, but ensures type safety at every point further up the chain.

I'm happy to announce the release of O/R Broker 3.0.0 final for Scala 2.8.

• O/R Broker is a JDBC framework that simplifies access to any JDBC database using type safe[*] declarative Scala configuration with external SQL statements.
• It's designed to ensure explicit transactional boundaries and supports, but does not enforce nor provide, external transaction management.
• Supports stored procedure calls and generally suitable for legacy database access, where tables, indices, procedures, etc cannot be modified to satisfy the ORM du jour.
• O/R Broker supports immutable domain classes, something no other JDBC framework (to my knowledge) allows. In fact, there are no limitations on how you choose to design your class, other than what is inherent in object-relational mapping. There are no annotations to apply, no traits or interfaces to extend.
• Full support for auto-generated keys and batch processing.

Check out the API, and the wiki.

---
[*] JDBC is inherently not type safe, so O/R Broker cannot improve on that, but ensures type safety at every point further up the chain.

Anything I ought to change in that Stack Overflow answer that mentions it?

On Sat, Aug 14, 2010 at 12:30 PM, Nils Kilden-Pedersen <nilskp@gmail.com> wrote:

I'm happy to announce the release of O/R Broker 3.0.0 final for Scala 2.8.

• O/R Broker is a JDBC framework that simplifies access to any JDBC database using type safe[*] declarative Scala configuration with external SQL statements.
• It's designed to ensure explicit transactional boundaries and supports, but does not enforce nor provide, external transaction management.
• Supports stored procedure calls and generally suitable for legacy database access, where tables, indices, procedures, etc cannot be modified to satisfy the ORM du jour.
• O/R Broker supports immutable domain classes, something no other JDBC framework (to my knowledge) allows. In fact, there are no limitations on how you choose to design your class, other than what is inherent in object-relational mapping. There are no annotations to apply, no traits or interfaces to extend.
• Full support for auto-generated keys and batch processing.

Check out the API, and the wiki.

---
[*] JDBC is inherently not type safe, so O/R Broker cannot improve on that, but ensures type safety at every point further up the chain.

--
Daniel C. Sobral

I travel to the future all the time.

Anything I ought to change in that Stack Overflow answer that mentions it?

On Sat, Aug 14, 2010 at 12:30 PM, Nils Kilden-Pedersen <nilskp@gmail.com> wrote:

I'm happy to announce the release of O/R Broker 3.0.0 final for Scala 2.8.

• O/R Broker is a JDBC framework that simplifies access to any JDBC database using type safe[*] declarative Scala configuration with external SQL statements.
• It's designed to ensure explicit transactional boundaries and supports, but does not enforce nor provide, external transaction management.
• Supports stored procedure calls and generally suitable for legacy database access, where tables, indices, procedures, etc cannot be modified to satisfy the ORM du jour.
• O/R Broker supports immutable domain classes, something no other JDBC framework (to my knowledge) allows. In fact, there are no limitations on how you choose to design your class, other than what is inherent in object-relational mapping. There are no annotations to apply, no traits or interfaces to extend.
• Full support for auto-generated keys and batch processing.

Check out the API, and the wiki.

---
[*] JDBC is inherently not type safe, so O/R Broker cannot improve on that, but ensures type safety at every point further up the chain.

--
Daniel C. Sobral

I travel to the future all the time.