Search Results for "java implementation loader"

The project has been renamed CrNiCKL (chronicle) and moved to http://crnickl.sourceforge.net. ChronoDB is a data manager written in Java. It supports time series of any type. With its simple and powerful schema subsystem it takes charge of very large heterogeneous data sets. The software consist of an API and a generic implementation layer running on top of an SQL or a NoSQL system. Applications can mix objects from multiple ChronoDB databases.

MXQuery is a low-footprint implementation of XQuery 1.0, XQuery Update 1.0, XQuery Fulltext 1.0 and XQuery Scripting 1.0 as well as a subset of XQuery 1.1 (windowing, try/catch). It provides extensions to do data stream processing/CEP and SOAP/REST

MighTyD is a prototype for demo puposes & the first implementation of the temporal database model devised by Nikos Lorentzos, Hugh Darwen & CJ Date. It uses Tutorial D as its language & PostgreSQL for storage & is compliant with the The Third Manifesto.

This will be a tool for a human relations department. AIESEC ChangeIT project implementation on Embarcadero Technologies Iasi. Wel will use this page as an aid for the project's workflow.It will contain the database for CVs and employees of the company.

OpenRolap: an implementation of OLAP in a relational database. Conceptually simple, the current version is in MySQL, with a Java API. The API aims to avoid complex MDX-type language, instead to use a simple "filter path" structure.

Mayfly is an in-memory SQL implementation for unit testing. It is fast on small data sets and you can create or destroy a database as easily any other Java object.

An implementation (parser/interpreter) of SPARQL, a query language for RDF data that is the current recommendation of the W3C. Allows easy cusomization of the language and plugs in to several popular RDF servers, like Sesame.

Gemello is a relational database written in pure Java. Its design is aimed at teaching. If you're searching for a fast relational engine, Gemello won't be a good choice. Is's rather a good and simple example of relational database implementation.

The DBAbstract Server is a middleware database server solution written entirely in Java. It provides connection to any type of database implementation through one JDBC partially complient driver, client-server encryption and connection pooling.

jxDBCon a framework to ease the development JDBC drivers. By using it you can concentrate on the tasks specific to your DBMS and benefit from the generic solutions provided by jxDBCon. jxDBCon contains a featureful driver implementation for PostgreSQL

This is an implementation of the java DOM specification that keeps all its "parsed-node" data in disk files instead of RAM. This means you can create really big DOM trees an not use all your RAM.

By far the simplest and fastest petstore implementation. Available on CVS.

A Fast, in memory, Java based XMLDB implementation.

[PROJECT ABANDONED] This project will provide a 100% pure Java database implementation accessible via JDBC. The database is stored in plaintext files and loaded into RAM at runtime. Implements mySQL datatypes for trivial migration to/from mySQL.

Index Cards Library is an Java library implementation of 3x5 index cards. It's just a simple database. Implementation of a display is up to the developer who uses the library.

Rodin (Relational Object Dbms Implementing java binding in a Not-proprietary way) is a free implementation of Matisse, the proprietary object database. This project is still in early stage of developpement.

This is a sample implementation of the TransQuery processing model, enabling the use of XSLT as a query language over multiple XML documents. See <a href="http://www.xmlportfolio.com/transquery">http://www.xmlportfolio.com/transquery</a> for more info.

DBDOM bridges the gap between XML and relational databases. DBDOM is an implementation of the World-Wide Web Consortium's (W3C) Document Object Model in SQL. DBDOM turns any RDBMS into an XML application server.

Ontology-based user context manager supporting uncertainty and handling of histories based on a database implementation