Free dbms software for linux

ZDB (Zazzybob.com DataBase) can be used to maintain simple lists and databases (such as telephone directories, address lists, etc). The project implements mechanisms for basic queries and reporting, and also allows us to join two tables by a primary key, and display query results based thereon.

ZDB is not a relational database. If you want a relational DB then use a proper DBMS!

ZDB is, however, highly useful for small, non-critical database needs, especially where "flat-files" are all thats really required, but where maintaining a long list of data manually would be too labour intensive.

ZDB requires the "usual-suspects" with regards to tool dependencies. All of the required tools will be present in any modern UNIX/Linux system. The scripts are implemented as bash scripts, but if you change the shebang line to match the path to your shell, and as long as your shell supports the ((...)) arithmetic construct, youll be okay! There arent any bash-specifics in the scripts.

Some of the scripts (especially query scripts) may run fairly slowly depending on your system. There is a lot of data processing going on in the background (involving many invocations of awk!). On a P4 2.66GHz the results will be instantaneous, whereas on a PII 233MHz you might not be so lucky.

Package Contents

The ZDB package consists of the following scripts:
zdb_constants

Contains constants needed by all scripts

zdb_create_table
Creates a new table
zdb_insert_values
Insert values into a table
zdb_join_tables
Query two tables using a join
zdb_remove_table
Drop a table
zdb_remove_values
Remove values from a table
zdb_select_all
Display an entire table
zdb_select_rows
Query a table by row
zdb_select_values
Query a table by column name
zdb_get_by_key
Get a single row by its key value

Also included in the download is zdb_test which is an example showing how each of the commands is used, creating tables, inserting values, querying the tables, and finally deleting the tables.

As you can see, I havent implemented a "change row" script. I dont see the point, as it would just duplicate the functionality of a call to zdb_remove_values followed by a call to zdb_insert_values. I have shown an example of this in the zdb_test script, included with the download.

Overview of Data Structure

Each table is made of two parts. A .def (Definition) file, and a .dat (Data) file. The .def file is created when the table is first created, and contains a list of all the column names in that table, and thus, provides that tables definition. The .dat file is created when the first row of values is inserted (and is deleted when the last row of data is removed). This is a flat file using ":" as a column delimeter. Therefore, do NOT use ":" in any of your data!

The idea of the .def file is to provide column name to field position translation, so that we can query in the form column_name=value (kind of like a WHERE clause in SQL). They are saved as table_name.{dat,def} in the directory specified by the ZDB_DIR constant (see below).

The first (left-most) column in each table is considered to be its key and must be unique for each row in the table.

Syntax

The syntax of each command is discussed below.

zdb_constants

Syntax

N/A

In the current implementation, this script contains only one constant, ZDB_DIR, which is the full path to the directory containing your database (.dat/.def) files. It is important that the directory exists, and that this constant is set correctly to reference the directories path, otherwise nothing will work!

Example

ZDB_DIR=/home/kevin/databases/db_one
zdb_create_table
Syntax
zdb_create_table table_name col_1 [ col_2 ... col_n ]

Create a table within ZDB_DIR named table_name as specified by the first argument to the command. The column names are specified by subsequent arguments to the command. At least one column must be specified. This command creates a file in ZDB_DIR named table_name.def.

Example

zdb_create_table my_table id f_name s_name t_name
zdb_insert_values
Syntax
zdb_insert_values table_name val_1 [ val_2 ... val_n ]

Insert values specified by val_1, etc, into table_name. This has various error checking mechanisms implemented, and will check for the correct number of values (i.e. the same number of values as there are columns in the table). val_1 in the left-most column is considered to be a primary key for that row of data, and must be unique within that table. Values are added sequentially, and are thus "appended" to the table in the order that they are added. No sorting takes place. If any single value contains spaces, it must be quoted, e.g. "example value with spaces".

Example

zdb_insert_values my_table 1 Kevin Waldron 0208-111-1111
zdb_join_tables
Syntax
zdb_join_tables table_one table_two [ searchterm | col=searchterm ]

Join two tables by their key field, and print fields from both tables where the row key matches. Other rows are not printed. An optional searchterm can be specified. This searchterm MUST be a single word, and can be of the form "searchterm" where all fields are searched, or "col=searchterm" whereby only the specified column name "col" is searched.

Example

Suppose we have two tables populated with data, the following session depicts command usage and possible output
$ zdb_join_tables my_info my_table name=Kevin

id name number data_1 data_2
1 Kevin Smith 02081111234 zdb_data more_data
2 Kevin Jones 02078392111 data_value more_data
68 Mr Kevin 9230192912 0291 19192

