Free statements seattle 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.

mysqlstress is small but powerfull program, though. It allows administrator, with a lot of arguments, to stress an mysql server to see if performance is given.
Usage
Usage: mysqlstress [OPTIONS]
-h, --hostname Connect to host. (default: localhost)
-u, --username User to log in. (default: root)
-p, --password Password to log in. (default: none)
-d, --database Database You want to connect. (default: mysql)
-S, --socket Connet to unix socket (default: NULL)
-P, --port Port number to use for connection. (default: 3306)
-n, --number Number of SQL statements per connection (default: 5000)
-s, --statement SQL statement you want to exec during stress test. (default "SELECT * FROM user")
-t, --threads Number of threads You want (default: 5000)
-i, --info Show version of MySQL Server
-c, --close Close MySQL connections (default: no). See README!
-q, --quiet No output, just work (default: no)
-V, --version Output version information and exit.
-H, --help Output this message and exit.
all options are logical, the only one is the -c or --close.
If you really want to stress your mysql dont close mysql connections.
Enhancements:
- first major release

SPindent (Server Page Indenter) is a JSP/PHP structural validator and indenter. It performs structural compatibility check of inner HTML generated from "parallel" branches of process flow statements such as if/else.

It allows for those HTML branches to have different entry and exit HTML stack points, as far as the branches are compatible.

This allows for verification and proper indentation of handy workarounds, as well as rusty pyramids. It is based on MixedCC (Mixed Compiler Compiler).

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.

Jifty::DBI::SchemaGenerator is a Perl module to generate table schemas from Jifty::DBI records.

This module turns a Jifty::Record object into an SQL schema for your chosen database. At the moment, your choices are MySQL, SQLite, or PostgreSQL. Oracle might also work right, though its untested.

SYNOPSIS

The Short Answer

See below for where we get the $handle and $model variables.

use Jifty::DBI::SchemaGenerator;
...
my $s_gen = Jifty::DBI::SchemaGenerator->new( $handle );
$s_gen->add_model($model);

my @statements = $s_gen->create_table_sql_statements;
print join("n", @statements, );
...
The Long Version
See Jifty::DBI for details about the first two parts.
MyModel
package MyModel;
# lib/MyModel.pm

use warnings;
use strict;

use base qw(Jifty::DBI::Record);
# your custom code goes here.
1;
MyModel::Schema
package MyModel::Schema;
# lib/MyModel/Schema.pm

use warnings;
use strict;

use Jifty::DBI::Schema;

column foo => type is text;
column bar => type is text;

1;
myscript.pl
#!/usr/bin/env perl
# myscript.pl

use strict;
use warnings;

use Jifty::DBI::SchemaGenerator;

use Jifty::DBI::Handle;
use MyModel;
use MyModel::Schema;

my $handle = Jifty::DBI::Handle->new();
$handle->connect(
driver => SQLite,
database => testdb,
);

my $model = MyModel->new($handle);
my $s_gen = Jifty::DBI::SchemaGenerator->new( $handle );
$s_gen->add_model($model);

# heres the basic point of this module:
my @statements = $s_gen->create_table_sql_statements;
print join("n", @statements, );

# this part is directly from Jifty::Script::Schema::create_all_tables()
$handle->begin_transaction;
for my $statement (@statements) {
my $ret = $handle->simple_query($statement);
$ret or die "error creating a table: " . $ret->error_message;
}
$handle->commit;

GTK Oracle is a GTK+ 2 interface to Oracle that aids in Oracle application development and testing.
Its features include a schema browser, multiple SQL work areas, SQL syntax highlighting, bind variable entry widgets in the command window, and SQL*Plus-style command scripting.
For SQL statement analysis and tuning there is a tree-style SQL statement "explain plan" facility and the ability to load SQL statements from the runtime cursor cache (V$SQL table), Oracle Statspack repository, and the Oracle Automatic Workload Repository in Oracle version 10g. Full statistics are available on loaded statements.
Main features:
- manually running your applications SQL, outside of the application itself
- trying to find out what queries your application is even running
- checking and gathering statistics
- comparing plans
- running statspack to evaluate results
- autotracing
- peeking in AWR
- peeking the shared pool / v$sqlarea / statspack SQL
- identifying high-resource SQL then this might be of some help.
Usage:
- SQL in the text buffer (anything that gets run via the Execute button) is run on its own thread in the background so it will not block the GUI part, and you can cancel it. This execution thread is started when you start up the program, hopefully never exits, and receives commands via a GLib asynchronous queue, so you can safely keep hitting Execute while a command is running, it will just execute them in order.
- If you log in as SYSDBA you will get a combo box just under the main menubar. Changing the value will execute ALTER SESSION SET CURRENT_SCHEMA=somebody; so when you browse it will be as if you were this user. Be aware that any SQL you execute will result in SYS being recorded as the parsing user in the cursor cache, however.
- If you want to access the cursor cache or statspack or AWR you will need to log in with SYSDBA privileges. You might be able to get away with simply having SELECT on SYS.V$SQLAREA and SYS.V$SQLTEXT.
- SYS is excluded from the cursor cache browsing results. Otherwise you end up with a mass of recursive SQL, which you are not going to be able to tune and that is the point here. If youre a masochist and you do want to browse recursives I suppose you can just modify the relevant SQL so that SYS is not exculded and recompile. Have fun.
- AWR features are only available on 10G servers.
- DBMS_OUTPUT works, go to Edit->DBMS OUTPUT Enable

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.