From a66f15e35501715190e05d1bd669cf64dcced76f Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Wed, 7 Jan 2009 19:36:43 +0000 Subject: [PATCH] Minor edits. --- src/java/com/samskivert/depot/DepotRepository.java | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/java/com/samskivert/depot/DepotRepository.java b/src/java/com/samskivert/depot/DepotRepository.java index 24335f2..f9ec34d 100644 --- a/src/java/com/samskivert/depot/DepotRepository.java +++ b/src/java/com/samskivert/depot/DepotRepository.java @@ -79,7 +79,7 @@ public abstract class DepotRepository * all the records that satisfy the query, then we acquire the actual requested data for * each key. The cache is consulted and updated in both steps: for the first, see if we've * already executed precisely this query and cached the resulting key set. For the second - * phase, searchthe cache for each key in said set, and retrieve the corresponding data + * phase, search the cache for each key in said set, and retrieve the corresponding data * record from there when possible. Finally execute a database query to retrieve the data * for any keys that were not in the cache, making sure to cache them in the process. * @@ -103,7 +103,8 @@ public abstract class DepotRepository * @Computed records and arbitrarily complicated queries. Note however that as with KEYS, * there is currently no automatic invalidation and it is potentially very memory intensive. */ - CONTENTS }; + CONTENTS + }; /** * Creates a repository with the supplied persistence context. Any schema migrations needed by