diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2018-07-14 21:03:06 +0100 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2018-07-14 21:03:06 +0100 |
commit | 8376ef56580626e9c0f796d5b85b53a0a1c7d5f5 (patch) | |
tree | 7681bbd4e8b05407772df40a4bf04cbbc8afc3fa /dev-db/gigabase/metadata.xml | |
parent | 30a9caf154332f12ca60756e1b75d2f0e3e1822d (diff) |
gentoo resync : 14.07.2018
Diffstat (limited to 'dev-db/gigabase/metadata.xml')
-rw-r--r-- | dev-db/gigabase/metadata.xml | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/dev-db/gigabase/metadata.xml b/dev-db/gigabase/metadata.xml new file mode 100644 index 000000000000..4277b141f815 --- /dev/null +++ b/dev-db/gigabase/metadata.xml @@ -0,0 +1,27 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> + <!-- maintainer-needed --> + <longdescription lang="en"> + 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. + </longdescription> + <upstream> + <remote-id type="sourceforge">gigabase</remote-id> + </upstream> +</pkgmetadata> |