You might be wondering what a native XML database is good for? Well it pretty much has one purpose, storing XML data. If you don’t have any XML data, don’t want any XML data or think XML is the most over-hyped technology of the new millennium, then Xindice is not for you. We’re not out to change the way data in general is stored, only to provide a good solution for storing XML data. If you survey your projects and see XML popping out of every corner, then Xindice might be a real help for storing that XML.

The benefit of a native solution is that you don’t have to worry about mapping your XML to some other data structure. You just insert the data as XML and retrieve it as XML. You also gain a lot of flexibility through the semi-structured nature of XML and the schema independent model used by Xindice. This is especially valuable when you have very complex XML structures that would be difficult or impossible to map to a more structured database.

At the present time Xindice uses XPath for its query language and XML:DB XUpdate for its update language. We provide an implementation of the XML:DB API for Java development and it is possible to access Xindice from other languages using built in XML-RPC API. As standards in the XML database area mature Xindice will include support for those that are most important.

Xindice is the continuation of the project that used to be called the dbXML Core. The dbXML source code was donated to the Apache Software Foundation in December of 2001.

Native XML database technology is a very new area and Xindice is very much a project still in development. The server currently supports storing well formed XML documents. This means it does not have any schema that constrains what can be placed into a document collection. This makes Xindice a semi-structured database and provides tremendous flexiblity in how you store your data, but, also means you give up some common database functionality such as data types. In its current state Xindice is already a powerful tool for managing XML data. However, there is still much that needs to be done. Feedback and contributions are actively encouraged.

This document attempts to describe those features that are working and can be used today. You should review the README file that is part of the Xindice distribution for the most current status on the project.

Here are some key features of “Apache Xindice”:

· Document Collections: Documents are stored in collections that can be queried as a whole. You can create collections that contain just documents of the same type or you can create a collection to store all your documents together. The database doesn’t care.

· XPath Query Engine: To query the Document Collections you use XPath as defined by the W3C. This provides a reasonably flexible mechanism for querying documents by navigating and restricting the result tree that is returned.

· XML Indexing: In order to improve the performance of queries over large numbers of documents you can define indexes on element and attribute values. This can dramatically speed up query response time.

· XML:DB XUpdate Implementation: When you store XML in the database you may want to be able to change that data without retrieving the entire document. XUpdate is the mechanism to use when you want to do server side updates of the data. It is an XML based language for specifying XML modifications and allows those modifications to be applied to entire document collections as well as single documents.

· Java XML:DB API Implementation: For Java programmers Xindice provides an implementation of the XML:DB API. This API is intended to bring portability to XML database applications just as JDBC has done for relational databases. Most applications developed for Xindice will use the XML:DB API.

· Command Line Management Tools: To aid the administrator Xindice provides a full suite of command line driven management tools. Just about everything you can do through the XML:DB API can also be done from the command line.

· Modular Architecture: The Xindice server is constructed in a very modular manner. This makes it easy to add and remove components to tailor the server to a particular environment or to embed it into another application.

· Database Structure

· The Xindice server is designed to store collections of XML documents. Collections can be arranged in a hierarchy similar to that of a typical UNIX or Windows file system.

· In Xindice the data store is rooted in a database instance that can also be used as a document collection. This database instance can then contain any number of child collections. In a default install of Xindice the database instance is called ‘db’ and all collection paths will begin with /db. It is possible to rename the database instance if desired though it is not necessary to do so.

Sources mirror 1 (tar.gz)

Sources mirror 2 (tar.gz)

Sources mirror 3 (tar.gz)

By replacing hardcoded passwords in scripts with a call to OPR, it helps to keep your Oracle environment secure and easier to maintain.

What’s New in This Release:

· The INSTALL file informed that you need to be able to see the oracle oci libraries, but it fact you need these only at runtime. You do need access to the OCI headers files during runtime though. But these rights are enabled by default oracle installations.
· opr now uses libltdl, a dynamic loading abstraction, to tackle compiling issues on (for example) hp-ux.
· added file locking on the repository file.
· fixed 2 strncat invocation bugs.

Sources mirror 1 (tar.gz)

Sources mirror 2 (tar.gz)

Sources mirror 3 (tar.gz)

The project of picoSQL was born in 1995. It was an ODBC driver for COBOL indexed files. It consisted of a DLL written in C++ on Windows 3.1 operating system. In the beginning the main effort was made in order to obtain a good compatibity with existing front-end (mainly the MS-Access, MS-Query and VisualBasic) and in order to see COBOL files as a normalized relational DB.

