Free statements software for linux

Database Fishing Tool is short DaFT is a front-end to any database that can be connected to with an ODBC driver. DaFT allows you to browse the database objects, view data in tables and views, and create and execute SQL statements, also as a script, including variable scanning.
DaFT contains a database objects list (tables and views), list of columns and column properties, a table for data snapshots, detailed data view, a notepad, a table for viewing the outcome of select statements, T-SQL or PL/SQL statements, a SQL statement editor with syntax highlighting, and a screen to follow all ODBC driver messages (errors etc.).
All selected data can be saved into a file. The supported file formats are HTML, XLS, CSV, SyLK, and DIF. The SQL statements can be saved into a text file.
Enhancements:
- Handle Tables, Views, and colums with names (partly) in capitals with surrounding quotes.
- Some bug fixes...

Pontoon is a PHP CMS framework. Pontoon supports you, when you develop in PHP.
Enhancements:
- A minor fix was made to html/classes/textpage.class.
- Error handling was made tighter.
- Error handling was added to Web pages.
- "die" statements were removed from MySQL function calls.
- html/libs/.htaccess and html/styles/blue.css were added.
- The default slogan in html/classes/config.class was changed.
- The nodename variable was fixed for the case where Pontoon isnt installed in document root.

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.

importgraph.py is a Python script that attempts to extract module dependencies from the import statements in a Python project.

This projects output can be fed into graphviz to produce graphs as these examples show.

Oracle::SQL is a Perl extension for building SQL statements.

SYNOPSIS

use Oracle::SQL;
No automatically exported routines. You have to specifically to import the methods into your package.
use Oracle::SQL qw(:sql);
use Oracle::SQL /:sql/;
use Oracle::SQL :sql;

This is a package initializing object for Oracle::SQL::Builder.

SQL::Generator is a Perl module to generate SQL-statements with oo-perl.

SYNOPSIS

use SQL::Generator;

With this module you can easily (and very flexible) generate/construct sql-statements. As a rookie, you are used to write a lot of sprintf`s every time i needed a statement (i.e.for DBI).

Later you start writing your own functions for every statement and every sql-dialect (RDBMS use to have their own dialect extending the general SQL standard). This SQL::Generator module is an approach to have a flexible abstraction above the statement generation, which makes it easy to implement in your perl code. Its main purpose is to directly use perl variables/objects with SQL-like code.

BasicQuery is a Java-based application used to access databases through JDBC. It features a Swing-based GUI and includes capabilities useful to developers when testing SQL statements against a database. BasicQuery also produces timing information, which is valuable during tuning exercises.