Free data from your database will be placed in the document software for linux

QDBM is a library of routines for managing a database. The QDBM database is a simple data file containing records, each is a pair of a key and a value.
Every key and value is serial bytes with variable length. Both binary data and character string can be used as a key and a value. There is neither concept of data tables nor data types. Records are organized in hash table or B+ tree.
As for database of hash table, each key must be unique within a database, so it is impossible to store two or more records with a key overlaps. The following access methods are provided to the database: storing a record with a key and a value, deleting a record by a key, retrieving a record by a key.
Moreover, traversal access to every key are provided, although the order is arbitrary. These access methods are similar to ones of DBM (or its followers: NDBM and GDBM) library defined in the UNIX standard. QDBM is an alternative for DBM because of its higher performance.
As for database of B+ tree, records whose keys are duplicated can be stored. Access methods of storing, deleting, and retrieving are provided as with the database of hash table. Records are stored in order by a comparing function assigned by a user. It is possible to access each record with the cursor in ascending or descending order.
According to this mechanism, forward matching search for strings and range search for integers are realized. Moreover, transaction is available in database of B+ tree.
QDBM is written in C, and provided as APIs of C, C++, Java, Perl, and Ruby.
QDBM is available on platforms which have API conforming to POSIX.
Enhancements:
- The utility API was enhanced.
- A bug related to B+ tree API for Ruby was fixed.

JDatabaseImport is a simple tool created to import data between different databases.
How does it work?
You can work with it in two ways, either using a configuration file or accessing its api using Java.
Example:
The following code show an example of a file called *export.xml*:
< export >
< from >
< driver >org.hsqldb.jdbcDriver< / driver >
< url >jdbc:hsqldb:hsql://localhost/source< / url >
< username >sa< / username >
< password >mysapass< / password >
< / from >
< to >
< driver >com.mysql.jdbc.Driver< / driver >
< url >jdbc:mysql://localhost/target< / url >
< username >root< / username >
< password >myrootpass< / password >
< / to >
< table name="firstTable"/ >
< table name="secondTable" >
< ignore >fieldToBeIgnored< / ignore >
< / table >
< table name="thirdTable"/ >
< / export >
Note that JDatabaseImport *will not* generate the target tables, but only import data from one source into the other.
In order to run JDatabaseImport, you need to put all drivers in the classpath and run it. The following code is an example on how to use it to import from mysql to hsqldb
java -cp mysql-connector-3.1.1.jar:hsqldb.jar:jdatabaseimport.jar br.com.caelum.jdatabaseimport.Main export.xml
Enhancements:
- This initial release has been tested with hsqldb, MySQL, Derby, and Oracle using some field types and different configurations.

XML::DB::DatabaseManager is an approximation to the XML:DB DatabaseManager.

SYNOPSIS

use XML::DB::DatabaseManager;
my $driver = Xindice; my $url = http://localhost:4080;
eval{ $dbm = new XML::DB::DatabaseManager(); $dbm->registerDatabase($driver); $col = $dbm->getCollection("xmldb:$driver:$url/db/test"); ...... };
if ($@){ die $@; }
deregisterDatabase($driver);

This is the initial class to use to get access to the XML:DB modules, an approximate implementation of the XML:DB API defined for Java at http://www.xmldb.org. This implementation is designed to give a uniform Perl access over XML-RPC to both of the current free native XML databases, eXist and Xindice, as well as providing the same front-end for a plain file-system.

Unlike the DatabaseManager defined in the XML:DB API (which is a Factory), this simply registers driver names, generating a new Database instance for each request. Multiple database drivers can be used simultaneously (eg. to transfer data from one database to another). The drivers themselves are rather confusingly called Databases in this system.

Only one DatabaseManager can be instantiated in a program.