The obtained success concurs to develop ulteriorly the product, refining the query optimizer and implementing an extended SQL, to exclusion of the DDL (Data Description Language). A later version, called PicoDB, were devoloped on UNIX system in client/server architecture.

PicoSql is released under GPL license; it derives from PicoDB (that remains a Picosoft proprietary product) with the addition of some SQL-DDL statement (CREATE/DROP TABLE(INDEX) and excluding COBOL files compatibility). The C/C++ library that allow the database access from C/C++ programs using the ODBC 2.5 API is released under LGPL license; this allows to link the library with programs that are not under GPL.

PicoSQL can be used from Windows applications (like MS-ACCESS, MS-Query, VB etc.) in client/server modality using the ODBC driver picoSQLNet. It can moreover be used from appropriate Java programs through the JDBC driver comprised in the distribution. Finally it can be used from programs written in C and C++ through its set of ODBC 2.5 compliant API.

PicoSQL lacks at the moment of some common characteristics to the most common RDBMS (like the schema and catalogue concepts and the management of the user permissions who can be obtained anyway using the permissions of the host operating system) but they are just these lacks to make it particularly simple to install and to use and fast in the logons and the queries.

Installation:

The installation is particularly simple: if you have the binary distribution, is sufficient to extract the compressed files in one directory ( under Windows NT/2000/XP) and execute:

startTestDb.sh (Unix/Linux)

PicoSQL consists fundamentally in a program, picosqld, to activate through inetd (or xinetd) or picoserv. In such a way it becomes a net service binded to a port, that is to a entire number comprised between 1 and 65535; this number (as an example 6789) must always be specified on the command line of picosqld. As an example:

picosqld 6789

For the activation with inetd (or xinetd), you must see the relative documentation. picoserv is a simple program that replaces inetd, mainly for scopes of test or debugging: its usage is the following:

picoserv [-f] commandLine portNumber

In our case the activation of picosqld can be obtained with the following command line:

picoserv “picosqld 6789″ 6789

To notice as the port number is specified two times, as an argument of picosqld and as an argument of picoserv.

When picosqld receive a connection request, it reads a configuration file to find the necessary informations. This file is a text file on Unix/Linux systems.

# Unix/Lunixthe file read for configuration is

$HOME/.picosql.ini

or, if this file is missing

/etc/picosql.ini

The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain attributes of the form

name=value

