Only matching pref. in resp. from edit_prefix call

Made sure that the return value from the edit_prefix function only
includes matching prefixes, eg. the prefixes which were actually
modified.
Bumped version to 0.22.3
Backed accidental changes to control-file

Rollback changes I accidentally introduced in the
nipap/debian/control-file.
Add more examples to NIPAP CLI man page

Fixes #426.
Merge branch '426-man-examples'
Bumped version to 0.22.4
Move trigger definitions into functions

Since we rewrite trigger functions every now and then it makes more
sense to have them in the functions.plsql file, as that is run on every
upgrade, rather than in ip_net.plsql which is only run when going
between database schema versions.

This will allow us to easily implement new triggers or remove current
ones in the future.
Merge branch 'db-stuff'
Modified pynipap to not store XML-RPC connections

To avoid the issue with XML-RPC-connections never being closed, XML-RPC
connections are no longer stored in each instance of the NIPAP objects.
The impact of this will probably be small as only the save() and
remove()-calls actually used the stored connections.

Fixes #384
Merge branch 'master' of github.com:SpriteLink/NIPAP
Create tables before functions and triggers

Should fix the bug I introduced in my previous commit.
query_id handled by all response handlers

Made sure that all the receivePrefixList-handlers verifies that the
query_id is not lower than the latest received query's. Also refactored
the code a bit to reduce code duplication.

Fixes #391
Merge branch 'db-stuff'
Add note on recursive delete to nipap CLI man page

Fixes #408.
Removed int()-casts in XHR controller

Removed some int()-casts in the XHR controller as the backend handles
both (and we avoid double validations). Also added a few missing
int()-casts with validation in the backend.

Fixed #423
Merge branch 'xhr_pass_through'
Modified install instructions
added customer_id
Implement precalculation of number of children

This implements the calculation and storing of the number of children to
a prefix. Previously we did this calculation kind of on-the-fly when
returning search results but as it is a value that doesn't change much
it is well suited to being calculated beforehand and stored in the
database.

Together with this, a lot of database triggers have been refactored.
Most of the changes pertain to how and when triggers are called and not
their actual function. Instead of triggering children/tag/indent
calculation on all updates we are now using the column based triggers
available in PostgreSQL 9.x to only trigger on changes that would
influence the result. For example, changing the description of a prefix
would not change the indent and so there is no need to trigger indent
calculation on changes to the description column. There is a certain
risk of new bugs as the changes are quite extensive but the unittests
run without fault and I've gone through everything more than once ;)

Naturally, the web UI now uses the values it receives from the backend
on how many children a prefix has. There was quite a lot of logic to
handle guessing the amount of children which has now been removed.

Also clarify certain parts of country code integrity test and fix other
unittests.

Fixes #421.
Fix rendering of inherited tags

When a prefix has a tag, a small icon is rendered next to the prefix and
onMouseOver a tooltip dialog will list the tags and inherited tags.
First, the icon and tooltip was not available if the prefix only had
inherited tags (ie, no tags). Secondly, when the tooltip was displayed,
the list contained the array index and not the name of the inherited
tag. Both issues have been resolved.

Fixes #430.