Free execute sql software for linux

Since MySQL is the most popular SQL server that is used in conjunction with web sites, there was a need for incremental backup utility. ZZEE Active SQL Backup is designed for clients of web hosting companies, and can be useful to system administrators as well.
Main features:
- Can perform *incremental* backup of MySQL database
- Can perform full backup of MySQL database
- Can replicate database
- Can process SQL queries
- Can dump database structure
- Can suggest database changes needed to process incremental backup
- Can send data backed up by email
- Can transfer backed up data by FTP to other computer (if Net::FTP is installed)
- Can compress backed up data
Usage synopsis
Active SQL Backup can do incremental or full backups of MySQL database as often as needed. It is suitable both for the clients of web hosting companies who can not get access to MySQL update logs and for the host administrators. Backup syntax is:
shell> ./zmdb.pl -b
It stores backup files in BACKUP_DIR, specified in user_settings.txt, named like YYYY_MM_DD_hh_mm_ss.sql[.gz]. The backup files consist of series of SQL INSERT statements and may contain DELETE statements. The database scheme is stored in file database_name.create.sql. If gzip is available, then Active SQL Backup automatically uses it to compress stored data. The program can automatically send backed up files by email or upload to the other computer by FTP.
If the system fails, Active SQL Backup can restore the database. Restore syntax for incremental backups is:
shell> ./zmdb.pl -r
If you make full backups, restore syntax is the following:
shell> ./zmdb.pl -e < BACKUP_DIR/database_name.create.sql
shell> ./zmdb.pl -e < BACKUP_DIR/YYYY_MM_DD_hh_mm_ss.sql &
The first line is needed to restore database structure, and the second is the *most recent* data file. You may need to "gunzip" it before supplying to restore.
You can use the program to dump database structure
shell> ./zmdb.pl -s > structure_dump_file
or to process queries. The latter feature is useful if you need to process queries regularly, for example, to update membership status of the users of your online service. The syntax to execute SQL queries is:
shell> ./zmdb.pl -e < some_sql_file
Where format of some_sql_file is the same as with Mysql utility: SQL statements are separated by semicolon. Note that if you pass SELECT queries to Active SQL Backup, then no result will be returned.
Syntax summary is:
zmdb.pl [SINGLE_OPTION]
-a --advice suggest database modifications and tables_config.txt
-b --backup backup database structure and data
-e --execute execute SQL queries [from STDIN]
-h --help print this screen
-r --restore restore database structure and data
-s --structure dump database structure [to STDOUT]

AxKit::XSP::ESQL is an Extended SQL taglib for AxKit eXtensible Server Pages.

SYNOPSIS

Add the esql: namespace to your XSP < xsp:page > tag:

< xsp:page
language="Perl"
xmlns:xsp="http://apache.org/xsp/core/v1"
xmlns:esql="http://apache.org/xsp/SQL/v2"
>

And add this taglib to AxKit (via httpd.conf or .htaccess):

AxAddXSPTaglib AxKit::XSP::ESQL

This tag library provides extensive support for executing SQL statements from within XSP. This tag library is the same as the Cocoon ESQL taglib.

TAG REFERENCE

Note that below we use the esql: prefix as a convention, however you can use whatever prefix you like provided it is mapped to the appropriate namespace.

< esql:connection>

parent: none

This is the required wrapper element that declares your connection.

< esql:driver>

parent: < esql:connection>

The contents of this element define the DBI driver to be used. For example, Pg, Sybase, Oracle.

You can also add an optional attribute: transactions=no to the driver element, to indicate that this driver does not support transactions (or just that you dont want to use transactions).

< esql:dburl>

parent: < esql:connection>

The name of this tag is a hang-over from the Cocoon (Java) version. In the AxKit version this is simply anything that goes after the driver in the connection string. So for PostgreSQL you might have in here dbname=axkit, to connect to the "axkit" database. The full connect string is constructed as follows:

"dbi:$driver" . ($dburl ? ":$dburl" : "")

See your DBD driver documentation for more details on what is valid for the connection string.

