Berkeley DB Reference Guide: Retrieving items by index key
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++

### Berkeley DB Reference Guide: Java API Tutorial - Index |

### Retrieving items by index key

Retrieving information via database index keys can be accomplished using the standard Java collections API, using a collection created from a DataIndex rather than a DataStore . However, the standard Java API does not support duplicate keys: more than one element in a collection having the same key. All three indices created in the prior section have duplicate keys because of the nature of the city, part number and supplier number index keys. More than one supplier may be in the same city, and more than one shipment may have the same part number or supplier number. This section describes how to use extended methods for stored collections to return all values for a given key.

Using the standard Java collections API, the Map.get method for a stored collection with duplicate keys will return only the first value for a given key. To obtain all values for a given key, the StoredMap.duplicates method may be called. This returns a Collection of values for the given key. If duplicate keys are not allowed, the returned collection will have at most one value. If the key is not present in the map, an empty collection is returned.

The Sample class is extended to retrieve duplicates for specific index keys that are present in the database.

>     import com.sleepycat.bdb.collection.StoredIterator;
>     import java.util.Iterator;
>     ...
>     public class Sample
>     {
>         ...
>         private SampleViews views;
>         ...
>         private class PrintDatabase implements TransactionWorker
>         {
>             public void doWork()
>                 throws Exception
>             {
>                 printEntries("Parts",
>                               views.getPartEntrySet().iterator());
>                 printEntries("Suppliers",
>                               views.getSupplierEntrySet().iterator());
>                 printValues("Suppliers for City Paris",
>                              views.getSupplierByCityMap().duplicates(
>                                                 "Paris").iterator());
>                 printEntries("Shipments",
>                               views.getShipmentEntrySet().iterator());
>                 printValues("Shipments for Part P1",
>                              views.getShipmentByPartMap().duplicates(
>                                                 new PartKey("P1")).iterator());
>                 printValues("Shipments for Supplier S1",
>                              views.getShipmentBySupplierMap().duplicates(
>                                                 new SupplierKey("S1")).iterator());
>             }
>         }

>         private void printValues(String label, Iterator iterator)
>         {
>             System.out.println("\n--- " + label + " ---");
>             try
>             {
>                 while (iterator.hasNext())
>                 {
>                     System.out.println(iterator.next().toString());
>                 }
>             }
>             finally
>             {
>                 StoredIterator.close(iterator);
>             }
>         }
>     }

The StoredMap.duplicates method is called passing the desired key. The returned value is a standard Java Collection containing the values for the specified key. A standard Java Iterator is then obtained for this collection and all values returned by that iterator are printed.

Another technique for retrieving duplicates is to use the collection returned by Map.entrySet . When duplicate keys are present, a Map.Entry object will be present in this collection for each duplicate. This collection can then be iterated or a subset can be created from it, all using the standard Java collection API.

Note that we did not discuss how duplicates keys can be explicitly added or removed in a collection. For index keys, the addition and deletion of duplicate keys happens automatically when records containing the index key are added, updated, or removed.

While not shown in the example program, it is also possible to create a store with duplicate keys in the same way as an index with duplicate keys--by calling Db.setFlags with the Db.DB_DUPSORT flag. In that case, calling Map.put will add duplicate keys. To remove all duplicate keys, call Map.remove . To remove a specific duplicate key, call StoredMap.duplicates and then call Collection.remove using the returned collection. Duplicate values may also be added to this collection using Collection.add .

The output of the example program is shown below.

>     Adding Suppliers
>     Adding Parts
>     Adding Shipments

>     --- Parts ---
>     PartKey: number=P1
>     PartValue: name=Nut color=Red weight=[12.0 grams] city=London
>     PartKey: number=P2
>     PartValue: name=Bolt color=Green weight=[17.0 grams] city=Paris
>     PartKey: number=P3
>     PartValue: name=Screw color=Blue weight=[17.0 grams] city=Rome
>     PartKey: number=P4
>     PartValue: name=Screw color=Red weight=[14.0 grams] city=London
>     PartKey: number=P5
>     PartValue: name=Cam color=Blue weight=[12.0 grams] city=Paris
>     PartKey: number=P6
>     PartValue: name=Cog color=Red weight=[19.0 grams] city=London

>     --- Suppliers ---
>     SupplierKey: number=S1
>     SupplierValue: name=Smith status=20 city=London
>     SupplierKey: number=S2
>     SupplierValue: name=Jones status=10 city=Paris
>     SupplierKey: number=S3
>     SupplierValue: name=Blake status=30 city=Paris
>     SupplierKey: number=S4
>     SupplierValue: name=Clark status=20 city=London
>     SupplierKey: number=S5
>     SupplierValue: name=Adams status=30 city=Athens

>     --- Suppliers for City Paris ---
>     SupplierValue: name=Jones status=10 city=Paris
>     SupplierValue: name=Blake status=30 city=Paris

>     --- Shipments ---
>     ShipmentKey: supplier=S1 part=P1
>     ShipmentValue: quantity=300
>     ShipmentKey: supplier=S2 part=P1
>     ShipmentValue: quantity=300
>     ShipmentKey: supplier=S1 part=P2
>     ShipmentValue: quantity=200
>     ShipmentKey: supplier=S2 part=P2
>     ShipmentValue: quantity=400
>     ShipmentKey: supplier=S3 part=P2
>     ShipmentValue: quantity=200
>     ShipmentKey: supplier=S4 part=P2
>     ShipmentValue: quantity=200
>     ShipmentKey: supplier=S1 part=P3
>     ShipmentValue: quantity=400
>     ShipmentKey: supplier=S1 part=P4
>     ShipmentValue: quantity=200
>     ShipmentKey: supplier=S4 part=P4
>     ShipmentValue: quantity=300
>     ShipmentKey: supplier=S1 part=P5
>     ShipmentValue: quantity=100
>     ShipmentKey: supplier=S4 part=P5
>     ShipmentValue: quantity=400
>     ShipmentKey: supplier=S1 part=P6
>     ShipmentValue: quantity=100

>     --- Shipments for Part P1 ---
>     ShipmentValue: quantity=300
>     ShipmentValue: quantity=300

>     --- Shipments for Supplier S1 ---
>     ShipmentValue: quantity=300
>     ShipmentValue: quantity=200
>     ShipmentValue: quantity=400
>     ShipmentValue: quantity=200
>     ShipmentValue: quantity=100
>     ShipmentValue: quantity=100

Copyright (c) 1996-2003 Sleepycat Software, Inc. - All rights reserved.