Free storing software for linux

ObjStore is a Perl extension for ObjectStore OODBMS.

SYNOPSIS

Like perl? Sick of SQL? Ready to try something new? This extension implements something like a relational database management system, except that s/SQL/Perl/ig.

ObjectStore is the market leader in object-oriented databases http://www.odi.com (NASDAQ: ODIS). They use a unique Cache-Forward Architecture to make persistent data available in literally the most efficient manner possible.

Prior to this joining of forces

ObjectStore was too radical a design decision for many applications
Perl5 did not have a simple way of storing complex data persistently

Now there is an easy way to build database applications (especially if you are concerned about preserving your ideals of encapsulation).

Email::Store::DBI is a Perl module for database backend to Email::Store.

SYNOPSIS

use Email::Store dbi:...;

This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.

"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.

Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.

mod_repository turns Apache into a content storage system with the benefit of storing just one copy of each file submitted to the repository. Upon storing a file a user is given a unique token representing the file.

This can be used to create content servers which are abstracted from the filesystem. Files can be placed, retrieved, and deleted from the server.

PowerMail provides a redundant and distributed system for receiving and storing mail.
PowerMail is a redundant and distributed system for receiving mail via SMTP and storing it for users to access with POP. The way PowerMail works is quite unorthodox, and its design emphasizes speed and efficiency.
Modified Maildir mailboxes allow PowerMail to employ hardlinks to save diskspace and deliver messages with thousands of recipients instantly.
PowerMail can operate self-sufficiently or cooperate with a regular MTA to support mail forwarding.
Enhancements:
- fixes for older gcc compilers (Ruben dArco)
- pptool ignored SYSCONFDIR and only did /etc/powermail (Ruben dArco)
- added ldap-forwarding-attribute
- --help display was somewhat screwed (Ruben dArco)
- run-as-uid/run-as-gid broken (Ruben dArco)
- TOP cleaned up (Ruben dArco)

Paymaster is an open source free payroll and HR application designed for small to large organisations. Paymaster project works in batch process system for paying employees, using journal entries and a series of ledgers for storing the accounts.

A customisable backed calculates the results to help meet the diverse requirements of payroll. Complex tax laws, leave, varying pay rates, allowances, superannuation are some of the things the payroll system can handle. Paymaster is written for gnome and uses postgresql for its database backend.

Sudoku solver application was created for solving a Sudoku with a backtracking algorithm. Instead of using a 9 x 9 matrix, it extends the matrix to 10 x 36 (10 rows, 36 columns), storing information in the extra cells.

The last row is used for keeping track of how many cells, for the current column, are still available.

The columns 9-17 (0-based) are used for storing the numbers which are still available in rows 0-8.

The columns 18-26 are used for storing the numbers which are still available in columns 0-8.

The columns 27-35 are used for storing the numbers which are still available in each square (counting from left to right and from top to bottom).

Wiki::Toolkit::Store::Mediawiki is a Mediawiki (MySQL) storage backend for Wiki::Toolkit.

SYNOPSIS

Implementation of Wiki::Toolkit::Store::Database which reads and writes to a Mediawiki 1.6 database running in MySQL. This is module is intended to be capable of running concurrently with a Mediawiki 1.6 installation without data corruption. That said, use it at your own risk.

If you are looking for a general Wiki implementation, you might be better off looking at Wiki::Toolkit::Kwiki. It is simpler, more general, and does not require the database to be initialized by outside software. Currently, initializing the database for this module requires a working (PHP) Mediawiki installation.

I initially wrote this module because I was sick of running both PHP and Perl on my web server so that I could have the only wiki I could find with the full featureset I wanted running in parallel with the Perl scripts which generate the rest of my content dynamically. Generating my Perl content was much faster than my Mediawiki installation and I like Perl better, so PHP lost. Converting the old Mediawiki database into a format that a less fully featured wiki could read looked generally unrewarding, so here we are.

All date and time values are returned as Time::Piece::Adaptive objects. This should be transparent for most uses.

See Wiki::Toolkit::Store::Database for more on the general API.