A fast erasure codec which can be used with the command-line, C,
Python, or Haskell.
Fast, portable, programmable erasure coding a.k.a. "forward error
correction": the generation of redundant blocks of information such
that if some blocks are lost then the original data can be recovered
from the remaining blocks. The zfec package includes command-line
tools, C API, Python API, and Haskell API.
This is a character encoding converter generator package.
Currently there are 72 different character encoding description files
supplied with this package, not counting the 13 *.net files, which are
modified character encoding description files. All but 13 of the above
mentioned files describe 8-bit character encodings/sets.
It covers ISO 646, many IBM codepages for MS-DOS, Microsoft Windows
codepages, ISO 8859-x, HP, Adobe, Apple Macintosh, Atari, NeXTSTEP
character encodings, a few EBCDIC encodings, KOI8-R, and a few more.
Command line interface to devel/librcc library. It is a highly
configurable tool (supports almost all library functionality) which
allows to recode standard input on the per-line basis. Additionally,
there is a special mode providing a way to bring the names of all
files in the specified directory to appropriate form (to the specified
encoding, transliterate all names to english, translate all names
to english, etc.)
A DBH is a convenient way to associate keys composed by characters to data
records. Any kind of digital information can go into the data record, such
as text, graphic information, database structures, you name it. The idea
behind using a DBH is to get rid of what is known as an index file in the
database world. In the DBH world, the index is built into the file format.
A little tool that will display dBase III files. You can also use
it to convert your old .dbf files for further use with Unix. It should
also work with dBase IV files, but this is mostly untested.
dbview displays the contents of a dBase III or IV database file. This is
done by displaying both the name of the field itself and its value. At
the end of every record a newline is appended.
Gadfly is a relational database management system which uses a
large subset of very standard SQL as its query language and Python
modules and optional Python/C extension modules as its underlying
engine. Gadfly stores the active database in memory, with recovery
logging to a file system. It supports an optional TCP/IP based
client server mode and log based failure recovery for system or
software failures (but not for disk failures).
libnvpair is a name-value pair library originating from Solaris
The nvpair library was released in OpenSolaris and has been extended
by the Illumos project. It exports a set of functions used for managing
name-value pairs. This is a base library for Solaris and its descendents.
However, the kernel-specific code has been removed thus libnvpair is
strictly meant for the userland. The XDR functionality has been masked
for now due to RPC differences between *BSD and Illumos.
What is MDB Tools?
MDB Tools is a planned set of libraries and utilities to facilitate exporting
data from MS Access databases (mdb files) into a multiuser database such as
Oracle, Sybase, DB2, Informix, MySQL, Postgresql, or similar. A nice little
Gtk MDB file browser will probably be written as well.
Ok, how much is done?
You can list catalog entries. There is some preliminary schema exporting
utility. And you can export data out to CSV (comma separated value) format.
Firebird is a relational database offering many ANSI SQL-99 features
that runs on Linux, Windows, and a variety of Unix platforms. Firebird
offers excellent concurrency, high performance, and powerful language
support for stored procedures and triggers. It has been used in
production systems, under a variety of names since 1981.
Firebird is completely free of any registration, licensing or deployment
fees. It may be deployed freely for use with any third-party software,
whether commercial or not.
This module acts as a mix-in, adding the relationship method to
Class::DBI::Loader. Since Class::DBI::Loader knows how to map between
table names and class names, there ought to be no need to replicate
the names. In addition, it is common (but not universal) to want
reverse relationships defined for has-many relationships, and for
has-a relationships to be defined for the linkages surrounding a
many-to-many table.