Free database management software for linux

Essential Management provides a project management system for organizing and writing technical documents.

Essential Management is a multi-user project management system for managing intricate and complex information. Its initial purpose was to allow software development teams to create, maintain, track, and store project requirements on a multi-project basis in a multi-user environment. It has now become more abstract in the type of data it can maintain, allowing the easy addition of new data models and other expansions. Information can be stored in any of several database management systems, and can take advantage of a networked DBMS.

The first and most important feature of the application is that data is stored in a central data repository managed by some database management server; initially PostgreSQL fills this role, but support for others are growing. The repository is fully searchable. An alternative data storage format exists in the form of a locally maintained XML file if the user wishes to use it.

One of the key features Essential Management was designed around is the ability to define and maintain relationships between requirements. Using the software requirement model as an example, our application allows users to define projects; each project is composed of zero or more root requirements, which are typically business level requirements. Each business requirement has zero or more sub-requirements, which either refine the parent business requirement or dive into the functional requirements which allow the business requirement to be achieved. This tree continues to branch and grow deeper until the most basic level that the user wishes to define is reached.

In addition the relationship between parent and child requirements, relationships can be defined between requirements not in the same branch. These relationships may have any meaning the user wishes to define and can be unidirectional or bi-directional.

Essential Management implements the concept of user level permissions, which provides a small measure of security for the projects and their requirements. Additionally, creation of and changes to requirements can be traced to the user who initiated the action.

Finally, the application provides a means to track changes made to requirements during their lifetime so it is possible to determine when a change was made, what information was changed and who edited the requirement.

Remote Gnu Database Manager is a network server daemon and client library for the standard GNU GDBM(3) database management interface, which itself incorporates Berkeley DBM.
To setup after installation (these notes are for 2.1.33 or later), let make install do what it can, and then:
1. create a user, gdbm, on the server machine with home in /var/lib/gdbm. Make install tries to do that for you using adduser so you likely just have to check /etc/passwd and /etc/group.
2. Create /var/lib/gdbm and change owner to gdbm. Again, make install has a stab at this for you and likely you will need to do nothing yourself.
3. Also create /var/lib/gdbm/data, /var/lib/gdbm/ctrl and change owner to gdbm. Make install should also have made those.
4. Copy those parts of /etc/passwd belonging to users who should be able to access the daemon to /var/lib/gdbm/ctrl/passwd. This is entirely in your hands.
5. Likewise for /etc/group to /var/lib/gdbm/ctrl/group.
6. Start the daemon as gdbm with some command like "sudo -u gdbm /usr/sbin/gdbmd", or "su -c /usr/sbin/gdbmd gdbm". The install will not start it for you, nor does it presently install a system startup script for it in /etc/init.d or elsewhere.
7. Write an application on the client that uses the standard gdbm_* calls in the GNU GDBM(3) manpage, but replace the gdbm_ calls with rgdbm_ calls. The install routine does do that ... or perhaps I lie.
Thats about it! Apart from setting up for SSL if you want to use that and Ill give some further indications as to how to do that below.
One has to add two extra calls in the application over and above what was there already for gdbm(3) usage; one to rgdbm_connect() and another to rgdbm_disconnect(), respectively to begin and end the session, as detailed in the rgdbm(3) man page.
Example:
Sample code ... start by making the connection:
rgdbm_connect(host, dir, user, 0);
Then open the desired database in that directory:
GDBM_FILE dbf = rgdbm_open(dbname, 1024, GDBM_WRCREAT, 0640, NULL);
Now the rgdbm(3) ops are available.
fprintf(stdout, "Database contains ...n");
datum key = rgdbm_firstkey(dbf);
if (key.dptr) {
datum content = rgdbm_fetch(dbf, key);
fprintf(stdout, "key %s content %sn", key.dptr, content.dptr);
while (key = rgdbm_nextkey(dbf, key), key.dptr) {
fprintf(stdout, "key %s content %sn", key.dptr, content.dptr);
}
}
Terminate by closing:
rgdbm_close(dbf);
and disconnect from the session:
rgdbm_disconnect();
Enhancements:
- Added (generated) debian directory to package.

Resource Management Game project is a Web-based resource management game.

Resource Management Game is a PHP framework for easily creating resource management and strategy games.

Two playable games are included.

The system uses sessions to store data and should work out of the box with little or no configuration.

Database Functions is a PHP class that can be used to build and execute MySQL database queries.

It can build SELECT, INSERT, UPDATE and DELETE queries from lists of parameters and values.

The class can also execute the generated queries and retrieve the SELECT query results into associative arrays.

LMS (LAN Management System) is the integrated system of networks management designed for various size internet providers (ISP).

That software writed in PHP, Perl and C, works with variuos database systems.

Community Content Management project consists of a light-weight CMS, designed for communities.
Community Content Management is a light-weight CMS, which is designed for small communities, such as churches, schools, and neighborhood watch groups.
It allows someone with relatively little knowledge of the Internet to publish news stories and events. It sets archive/publishing dates, allowing groups to write press releases/articles about events before they happen.
Its output conforms to XHTML 1.0 and uses CSS 2, and its configuration comprises one file, which sets the site title, database, host, and meta tags.
Enhancements:
- Login - code changed so correct variables are passed to login script :)
- Search - Search Engine Added
- Articles - new lines (n) are replaced with "
" instead of " "

PHP Sessions Management Class is a php class to handle sessions by using a mySQL database for session related data storage providing better security then the default session handler used by PHP.
If you are not familiar with what php sessions are and what are they good for, check out the dedicated chapter in the php manual
If you are familiar with php sessions and you want to use this php class in your projects then remember that to prevent session hijacking, you must not forget to use the regenerate_id() method whenever you do a privilege change in your application
Before usage, make sure you use the session_data.sql file (which is a sql dump file generated with phpMyAdmin) from the install_sql folder to set up the table used by the class
You dont need to modify anything in your previous applications: after instantiating the php class, just use sessions as you would normally.
Note:
The class assumes that there is an active connection to a mySQL database and it does not attempt to create one. This is due to the fact that, usually, there is a config file that holds the database connection related information and another class, or function that handles database connection. If this is not how you do it, you can easily adapt the code by putting the database connection related code in the "open" method of the class.
Enhancements:
- The get_users_online() method is now more accurate as it now runs the garbage collector before getting the number of online users.
- The structure of the MySQL table used by the class was tweaked in so that the "http_user_agent" field was changed from VARCHAR(255) to TEXT to accomodate user agent strings that are longer than 255 characters.
- The "session_data" field was also changed from TEXT to BLOB to help users who store a large amount of data in sessions.