zdb_remove_table
Syntax
zdb_remove_table table_name

If table_name exists, both its .def and .dat files will be deleted.

Example

zdb_remove_table my_table
zdb_remove_values
Syntax
zdb_remove_values table_name key

Removes the row from table_name specified by key, where key is the unique identifier for that row (the entry in the first column of the table for that row).

Example

To remove the row with key "4" from my_table

zdb_remove_values my_table 4
zdb_select_all
Syntax
zdb_select_all table_name

Displays all data from table_name preceeded by a header row detailing the column names

Example

zdb_select_all my_table
zdb_select_rows
Syntax
zdb_select_rows table_name searchterm|col=searchterm

Shows all rows from table_name where searchterm can be found. Accepts both forms of searchterm specification, as discussed in the zdb_join_tables section above.

Example

zdb_select_rows my_table Kevin
zdb_select_values
Syntax
zdb_select_values table_name col_1 [ col_2 ... col_n ]

Selects and displays all data from the specified columns in table_name
Example
Yes, multiple instances of the same column can be specified, to repeat their output

zdb_select_values my_table f_name f_name s_name
zdb_get_by_key
Syntax
zdb_get_by_key table_name key

Select only the single row from table_name that has the unique key key.

Example

zdb_get_by_key my_table 1

cmsdAm provides a link extractor/collector based on Qt.
CmsdAm is a simple and secure Content Management System Framework with a core API specially designed for people with some knowledge of PHP4 that want to create dynamic sites quickly.
Main features:
- include plugins
- handle user defined (sub)sections
- developed with system administrators in mind (Im a Linux system administrator!)
- sections navigation bar
- media serialization, good for ex. to hide/deny media usage for someone
- handle users and groups
- section view, search, manage users and group permissions
- search engine for user defined sections
- simple set of PHP api (class methods) for users, sections, search engine, etc...
- with php knowlege cmsdAm let you bring up sites in a while
- implements simple HTTP cache mechanisms (or not ;-)), meta tags handling, error templates, content encoding, i18n!)
- handle users and groups ACL to access sections
- handle emails
- automatic internal cache mechanisms memcached daemon ready
- full scalable LDAP support
- supports MySQL, (PostgreSql support will come soon), ldap, (other dbms support will come soon)
- developed with security, scalability and velocity in mind!
- more and more
Enhancements:
- Overall tests done
- PHPWarn_on_sectioninclude parameter now also handle section inclusion comments
- Full email attachments support in the mail class just written
- FAQ written
- file_container class written to add any content(files, strings, text, variables) to the server
- filesystem from your sections
- $LDAP_exclusive parameter changed from 1 to 2
- Code cleanup
- Simple error/function handler written, ex to avoid problems with PHP without ldap support
- cmsdmam_errors class added to handle simple error handling
- Many PHP bad style notices fixed
- We are now able to handle PHP Error Reporting (cmsdam core and sections) by configuration file
- Minor bug fixes in index_header.php

MySQA program is a useful program to analyze log files created by MySQL slow queries or queries that dont use indexes.

About MySQL:

MySQL is a multithreaded, multi-user, SQL (Structured Query Language) Database Management System (DBMS) with an estimated six million installations. MySQL AB makes MySQL available as free software under the GNU General Public License (GPL), but they also dual-license it under traditional proprietary licensing arrangements for cases where the intended use is incompatible with the GPL.

Unlike projects such as Apache, where the software is developed by a public community, and the copyright to the codebase is owned by its individual authors, MySQL is owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, which holds the copyright to most of the codebase.

The company develops and maintains the system, selling support and service contracts, as well as proprietary-licensed copies of MySQL, and employing people all over the world who collaborate via the Internet. Two Swedes and a Finn founded MySQL AB: David Axmark, Allan Larsson, and Michael "Monty" Widenius.

DBIx::Recordset is a Perl extension for DBI recordsets.

SYNOPSIS

use DBIx::Recordset;

# Setup a new object and select some recods...
*set = DBIx::Recordset -> Search ({!DataSource => dbi:Oracle:....,
!Table => users,
$where => name = ? and age > ?,
$values => [richter, 25] }) ;

# Get the values of field foo ...
print "First Records value of foo is $set[0]{foo}n" ;
print "Second Records value of foo is $set[1]{foo}n" ;
# Get the value of the field age of the current record ...
print "Age is $set{age}n" ;

# Do another select with the already created object...
$set -> Search ({name => bar}) ;

# Show the result...
print "All users with name bar:n" ;
while ($rec = $set -> Next)
{
print $rec -> {age} ;
}