< esql:username>

parent: < esql:connection>

The username to connect to the database with.

< esql:password>

parent: < esql:connection>

The password to use to connect to the database.

< esql:execute-query>

parent: < esql:connection>

This tag is a wrapper tag around queries. You may have as many queries as you like within a single < esql:connection> tag.

< esql:skip-rows>

parent: < esql:execute-query>

The contents of this tag (which may be an < xsp:expr>) define a number of rows to skip forward in the result set.

< esql:max-rows>

parent: < esql:execute-query>

The maximum number of rows to return.

< esql:query>

parent: < esql:execute-query>

The contents of this tag define the query to be executed.

< esql:parameter>

parent: < esql:query>

This tag can be put in your SQL query everywhere you might put a ? in your SQL in DBI. ESQL is intelligent enough to create a cached statement when you do this, and only execute your code when necessary. You put an expression (or another taglib) within the parameter tag (see the example below).

< esql:results>

parent: < esql:execute-query>

The contents of this tag are "executed" whenever the query returns some results.

< esql:row-results>

parent: < esql:results>

The contents of this tag are "executed" for each row of the results

< esql:get-columns>

parent: < esql:row-results>

This tag gets all of the columns in the current row, and outputs them as < column_name>value< /column_name>. If you specify an attribute tag-case="upper", all columns are upper case. Alternatively, "lower" gives you all tags in lower case. An ancestor attribute is also allowed, see "Nested Results" below for more details.
get-*

parent: < esql:row-results>

These are:

get-column
get-string
get-boolean
get-double
get-float
get-int
get-long
get-short
(and more below)

Each of these takes either an attribute column="name", or a child tag, < esql:column> which gives the column name. Alternatively either the attribute or child element can be an integer (starting at 1) specifying the column number.
Also allowed is an ancestor attribute, which is an integer (default 0), which indicates how far up the nested results you go. See Nested Results below.

< esql:get-date>, < esql:get-time>, < esql:get-timestamp>

parent: < esql:row-results>

These tags are the same as get-* above, except they also take a format="..." attribute, which contains a strftime formatting string.

< esql:get-xml>

parent: < esql:row-results>

Again the same as get-* above. This tag assumes the contents of the column are valid XML, and appends that XML into the result tree.

< esql:get-row-position>

parent: < esql:row-results>

Gets the current row number. Optional ancestor attribute.

< esql:get-column-name>

parent: < esql:row-results>

Gets the column name indicated by the numbered column in the column="..." attribute, or the child < esql:column> element. The attribute/child can actually be a string (name), but then what is the point of that?

< esql:get-column-label>

parent: < esql:row-results>

Gets the label of the column. This is a hang-over from the Cocoon java implementation where sadly nobody seems to know what label is compared with name. In this case, get-column-name is always lower case, whereas get-column-label is returned in the case that the DBD driver returns it as.

< esql:get-column-type-name>

parent: < esql:row-results>

Returns the TYPE_NAME of the column indicated as other get-* elements. See the DBI docs for more details.

< esql:no-results>

parent: < esql:execute-query>

The contents of this element are executed when the SQL returned no rows.

< esql:update-results>

parent: < esql:execute-query>

The contents of this element are executed when the SQL was an update statement. The number of rows updated are in the $rv variable.

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.

Chemistry::SQL is an access database functions module.

SYNOPSIS

use strict;
use Chemistry::SQL;
use Chemistry::Artificial::SQL;

my $db_name = $ARGV[0];
my $file = $ARGV[1];

my $db1 = Chemistry::SQL::new(db_host=>"127.0.0.1",db_user=>"root",db_port=>"3306",db_pwd=>"",
db_name=>$db_name,db_driver=>"mysql");
if ($db1->db_exist)
{ $db1->connect_db;
$db1->del_tables;
$db1->create_tables_mysql;
$db1->inscomp_from_file("$file");
}
else
{
$db1->create_db;
$db1->connect_db;
$db1->create_tables_mysql;
$db1->inscomp_from_file("$file");
}
# Reaction Insertion

