Free statements tile software for linux

SQL::Statement::Embed can embed a SQL engine in a DBD or module.

SQL::Statement is designed to be easy to embed in other modules and to be especially easy to embed in DBI drivers. It provides a SQL Engine and the other module needs to then provide a data source and a storage mechanism. For example, the DBD::CSV module uses SQL::Statement as an embedded SQL engine by implementing a file-based data source and by using DBI as the user interface. Similarly DBD::Amazon uses SQL::Statement as its SQL engine, provides its own extensions to the supported SQL syntax, and uses on-the-fly searches of Amazon.com as its data source.

SQL::Statement is the basis for eight existing DBDs (DBI database drivers). If you have a new data source, you too can create a DBD without having to reinvent the SQL wheel. Its fun, its easy, become a DBD author today!

SQL::Statement can be also be embedded without DBI. Well explore that first since developing a DBD uses most of the same methods and techniques.

The role of SQL::Statement subclasses

SQL::Statement provides a SQL parsing and execution engine. It does not provide a data source or storage mechanism other than in-memory tables. The DBD::File module is a subclass of SQL::Statement that provides access to file-based storage mechanisms. Its quite possible to use things other than files as data souces, in which case we wouldnt use DBD::File, instead wed replace DBD::Files methods with our own. In the examples below, well use DBD::File, replacing only a few methods.

SQL::Statement provides SQL parsing and evaluation and DBD::File provides file-based storage. The only thing missing is a data source - what we actually want to store and query. As an example suppose we are going to create a subclass called Foo that will provide as a data source a simple file similar to a passwd file - one record per line, fields separated by colons, with only three fields "username, uid, gid".

Consider what needs to happen to perform a SELECT query on our Foo data:

* recieve a SQL string
* parse the SQL string into a request structure
* open the table(s) specified in the request
* define column names and postions for the table
* read rows from the table
* convert the rows from colon-separated format into perl arrays
* match the columns and rows against the requested selection criteria
* return requested rows and columns to the user

To perform operations like INSERT and DELETE, we also need to:

* convert rows from perl arrays into colon-separated format
* write rows
* delete rows

SQL::Statement takes care of all of the SQL parsing and evaluation. DBD::File takes care of file opening, reading, writing, and deleting. So the only things Foo is really responsible for are:

* define column names and postions for the table
* convert rows from colon-separated format into perl arrays
* convert rows from perl arrays into colon-separated format

In SQL::Statement subclasses these responsibilities are assigned to two objects, a ::Statement object is responsible for opening the table, defining the column names and positions, and for creating new ::Table objects. A ::Table object is responsible for reading, converting, writing, and deleting data.

HTML::TableTiler can easily generates complex graphic styled HTML tables.

HTML::TableTiler uses a minimum HTML table as a tile to generate a complete HTML table from a bidimensional array of data. It can easily produce simple or complex graphic styled tables with minimum effort and maximum speed.

Think about the table tile as a sort of tile that automatically expands itself to contain the whole data. You can control the final look of a table by choosing either the HORIZONTAL and the VERTICAL tiling mode among: PULL, TILE and TRIM.

The main advantages to use it are:

automatic table generation

Pass only a bidimensional array of data to generate a complete HTML table. No worry to decide in advance the quantity of cells (or rows) in the table.
complex graphic patterns generation without coding

Just prepare a simple table tile in your preferred WYSIWYG HTML editor and let the module do the job for you.

simple to maintain

You can indipendently change the table tile or the code, and everything will go as you would expect.

Mergeant is a database administration tool.

Mergeant allows to connect to any database through the Libgda library (MySQL, PostgeSQL, Oracle, etc) and manage data within the database.

Any DML (data manipulation: insertion, update, deletion and selection) query can be created to help managing the data (queries can have optionnal parameters), from SQL statements or from a GUI interface.

The database structure (tables, data types, etc) can be browsed (modification is on the TODO list), and graphical representations of the database relations can be created.

UJAC provides a collection of JAVA components which may be useful in some projects.
Each component is designed for easy use, easy integration into existing projects, extensibility and last but not least efficiency.
Enhancements:
Chart Module:
- Moved common types into the interface org.ujac.util.UjacTypes.
Form Module:
- Fixed handling of default values.
Print Module:
- At < insert-document > tag: Fixed offset handling.
- At tags < background-image > & < watermark >: Removed code that forces the existance of a page for the background image.
Utils Module:
- Added interface UjacTypes, which defines common types, used inside the UJAC project.
- Added class UjacTypeHelper, which provides methods to convert data type IDs to Strings and vice versa.
- Moved class XmlUtils into sub package org.ujac.util.xml
SimplePatternMatcher:
- Fixed handling of empty patterns (always matches).
Table:
- Moved common types into the interface org.ujac.util.UjacTypes.
TemplateInterpreter:
- Fixed handling of underscores that are not part of statements.
- Added class BaseObjectSerializer, which provides basic code to easily read/write Objects from/to XML.
Web Module:
- Added support for PageTiles to ActionContext.
- Added < tile > tag which includes PageTiles into JSPs.
- Added class WebFormSerializer, which reads/writes WebForm definitions from/to XML.
- Added support for dynamic form registration from XML definitions.
- Fixed bugs in form field value handling.
- Fixed bugs in form field rendering.

Step-by-Step is a simple logic game where you have to clear all colored tiles by stepping over them.

Depending on the colour of the tile, this takes one to three steps. Step-by-Step project contains 99 levels and a separate level editor.

Subtle application is a another tiling window manager with a slightly different approach to place the windows, in contrast to other tiling window managers like Wmii or Ion. The placement in subtle is done by tiling windows which arrange every child-window either in a horizontal or a vertical manner. Client or even tiling windows can be moved/dragged into a tile and will be arranged according to the tile type. Every window can be swapped too and shaded inside of it’s parent tile. (view)

This behaviour is mostly inspired by Wily, an emulation of ACME – the well-known Plan9 “editor”.

Configuration and theming is done with the help of Lua. Furthermore there is an extendable “statusbar” attached to the main tile. Sublets, small Lua scripts, provide features like a customizable clock or even a small progressbar for the battery capacity of a notebook.

The initial code was based on Aewm, but is meanwhile completely re-written.
Simplicty and flexibility are the goals of this project – besides not to be bloated of course. Controlling can be done either with the mouse or the keyboard – just as the user prefers.

Schema-compare is a script that will compares two database schema and show the differences side-by-side.
Schema-compare can also generate SQL statements that will alter the old database to match the schema of the new database.
The comparisons are correct, but the SQL statements at the bottom are not quite right, they are close to what is necessary, but probably not exactly right.
To install simply ungzip/untar the file wherever you want to put it in your web folder and then edit the include/config.inc.php file with the information needed to connect to the two databases you want to compare. Both databases need to be on the same database server and use the same username and password to connect to them.
Enhancements:
- This is the first release of schema-compare. It compares the database schema just fine, but the sql alter statements it creates could use some work.