4

Apparently you could do either, but the former is more common.

Why would you choose the latter and how does it work?

I read this: http://www.drdobbs.com/cpp/stls-red-black-trees/184410531; which made me think that they did it. It says:

insert_always is a status variable that tells rb_tree whether multiple instances of the same key value are allowed. This variable is set by the constructor and is used by the STL to distinguish between set and multiset and between map and multimap. set and map can only have one occurrence of a particular key, whereas multiset and multimap can have multiple occurrences.

Although now i think it doesnt necessarily mean that. They might still be using containers.

I'm thinking all the nodes with the same key would have to be in a row, because you either have to store all nodes with the same key on the right side or the left side. So if you store equal nodes to the right and insert 1000 1s and one 2, you'd basically have a linked list, which would ruin the properties of the red black tree.

Is the reason why i can't find much on it that it's just a bad idea?

Matthias
  • 105
  • 1
  • 9
  • I don't think sorted search trees (and hashes) were meant and designed to support duplicate keys. Their primary use case is unique keys. – Alexey Frunze Sep 28 '12 at 08:10
  • I think one reason to store them as individual nodes is because you can reference them more easily. I chose to use collections and now I need two iterators to reference one key/value-pair. (i'm writing a multimap based on the red black tree) – Matthias Sep 29 '12 at 20:09

2 Answers2

2

down side of store as multiple nodes:

  1. expands tree size, which make search slower.

  2. if you want to retrieve all values for key K, you need M*log(N) time, where N is number of total nodes, M is number of values for key K, unless you introduce extra code (which complicates the data structure) to implement linked list for these values. (if storing collection, time complexity only take log(N), and it's simple to implement)

  3. more costly to delete. with multi-node method, you'll need to remove node on every delete, but with collection-storage, you only need to remove node K when the last value of key K is deleted.

Can't think of any good side of multi-node method.

FrostNovaZzz
  • 802
  • 3
  • 10
  • 22
2

Binary Search trees by definition cannot contain duplicates. If you use them to produce a sorted list throwing out the duplicates would produce an incorrect result. I am working on an implementation of Red Black trees in PHP when I ran into the duplicate issue. We are going to use the tree for sorting and searching. I am considering adding an occurrence value to the node data type. When a duplicate is encountered just increment occurrence. When walking the tree to produce output just repeat the value by the number of occurrences. I think I would still have a valid BST and avoid having a whole chain of duplicate values which preserve the optimal search time.

daniel jimison
  • 37
  • 1
  • "... Binary Search trees by definition cannot contain duplicates ... " Can you point me to that definition? I'm struggling to find it here: https://en.wikipedia.org/wiki/Binary_search_tree – dominikz Apr 14 '19 at 16:19