MapperDao ORM library 0.7.0 released, with support for oracle,derby,pagination

Hi all,

   I am happy to announce the release of version 0.7.0 of the
MapperDao ORM library for Scala.

https://code.google.com/p/mapperdao/

Since 0.6.0, the following features were added:

- a driver for oracle
- a driver for derby
- simplified mappings
- pagination capability for queries (returns only a range of rows or a
page of rows, each page containing a number of rows)
- configurable data retrieval: skip loading of a set of relationships
to optimize performance
- mapping of class hierarchies

All new features follow the "map in one database, run in all supported
databases" feature of mapperdao, which currently allows applications
to persist & query data in postgresql, mysql, oracle and derby
databases with sql server driver coming soon.

MapperDao is using spring framework's JdbcTemplate for low level
database access with excellent transaction support, allows for a clean
domain model with zero references to the ORM layer, supports and
encourages immutability for domain classes, type safe mappings and
uses a type safe DSL similar to select statements to query for
entities.

AsyncFP Release 1.2.5--database recovery

Release 1.2.5 of AsyncFP now supports rebuilding a small datastore
from the log files. This is allows you to change the max size of the
database or recover from a corrupted database. And recovery is very
fast with each log file processed as a single transaction, so there is
only a single write to the datastore for each log file that is
processed.

AsyncFP is a scala project with composable actors that interoperate
both synchronously and asynchronously. The current focus is on
providing a kit for creating high-performance custom NoSQL databases.
The small datastore currently under development is a crash-proof in-
memory database supporting multiple queries or single update. Updates
write to a backing disk file.

Bill La Forge
https://github.com/laforge49/Asynchronous-Functional-Programming/wiki

AsyncFP release 1.3.0--batch update and opportunistic locks

Release 1.3.0 of AsyncFP includes the small records datastore, an in-
memory, crash proof database that supports batch updates and
opportunistic locking. See
https://github.com/laforge49/Asynchronous-Functional-Programming/wiki/SmallRecordsDataStore

AsyncFP is a Scala project with composable actors that interoperate
both synchronously and asynchronously. The current focus is on
providing a kit for creating high-performance custom NoSQL databases.
The small datastore currently under development is a crash-proof in-
memory database supporting multiple queries or single update. Updates
write to a backing disk file. Home: https://github.com/laforge49/Asynchronous-Functional-Programming/wiki

Bill La Forge

Re: AsyncFP release 1.3.2--the swift datastore

AsyncFP release 1.3.2--the swift datastore

A new datastore, Swift, only periodically updates its datastore and on
restart the tail of the old log file is used to create a current
version. The transaction rate is now limited primarily by flushes to
the log file. Using a 5,400 rpm drive, Swift does 5,552 transactions
per second (2,776 being updates)--when not flushing the log file. But
flushing the log file is necessary if want to offer any assurance that
there will be no lost transactions. And that brings the transaction
rate down to 76 per second (38 updates).

Bill La Forge
https://github.com/laforge49/Asynchronous-Functional-Programming/wiki

Announcing docs.scala-lang.org, Scala Documentation Repository

We're happy to announce the (beta) launch of the official Scala  
Documentation repository, at http://docs.scala-lang.org.

The Scala Documentation repository is meant to be a centralized,  
organized repository of many different types of documentation,  
including:
- Guides
- Overviews
- Tutorials
- Glossary
- Cheatsheets
- Scala Improvement Process documents
- the Scala Style Guide

Two equal focuses of its design are that (1) documents be easy for  
users to find, and (2) it is as easy as possible for core committers  
and the community alike to contribute and evolve documentation.

As community involvement is a central goal of the Scala Documentation  
repository, we urge those that have found holes in current  
documentation, or areas in which existing documentation can otherwise  
be improved, to participate and help us to improve that documentation  
for others in the future.

We are also happy to consider accepting entirely new guides/overviews,  
tutorials, or cheatsheets.

To submit a document one must simply fork the repository at  
http://github.com/scala/scala.github.com, add their document to the  
appropriate location on the site (written in Markdown markup), and  
submit a pull request.

For more information on contributing, please see  
http://docs.scala-lang.org/contribute.html

Feedback welcome!
(via Feedback tab on http://docs.scala-lang.org)

Cheers,
Heather Miller