Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

Add to Readme a link to a StackOverflow answer with details on Chronicle-Map-as-multimap usage issues

Browse Source
This commit is contained in:
leventov
2016-04-07 21:30:35 +01:00
parent b1b4dfb571
commit 6e15ff071d
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -1
View File
@@ -81,7 +81,8 @@ Read [the Chronicle Map data store design overview](spec/2-design-overview.md) f
- A document store. No secondary indexes.
- A [multimap](https://en.wikipedia.org/wiki/Multimap). Using a `ChronicleMap<K, Collection<V>>`
as multimap is technically possible, but often leads to problems. Developing a proper multimap with
as multimap is technically possible, but often leads to problems (see [a StackOverflow answer](
http://stackoverflow.com/a/36486525/648955) for details). Developing a proper multimap with
Chronicle Map's design principles is possible, [contact us](mailto:sales@chronicle.software) is
you consider sponsoring such development.