Depot

A library for relational-database-based persistence in Java.

License	The (New) BSD License
GroupId	com.samskivert
ArtifactId	depot
Last Version	1.7.4
Release Date	Apr 23, 2017
Type	jar
Description	Depot A library for relational-database-based persistence in Java.
Project URL	https://github.com/threerings/depot
Source Code Management	https://github.com/threerings/depot/

Download depot

Filename	Size
depot-1.7.4.pom
depot-1.7.4.jar	422 KB
depot-1.7.4-sources.jar	185 KB
depot-1.7.4-javadoc.jar	582 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/com.samskivert/depot/ -->
<dependency>
    <groupId>com.samskivert</groupId>
    <artifactId>depot</artifactId>
    <version>1.7.4</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/com.samskivert/depot/
implementation 'com.samskivert:depot:1.7.4'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.samskivert/depot/
implementation ("com.samskivert:depot:1.7.4")

Apache Buildr

'com.samskivert:depot:jar:1.7.4'

Apache Ivy

<dependency org="com.samskivert" name="depot" rev="1.7.4">
  <artifact name="depot" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='com.samskivert', module='depot', version='1.7.4')
)

Scala SBT

libraryDependencies += "com.samskivert" % "depot" % "1.7.4"

Leiningen

[com.samskivert/depot "1.7.4"]

Dependencies

compile (2)

Group / Artifact	Type	Version
com.google.guava : guava	jar	18.0
net.sf.ehcache : ehcache Optional	jar	1.6.0

provided (1)

Group / Artifact	Type	Version
org.apache.ant : ant	jar	1.7.1

test (3)

Group / Artifact	Type	Version
junit : junit	jar	4.10
org.hsqldb : hsqldb	jar	2.2.9
com.samskivert : samskivert	jar	1.9

Project Modules

There are no modules declared in this project.

Depot Persistence Library

Depot is a relational persistence library for Java. It is an ORM library, but has aims that are somewhat different from the popular "managed" persistence libraries like Hibernate and others.

Design Goals

• Eliminate (as much as possible) the use of raw SQL, instead providing Java classes that allow the expressions of queries and updates in as concise but compile-time checkable a manner as possible.
• Reduce the pain of schema and data migrations as much as possible, but not so much that the system used to do the migrations is too complex for anyone to understand or use properly.
• Use annotations to layer database metadata over the top of (almost) POJOs.
• Use annotations that are syntactically and semantically equivalent to EJB3 persistence annotations wherever possible.
• Support multiple database backends (currently MySQL, Postgresql and HSQLDB).
• Provide caching support (currently integrated with EHCache).
• Keep an eye toward eventual support for sharded databases (not yet implemented).

Depot studiously avoids ever doing anything magical. You only access the database when you make a method call requesting that records be read from the database or records be updated in the database. Depot attempts only to be a concise, compile-time checkable veneer over raw database access that conveniently models database tables as Java objects.

In this way Depot is more of an evolution of DAO-like libraries of the past than a pared down sibling of the managed persistence libraries of the present. It distinguishes itself by taking advantage of annotations to concisely express database metadata and by striving to stay out of your way as much and surprise you as little as possible.

Code Examples

Here's are some example to give you a taste of what code using Depot looks like.

• A simple code example
• Various example queries

API docs are also available.

Features

Depot supports a number of very useful features. Here are a few of the main features for which time has permitted documentation:

• Schema and Data migration
• Caching

Getting Started

If you want to use Depot on your project, check the following page for information on getting Depot and dependencies via Maven or manually, as well as what sort of configuration Depot requires to start talking to your database.

• Configuring and integrating Depot with your project

Discussion

Feel free to pop over to the OOO Libs Google Group to ask questions and get (and give) answers.

History

Depot was started in September of 2006 by Three Rings as a part of their Whirled project. Its primary authors are Michael Bayne and Pär Winzell.

License and Distribution

Depot is released under the New BSD License. The most recent version of the library is available at https://github.com/threerings/depot/

Three Rings

Versions

Version
1.7.4 Apr 23, 2017
1.7.3 Apr 3, 2016
1.7.2 Oct 12, 2015
1.7 Mar 12, 2015
1.6.5 Jun 26, 2014
1.6.4 Jun 26, 2014
1.6.2 Sep 17, 2013
1.6.1 May 7, 2013
1.6 Oct 9, 2012
1.5 Sep 30, 2011
1.2 Jan 8, 2011
1.1 Nov 20, 2010
1.0 Sep 23, 2010