my $qart = Chemistry::Artificial::SQL::new($db1);
my $qr =$qart->q_reaccion(C=CC=C.C=C>>C1=CCCCC1,smiles);
$db1->reactionsert($qr,"","0");

This package provides the necessary functions to interact with the database. The methods implemented in this module are oriented to give users control of the database without knowing how to use SQL queries.

JDBC SQL Profiler is a quickly hacked tool to do statistics on SELECT queries in order to know where it is most efficient to create indexes.

This small tool, released under an Apache-based license connects to the P6Spy JDBC logger and displays in real time the queries going to the database. It uses an integrated SQL parser to build statistics on the most accessed tables and columns and can generate SQL index creation files.

Other information is also gathered and displayed, such as the request time for a single request, for a class of request, and for all the requests. Sorting may be done on these views to detect database problems efficiently.

This tool can be very useful when you have a big volume of queries that you need to analyze not one by one (meaning that the specific time isnt that much of interest), but rather when you want to know what "group" of queries is taking a lot of time, such as queries on the same tables and columns but with different query values. The integrated SQL parser (built with ANTLR) is used to analyze the incoming SELECT queries.

The Swing GUI was based on Apaches Log4J Chainsaw, but all the bugs are mine. Also contributors are welcome to test, make new suggestions, give their opinion and submit patches.

JoSQL (SQL for Java Objects) provides the ability for a developer to apply a SQL statement to a collection of Java Objects.
JoSQL provides the ability to search, order and group ANY Java objects and should be applied when you want to perform SQL-like queries on a collection of Java Objects.
Example:
// Get a list of java.io.File objects.
List myObjs = getMyObjects ();
// Create a new Query.
Query q = new Query ();
// Parse the SQL you are going to use, it is assumed here that
// "myObjs" contains instances of "java.io.File".
q.parse ("SELECT name,length " +
"FROM java.io.File " +
"WHERE fileExtension (name) = :fileExt " +
"ORDER BY length DESC, name " +
"EXECUTE ON RESULTS avg (:_allobjs, length) avgLength");
// Set the bind variable "fileExt".
q.setVariable ("fileExt", "java");
// Execute the query.
QueryResults qr = q.execute (myObjs);
// Get the average length, this is a save value, the result
// of executing the call "avg (:_allobjs, length)", it is saved against
// key: "avgLength".
Map saveValues = qr.getSaveValues ();
Number avg = (Number) saveValues.get ("avgLength");
// Cycle over the results.
List res = qr.getResults ();
for (int i = 0; i < res.size (); i++)
{
// This time there is a List for each row, index 0 holds the name of
// the file that matched, index 1 holds the length.
List r = (List) res.get (i);
System.out.println ("NAME: " + r.get (0));
System.out.println ("LENGTH: " + r.get (1) + ", AVG: " + avg);
}
Enhancements:
- This release focuses on bug fixes.

YASQL project is an open source Oracle command line interface. It features a much kinder user interface than SQL*Plus (sqlplus).
This is meant to be a complete replacement for SQL*Plus when dealing with ad hoc queries and general database interfacing.
Main features:
- full ReadLine support for command history and tab completion
- alternate output methods
- table
- list
- CSV
- redirection and piping of query results
- query editing
- scripting
- easy administrative data dictionary commands.
Enhancements:
- Fixed the DECIMAL problem with describe command.
- Added sql mode with i (patch by Ed Avis).
- Added redirectors (>, >>, |) to describe.
- Added show user command.
- Added show uid command.
- Added new makefile targets: clean, check. (patch by Ed Avis)
- Added "and owner = ?" to some show targets (patch by anonymous).
- Added command_complete_list feature and config option.
- Added disconnect command
- Added command completion: select, update, insert, delete, execute, etc.
- Added table.column name completion.
- Added feature to run tty-less (patch by Michael Kroell).
- Added a workaround for SunOSs alarm() bug (patch by Ed Avis).
- Fixed some minor issues in parser code.