The file is line-based – that is, each newline-terminated line represents either a comment, a section name or a parameter. Section and parameter names are not case sensitive. Only the first equals sign in a parameter is significant. Any line beginning with a semicolon (‘;’) or a hash (‘#’) character is ignored, as are lines containing only whitespace. Each section corresponds to a database and comprises information like user, password and DB location. In the following example there are two database declared, the former called picoSqlTest, is accessible by anyone while the latter, called rubrica is accessible only by user pico giving the appropriate password.

[picoSqlTest]
DataDirectory=/home/test.db

[rubrica]
DataDirectory=/home/rubrica.db
User=pico
Password=soft
PicoOdbcTrace=NO
SuspensiveLock=YES
; for picosql client only
server=localhost
port=6789

What’s New in This Release:

· This version fixes a problem on authentication and a bug when the connection fails.

Binary mirror 1 (tar.gz)

Sources mirror 1 (tar.gz)

MySQL is a client and server implementation that consists of a server daemon (mysqld) and many different client programs/libraries.

MySQL is a type of SQL database management featured in Thelix hosting plans. A database is an organized collection of information that a computer uses to select and display data.

Databases can help organize and enhance your site content. Sites with dynamic pages and/or shopping cart software often need an underlying database structure. Back to Top
www.thelix.net/support/faq/glossary.htm

Pronounced Òmy ess cue elÓ (each letter separately) and not “my SEE kwill.” MySQL is an open source RDBMS that relies on SQL for processing the data in the database. MySQL provides APIs for the languages C, C++, Eiffel, Java, Perl, PHP and Python. In addition, OLE DB and ODBC providers exist for MySQL data connection in the Microsoft environment. A MySQL

NET Native Provider is also available, which allows native MySQL to .NET access without the need for OLE DB. MySQL is most commonly used for Web applications and for embedded applications and has become a popular alternative to proprietary database systems because of its speed and reliability. MySQL can run on UNIX, Windows and Mac OS.

MySQL is a relational database management system, which means it stores data in separate tables rather than putting all the data in one big area. This adds flexibility, as well as speed.

The SQL part of MySQL stands for “Structured Query Language,” which is the most common language used to access databases. The MySQL database server is the most popular open source database in the world. It is extremely fast and easy to customize, due to its architecture.

Extensive reuse of code within the software, along with a minimalist approach to producing features with lots of functionality, gives MySQL unmatched speed, compactness, stability, and ease of deployment.

Their unique separation of the core server from the storage engine makes it possible to run with very strict control, or with ultra fast disk access, whichever is more appropriate for the situation.

RedHat RPM mirror 1 (i386)

RedHat RPM mirror 2 (x86 64)

RedHat SRPM mirror 1

Sources mirror 1 (tar.gz)

Count on the Highest Quality of Service
Oracle Database 10g delivers the response times your users demand and reduces your cost of downtime. Only Oracle offers the availability, scalability, and low-cost benefits of clustering with Oracle Real Application Clusters.

Lower Costs with the Self-Managing Database
Oracle automates time-consuming, error-prone administrative tasks, so DBAs can focus on strategic business objectives. Studies from the Edison Group prove Oracle Database 10g offers superior manageability and significant cost savings over both IBM DB2 8.2 and Microsoft SQL Server 2000.

Build Your Foundation for Grid Computing
Oracle Database 10g with Real Application Clusters and Automatic Storage Management coordinates the use of large numbers of servers and storage acting as one self-managing Grid for the highest quality of service on low-cost, modular hardware.

Oracle Database 10g is the industry’s first database designed for grid computing. Low entry-level pricing makes Oracle the best choice for large enterprises and small to midsize businesses alike, with a variety of editions to choose from:

Enterprise Edition

Industry-leading performance, scalability, and reliability for OLTP, decision support, and content management.
View a list of Enterprise Edition options.

Standard Edition

Four-processor version of Oracle Database 10g, including full clustering support.

Standard Edition One

Two-processor version of Standard Edition at an attractive entry-level price.

Personal Edition

Full-featured version for individuals, compatible with the entire Oracle Database family.

Lite Edition

Complete software for building, deploying, and managing mobile database applications.

Sources mirror 1 (gz)

Transactions
Write Ahead Log
Multiple Isolation Levels
BTree Indexes
Entry Level SQL-92
System Catalogs

A distinguishing feature of the project is that the DBMS is being built in a modular fashion. The aim is ensure that each module is usable on its own ; for example, the Lock Manager or the Log Manager modules can be used on their own even if the rest of the system is not of interest.

There will be two major sub-systems in the dbms backend. The Data Manager subsystem is named RSS, and is responsible for implementing transactions, locking, tuple management, and index management. This sub-system is currently under development.

The second major sub-system will be called SQL Manager. Its job will be to parse SQL statements, produce optimum execution plans, and execute the SQL statements. Development of this sub-system is expected to start sometime in 2006.

SimpleDBM is being built in Java 5.0 and will use new features such as java.util.concurrent package and Generics available in this version of Java. SimpleDBM will not be compatible with previous versions of Java.

Binary mirror 1 (jar)

Sources mirror 1 (zip)

MySQL project is a client/server implementation that consists of a server daemon (mysqld) and many different client programs/libraries.

MySQL is a type of SQL database management featured in Thelix hosting plans. A database is an organized collection of information that a computer uses to select and display data.

Databases can help organize and enhance your site content. Sites with dynamic pages and/or shopping cart software often need an underlying database structure. Back to Top
www.thelix.net/support/faq/glossary.htm

Pronounced Òmy ess cue elÓ (each letter separately) and not “my SEE kwill.” MySQL is an open source RDBMS that relies on SQL for processing the data in the database. MySQL provides APIs for the languages C, C++, Eiffel, Java, Perl, PHP and Python. In addition, OLE DB and ODBC providers exist for MySQL data connection in the Microsoft environment. A MySQL

NET Native Provider is also available, which allows native MySQL to .NET access without the need for OLE DB. MySQL is most commonly used for Web applications and for embedded applications and has become a popular alternative to proprietary database systems because of its speed and reliability. MySQL can run on UNIX, Windows and Mac OS.

MySQL is a relational database management system, which means it stores data in separate tables rather than putting all the data in one big area. This adds flexibility, as well as speed.

The SQL part of MySQL stands for “Structured Query Language,” which is the most common language used to access databases. The MySQL database server is the most popular open source database in the world. It is extremely fast and easy to customize, due to its architecture.

Extensive reuse of code within the software, along with a minimalist approach to producing features with lots of functionality, gives MySQL unmatched speed, compactness, stability, and ease of deployment.

Their unique separation of the core server from the storage engine makes it possible to run with very strict control, or with ultra fast disk access, whichever is more appropriate for the situation.

RedHat RPM mirror 1 (Server)

RedHat RPM mirror 2 (Client)

RedHat SRPM mirror 1

Sources mirror 1 (tar.gz)

iODBC Driver Manager and SDK enables the development of database-centric solutions that are both database and platform independent.

What is the ODBC Value Proposition?

The ability to develop applications independent of back-end database engine.

What is iODBC?

iODBC is the acronym for Independent Open DataBase Connectivity, an Open Source platform independent implementation of both the ODBC and X/Open specifications. It is rapidly emerging as the industry standard for developing solutions that are language, platform and database independent.

What is the iODBC Value Proposition?

The ability to develop applications independent of back-end database engine, operating system, and for the most part programming language. Although ODBC and iODBC are both ‘C’ based Application Programming Interfaces (APIs) there are numerous cross language hooks and bridges from languages such as: C++, Java, Perl, Python, TCL etc.

iODBC has been ported to numerous platforms, including:

Linux (x86, Itanium, Alpha, Mips, and StrongArm), Solaris (Sparc & x86), AIX, HP-UX (PA-RISC & Itanium), Digital UNIX, Dynix, Generic UNIX 5.4, FreeBSD, MacOS 9, MacOS X, DG-UX, and OpenVMS.

This is a great SDK for porting WIN32-based ODBC applications to Linux and other OS platforms.

What’s New in This Release:

· Added support for GTK+ 2.x
· Fixed long mutex lock on connect
· Fixed problems with SQLBrowseConnect
· Fixed missing functions in export list
· Fixed core dump when checking for driver odbc version
· Fixed allocation error in SQLDescribeCol
· Fixed rpm specification for RedHat
· Fixed porting problems on FreeBSD, OpenBSD and OSF
· Use SQLFetchScroll in iodbctest

RedHat RPM mirror 1

RedHat SRPM mirror 1

Sources mirror (tar.gz)

MUSCLE has been developed, used, and refined as the networking component of BeShare, CueStation, CueConsole, and various other audio control applications at Level Control Systems for over four years.

Here are some key features of “MUSCLE”:

· Use BMessage-like muscle::Messages under any operating system.
· Send flattened muscle::Messages from one computer to another over TCP streams, eliminating unnecessary compatibility and protocol-versioning hassles.
· Run a “muscled server” on a central machine, and write (or download) client programs to log in to the server and communicate through it. Once logged in, client programs can discover who else is logged in, send muscle::Messages to other clients, and store muscle::Messages in the server’s RAM for other clients to download later. Clients can also “subscribe” to selected data on the server, and be automatically notified whenever it changes. Unicast-style, multicast-style, and broadcast-style Message routing are all supported via an intelligent hierarchical pattern-matching routing mechanism. Writing multiplayer games, IRC style chat applications, SETI style distributed calculation apps, or any other type of distributed software is made easy because MUSCLE handles all the dirty work for you!
· Customize the included “muscled server” by defining your own session logic or message-streaming protocol. (Note that this is only necessary for certain specialized applications–the standard server provides sufficient functionality for most things)
· Write your client code in C++, Java, or Python. Single-threaded and multi-threaded messaging APIs are provided for all three languages.
· Or just use the included message, string, dataIO, hashtable, dequeue, string-tokenizer, reference-count, regular expression and pattern matching parser, and object-pool code by themselves, as handy cross-platform utility classes. All source code is included, and you are free to use and abuse it any way you wish.
· See the Beginner’s Guide for a more detailed description of the system and its capabilites.

What’s New in This Release:

· This release includes various minor bugfixes, features, and code cleanup.

Sources mirror 1 (zip)

Unlike other applications, Online Medical DataBase is built upon a compatible and modular system , a system conceived to be adaptable to the needs and structures of each medical center who uses it.

OMD is a dependable, unbreakable system, answering in a professional and timely manner to the requirements of its most demanding users.

Requirements:

· Web server with PHP 5.x or higher.
· A Postgresql server, 8.1 or higher compiled with tcl support

Sources mirror 1