Log message:
Update gigabase to 3.82.
per maintainer update request by PR#45076.

--- Release version 3.80 15.12.2010 -------------------------------------
1. Fix bug with preserving indices
2. Replace sprintf with strcat in ClassDescriptor constructor to avoid problems
   in SymbianOS
3. Fix problem with std_tmp_allocator in xml.cpp

--- Release version 3.81 29.03.2011 -------------------------------------
1. Change return type of select method to be able to selcet more than 2Gb
   records
2. Patch of SubSQL HTML dump done by Christen Volker improving visualisation of
   large arrays
3. Visual Studio 10 compatibilty fixes

--- Release version 3.82 06.05.2011 -------------------------------------
1. Fix bug with scheduled incremental backup
2. Fix namespace support

Log message:
Import gigabase-3.79 as databases/gigabase.
Based on PR#43854 by GEnnady Proskurin,
remove FreeBSD-port-izm, really destdir support, and some fixes.

GigaBASE: Object-Relational Database Management System

GigaBASE inherits most of the features of FastDB, but uses page pool instead
of direct mapping of file on virtual memory. So GigaBASE is able to handle
database, which size significantly exceeds size of computer physical memory.
Convenient and flexible C++ interface makes development of application for
GigaBASE very easy and automatic scheme evaluation simplifies maintenance
and modification of the system. GigaBASE merges best features of relational
(simple data structure and non-procedural query language) and object-oriented
(direct object references, user defined types and methods) databases.
GigaBASE is primary oriented on application requiring fast data retrieving
by means of indices and direct object references, such as Web Server databases
applications.

SUBSQL utility can be used for database browsing and inspection, performing
online backups, database recovery, importing data to and exporting data from
database. GigaBASE will perform automatic recovery after system or application
crash, you should not worry about it. The only thing you can have to do manually
is stopping all database application if one of them is crashed leaving database
blocked.