# Setup another object and insert a new record
*set2 = DBIx::Recordset -> Insert ({!DataSource => dbi:Oracle:....,
!Table => users,
name => foo,
age => 25 }) ;


# Update this record (change age from 25 to 99)...
$set -> Update ({age => 99}, {name => foo}) ;

DBIx::Recordset is a perl module for abstraction and simplification of database access.

The goal is to make standard database access (select/insert/update/delete) easier to handle and independend of the underlying DBMS. Special attention is made on web applications to make it possible to handle the state-less access and to process the posted data of formfields, but DBIx::Recordset is not limited to web applications.

DBIx::Recordset uses the DBI API to access the database, so it should work with every database for which a DBD driver is available (see also DBIx::Compat).
Most public functions take a hash reference as parameter, which makes it simple to supply various different arguments to the same function. The parameter hash can also be taken from a hash containing posted formfields like those available with CGI.pm, mod_perl, HTML::Embperl and others.
Before using a recordset it is necessary to setup an object. Of course the setup step can be made with the same function call as the first database access, but it can also be handled separately.

Most functions which set up an object return a typglob. A typglob in Perl is an object which holds pointers to all datatypes with the same name. Therefore a typglob must always have a name and cant be declared with my. You can only use it as global variable or declare it with local. The trick for using a typglob is that setup functions can return a reference to an object, an array and a hash at the same time.

The object is used to access the objects methods, the array is used to access the records currently selected in the recordset and the hash is used to access the current record.

If you dont like the idea of using typglobs you can also set up the object, array and hash separately, or just set the ones you need.

gen_names populates customer/invoice tables with random (but realistic looking) data. Thedata has been gathered from various sources including census and local council Web sites.
The project is supposed to be used to road test various DBMS solutions.
Enhancements:
- This release fixes Oracle support, which was previously broken.

Valentina is cross-platform DBMS that makes it easy to switch between a local embedded database and server using the same sources. It supports disk and in-memory databases, field types from Bit to BLOB, and both a SQL92(99) and non-SQL API.
Valentina supports Relational, Extended Navigational, and Object-Relational data models. It introduces a revolutionary model abstraction "Link". It works natively in UTF-16, can accept 270 encodings, and features advanced features such as regular expressions, XML, full-text search, pictures, functions, and calculated fields. It offers triggers, views, and stored procedures.
Enhancements:
- Valentina Studio now has a Diagrams panel for database schema.
- There are new examples on the usage of Link refactorings API and SQL commands.
- There are about 40 bugfixes over the entire product line (kernel, PHP, REALbasic, Director, VCOM, and VStudio).

MonetDB is an open source high-performance database system developed at CWI, the Institute for Mathematics and Computer Science Research of The Netherlands.
MonetDB project was designed to provide high performance on complex queries against large databases, e.g. combining tables with hundreds of columns and multi-million rows.
As such, MonetDB can be used in application areas that because of performance issues are no-go areas for using traditional database technology in a real-time manner.
MonetDB has been successfully applied in high-performance applications for data mining, OLAP, GIS, XML Query, text and multimedia retrieval.
MonetDB achieves this goal using innovations at all layers of a DBMS: a storage model based on vertical fragmentation, a modern CPU-tuned vectorized query execution architecture that often gives MonetDB a more than 10-fold raw speed advantage on the same algorithm over a typical interpreter-based RDBMS.
MonetDB is one of the first database systems to focus its query optimization effort on exploiting CPU caches. MonetDB also features automatic and self-tuning indexes, run-time query optimization, a modular software architecture, etcetera.
In-depth information on the technical innovations in the design and implementation of MonetDB can be found in our digital library.
Main features:
- A fairly extensive ANSI SQL-99 language interface including:
- Primary and foreign key enforcement
- View management
- Sub-queries
- Authorization scheme
- Unicode support (UTF-8)
- Support for external functions
- A full-fledged and scalable implementation of XQuery.
- SQL and XQuery query caching to speed up data processing.
- Extensible architecture at any level of sophistication needed.
- The MonetDB engine can be embedded into your application.
- High performance, using highly tuned data structures and algorithms to exploit the power of modern hardware.
- Transaction control at various levels of granularity, which makes query dominant applications run at light speed.
- Tapping into the experiences gained in supporting XML, Multimedia, GIS, etc. applications right op top of a kernel without the overhead often encountered in SQL-based systems.
- Broad hardware spectrum ranging from StrongARM-based PDAs up to Opteron-based Servers (cf. Platforms).
- 32- and 64-bit cross-platform support for:
- Linux, Microsoft Windows, Apple MacOS X, Sun Solaris, IBM AIX, and SGI IRIX;