Skip to main content

Java - Data Structure (Binary Trees)

Binary Trees are one of the fundamental data storage structures used in programming. They provide advantages that the data structures we've seen so far cannot.

Why use binary tree?Usually, because it combines the advantages of two other structures: an ordered and array and a linked list. You can search a tree quickly, as you can with an ordered array, and you can also insert and deleted items quickly,as you can with a linked list.

The disadvantage of an ordered array: slow insertion and deletion.
Disadvantage of a linked list: slow searching.

What is a Tree: A tree consists of nodes connected by edges.
                   O -- Node
                 /    \  --- Edges
               /        \
             O         O
            /  \

In computers programs, nodes often represent such entities as people, car parts, airline reservations, and so on.
Edges are likely to be represented in a program by references, if the program is written in Java( or by pointers if the program is written in C or C++)
class Node{
int iData;
node leftChild;
node rightChild;
}
class Tree{
private Node root;
Node find(key)
}
public Node find(int key){
Node current = root;
while(current.iData != key){
  if(key > current.iData) current = current.leftChild;
  else current = current.rightChild;
if(current == null) return null ; // didn't find it
} // end where
return current;
}

//Successor is left descendant of Right Child of delNode
node getSuccessor(node delNode){
Node successorParent = delNode;
node successor = delNode;
Node current = delNode.rightChild; // go to right child until no more left children
while(current != null){
successorParenet = successor;
successor = current;
current = current.leftChild ; //go to left child if successor not  right child,
}
if(successor != delNode.rightChild) {
successorParent.leftchild = successor.rightChild;
successor.rightChild = delNode.rightChild;
}
 return successor;
}

Comments

Popular posts from this blog

Quicksort implementation by using Java

 source: http://www.algolist.net/Algorithms/Sorting/Quicksort. The divide-and-conquer strategy is used in quicksort. Below the recursion step is described: 1st: Choose a pivot value. We take the value of the middle element as pivot value, but it can be any value(e.g. some people would like to pick the first element and do the exchange in the end) 2nd: Partition. Rearrange elements in such a way, that all elements which are lesser than the pivot go to the left part of the array and all elements greater than the pivot, go to the right part of the array. Values equal to the pivot can stay in any part of the array. Apply quicksort algorithm recursively to the left and the right parts - the previous pivot element excluded! Partition algorithm in detail: There are two indices i and j and at the very beginning of the partition algorithm i points to the first element in the array and j points to the last one. Then algorithm moves i forward, until an element with value greater or equal

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory        About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object        

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/>