Aqua Data Studio program is a database query tool and administration tool that allows developers to easily create, edit, and execute SQL scripts, as well as browse and visually modify database structures.
Aqua Data Studio provides an integrated database environment with a single consistent interface to all major relational databases. This allows the database administrator or developer to tackle multiple tasks simultaneously from one application.
Main features:
Query Analyzer/Window
- Aqua Data Studios sophisticated Query Analyzer allows users to work on database scripts with specific RDBMS syntax highlighting and auto-completion to develop and test SQL scripts. Other features to speed up development include SQL automation, auto-describe and sortable multi-grid results. The query analyzer also provides client side variable binding, allowing a user to execute stored procedures or functions with local variables binded to receive out parameters. The query window also provides two modes of operation, using a SplitPane View or a MultiTab View for the editor and the query results.
Schema Browser & Visual Editing
- Its graphical browsing capabilities allow you to understand the structure and dependencies of the database schema with a single mouse click. The schema browser also allows you to visually edit any schema object with a graphical design form to CREATE, ALTER or DROP the object. Visual editing supports Tables, Indexes, Procedures, Data Types and other schema objects. The visual editors also provides an SQL preview of all the commands to be executed to commit the operation.
Schema Extraction & DDL Scripting
- Its graphical browsing allows you to extract the structure definition of all schema objects and to script the SQL DDL and DML (eg CREATE, ALTER, DROP, SELECT, INSERT, UPDATE and DELETE) syntax for database schema objects (including Tables, Views, Triggers, Stored Procedures and Functions).
Table Data Editor
- A powerful Table Data Editor allows you to modify your results graphically and save them. By writing a single table SELECT statement in the Query Analyzer and clicking on the Execute Edit button, a separate window is opened with the query results for you to edit and save. You may also browser to a table in the schema browser and select the Edit Table from the popup menu to edit the first 1000 records in a table.
Enhancements:
- Enhancements in this release include OS X Integration, Windows integration, complete and customizable keymapping, a schema difference tool, a directory difference tool, a file difference tool, a tab difference tool, a copy history difference tool, SQL Server DBA tools, and Sybase DBA tools.
- In total, there were over 100 new features.

SILVERCODERS T-Script is a scripting language which primary purpose is to generate text files.

It can be useful for processing template files based on some additional data retrieved from data sources like sql databases or other text files. T-Script can be easly embedded into your application and work with its internal data.

SILVERCODERS T-Script library is now being intergrated into the LMS project.

Dee-Python project is an implementation of a truly relational database language with Python. Inspired by Date and Darwens Third Manifesto, it addresses the problems of impedance mismatch between programming languages and databases and the weakness of SQL.

Mind The Gap

Most of todays programs handle data in one way or another and often this data is stored in some kind of relational database. To read and modify this data, a program must bridge the gap between its representation and the one used by the dialect of SQL that the database provides. This bridge typically comprises a database API that sends queries as text strings, often accompanied by some kind of table-to-object mapper that has to coerce data and relationships in both directions, usually with elaborate layers of abstraction in an effort to keep the two sides loosely coupled.

"Yet by obscuring the true data source these solutions end up throwing away the most compelling feature of relational databases; the ability for the data to be queried."

Microsoft, DLinq .NET Language-Integrated Query for Relational Data, May 2006.

This approach not only adds complexity and increases the need for data transformations but, most importantly, it destroys the significant advantages provided by the relational model of data. The relational model is built upon predicate logic which brings the power of formal reasoning to data: it is the only sound foundation available.

BlogTrader Platform is a free, open source stock technical analysis platform with a pluggable architecture that is ideal for extensions such as indicators and charts. BlogTrader Platform is built on pure java.
It supports parallel quote data retrieval from Yahoo! or ASCII text files, historical, intra-day, and real-time charts, and candle, bar, and line charts. It has a natural date/trading date view model. "MACD", "OBV", "ROC", "KD", "BIAS", "DMI", "RSI", "MTM", and "WMS" indicators and drawing of "Line", "Parallel", "Gann Angle", and "Fibonacci Line" are supported. You can easily write your own indicators.
Main features:
- Retrieve quote data in parallel from Yahoo! Finance, netfonds.se, or CSV files.
- Save quote data to local database (hsqldb).
- Adjust quote chart for splits and dividents if possibale (Yahoo! quote data only).
- Daily, Weekly, Monthly charts (Weekly, Monthly data are composed automatically from Daily data)
- Historical/Intra-Day/Real-Time Chart
- Real-time Ticker Board
- Update Daily, Weekly, Monthly Charts and their indicators automatically according to the newest tickers.
- Multiple quote-charts comparison
- Candle/Bar/Line
- Calendar/Trading date view
- Define indicators parameters separately for Daily, Weekly and Monthly charts, parameters can be saved as default or apply to all
- Add layer drawings separately for Daily, Weekly and Monthly. Save/Restore drawings.
- Carefully design for writing your own indicator easy, but in java (maybe will support scripts some day)
- Supports multiple platforms, includes windows, linux, macos, solaris, etc. (Java JRE 1.5 required)
- More to be come ...
Enhancements:
- Minor bugfixes