Free extract data software for linux

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.

Convert::BinHex can extract data from Macintosh BinHex files.

ALPHA WARNING: this code is currently in its Alpha release. Things may change drastically until the interface is hammered out: if you have suggestions or objections, please speak up now!

SYNOPSIS

Simple functions:

use Convert::BinHex qw(binhex_crc macbinary_crc);

# Compute HQX7-style CRC for data, pumping in old CRC if desired:
$crc = binhex_crc($data, $crc);

# Compute the MacBinary-II-style CRC for the data:
$crc = macbinary_crc($data, $crc);

Hex to bin, low-level interface. Conversion is actually done via an object ("Convert::BinHex::Hex2Bin") which keeps internal conversion state:
# Create and use a "translator" object:
my $H2B = Convert::BinHex->hex2bin; # get a converter object
while (< STDIN >) {
print $STDOUT $H2B->next($_); # convert some more input
}
print $STDOUT $H2B->done; # no more input: finish up

Hex to bin, OO interface. The following operations must be done in the order shown!
# Read data in piecemeal:
$HQX = Convert::BinHex->open(FH=>*STDIN) || die "open: $!";
$HQX->read_header; # read header info
@data = $HQX->read_data; # read in all the data
@rsrc = $HQX->read_resource; # read in all the resource

Bin to hex, low-level interface. Conversion is actually done via an object ("Convert::BinHex::Bin2Hex") which keeps internal conversion state:
# Create and use a "translator" object:
my $B2H = Convert::BinHex->bin2hex; # get a converter object
while (< STDIN >) {
print $STDOUT $B2H->next($_); # convert some more input
}
print $STDOUT $B2H->done; # no more input: finish up

Bin to hex, file interface. Yes, you can convert to BinHex as well as from it!
# Create new, empty object:
my $HQX = Convert::BinHex->new;

# Set header attributes:
$HQX->filename("logo.gif");
$HQX->type("GIFA");
$HQX->creator("CNVS");

# Give it the data and resource forks (either can be absent):
$HQX->data(Path => "/path/to/data"); # here, data is on disk
$HQX->resource(Data => $resourcefork); # here, resource is in core

# Output as a BinHex stream, complete with leading comment:
$HQX->encode(*STDOUT);

PLANNED!!!! Bin to hex, "CAP" interface. Thanks to Ken Lunde for suggesting this.
# Create new, empty object from CAP tree:
my $HQX = Convert::BinHex->from_cap("/path/to/root/file");
$HQX->encode(*STDOUT);

BinHex is a format used by Macintosh for transporting Mac files safely through electronic mail, as short-lined, 7-bit, semi-compressed data streams. Ths module provides a means of converting those data streams back into into binary data.

Locale::Maketext::Extract::Run is a Perl module interface to xgettext.pl.

SYNOPSIS

use Locale::Maketext::Extract::Run xgettext;
xgettext(@ARGV);

MDF audio extracter project is a tool to extract audio data from MDF/MDS audio cd images to wav or raw files. Tracks will be extracted to the current directory and named track_[num].wav or track_[num].raw. Output can also be redirected to stdout to allow the audio data to be fed to an encoder or player directly.
You need both a .mds and .mdf file to be able to extract tracks. The .mds file contains the information about the tracks, while the .mdf file contains the actual data. They usually should have the same name (except for the extension ofcourse). This is case sensitive, so for example FileName is not the same as filename.
Usage: mdfextract [options] file.mds
Options:
-i output mds info instead of extracting
-r extract raw track data
-s output to stdout instead of file
-t < num > extract single track (num > 0)
-q quiet, no output
Version restrictions:
- Probably does not work on big endian archs.

g3data is used for extracting data from graphs. In publications data is usually presented as graphs, while the actual data is often missing. The project makes the extracting process much easier. The commercially available alternative is called data thief.
Main features:
- Zoom windows for maximum accuracy
- Can handle logarithmic scales and non-ortogonal graphs
- Tabbed processing of multiple images consequetively
Enhancements:
- Added basic drag-n-drop support, current version only supports uri drops.
- Added preliminary basis for datapoint movement.
- Some of the graph properties are now hideable, to resolv issues on lower resolution screens.

Maypole::Plugin::QuickTable is a HTML::QuickTable convenience.

SYNOPSIS

use Maypole::Application qw( LinkTools QuickTable );

METHODS

setup

quick_table

Returns a HTML::QuickTable object for formatting data.

print $request->quick_table( %args )->render( $data );

The method gathers arguments from the quicktable_defaults method on the model class. This is a Class::Data::Inheritable method, so you can set global defaults on the main model class, and then override them in model subclasses. To preserve most settings and override others, say something like

$sub_model->quicktable_defaults( { %{ $model->quicktable_defaults }, %hash_of_overrides } );

Arguments passed in the method call override those stored on the model.

Arguments are passed directly to HTML::QuickTable->new, so see HTML::QuickTable for a description.

Additional arguments are:

object => a Maypole/CDBI object

Pass a Maypole/CDBI object in the object slot, and its data will be extracted and $qt->render called for you:

print $request->quick_table( %args, object => $object );

Related objects will be displayed as links to their view template.
If no object is supplied, a HTML::QuickTable object is returned. If an object is supplied, it is passed to tabulate to extract its data, and the data passed to the render method of the HTML::QuickTable object.

To render a subset of an objects columns, say:

my @data = $request->tabulate( objects => $object, with_colnames => 1, fields => [ qw( foo bar ) ] );

$request->quick_table( @data );

tabulate( $object|$arrayref_of_objects, %args )

Extract data from a Maypole/CDBI object (or multiple objects), ready to pass to quick_table->render. Data will start with a row of column names if $args{with_colnames} is true.

A callback subref can be passed in $args{callback}. It will be called in turn with each object as its argument. The result(s) of the call will be added to the row of data for that object. See the list template in Maypole::FormBuilder, which uses this technique to add edit and delete buttons to each row.

Similarly, a field_callback coderef will be called during rendering of each field, receiving the object and the current field as arguments. See the addmany template for an example.

Arguments:

callback coderef
field_callback coderef
with_colnames boolean
fields defaults to ( $request->model_class->display_columns, $request->model_class->related )
objects defaults to $request->objects
orderby_link( $field, [ $model_class ] )

Build a link for a column header. Controls whether the table should be sorted by that column. Toggles sort direction.

The $model_class parameter is only necessary when building a table for a class different from the current model class for the request.

screen-scraper project is a tool used to extract data from web sites. You might use screen-scraper for the following purposes:
- Data Mining and Extraction
- Data Migration
- Application Integration
- Business Intelligence
- Web Task Automation
- Portal Components
- Meta-Searching
- Archiving
The screen-scraper application consists of two primary pieces:
- Workbench: A graphical user interface provides an intuitive approach that allows you to designate pages and specific pieces of information to be extracted.
- Server: After using the workbench to designate the data to be scraped, screen-scraper can be run in a server mode, much like a database. External applications can then connect to screen-scraper, which will pull data off of the designated web sites, then return them to the calling application. For example, you might build a web-based application using Active Server Pages (ASP) or PHP that invokes screen-scraper to search for products found on an external web site in real-time.
Additionally, screen-scraper can be started in a non-graphical mode from the command line such that it can be scheduled or invoked on-demand.
screen-scraper can automate many of the tasks typically required when scraping data from web pages, such as tracking cookies, logging in to web sites, and traversing search results pages.
Depending on the programming languages and platforms you most prefer, screen-scraper is likely to be familiar to you. screen-scraper contains an internal scripting engine that supports:
- VBScript
- JScript
- Perl
- Interpreted Java
- JavaScript
- Python
When invoking screen-scraper externally take your pick from the following languages:
- Java
- PHP
- Anything COM-based (such as Active Server Pages, Visual Basic, and Visual C++)
- .NET (both Microsoft-based and Mono)
- Cold Fusion
Enhancements:
- Several bugfixes and minor features have been added, including automatic backup of the database, enhanced HTML rendering and HTML stripping, fixing an error that caused duplicate scripts to appear at times on import, and fixing multiple errors relating to international character sets and non-ASCII characters.

ZZIPlib library is intentionally lightweight, it offers the ability to easily extract data from files archived in a single zip file. Applications can bundle files into a single zip archive and access them. The implementation is based only on the (free) subset of compression with the zlib algorithm which is actually used by the zip/unzip tools.

The library allows reading zip archives in a number of ways,
archive mode:

reading the zip directory and extracting files from it. This is the traditional mode as seen with unzip-utilities. Some extra unzip-utiles for transparent/magic mode are shipped as well.

replacement mode:

Use ZZIP_FILE / ZZIP_DIR pointers provided by zziplib and put them to work with routines originally developped to work with real directories and file handles. The API calls do follow traditional synopsis from posix/stdio.

transparent mode:

Use replacement handles and allow the open()-calls to automatically detect when a file is contained in a zip archive or when it is a real file in the file system. A filepath can be partly in a real filesystem and partly within the zip archive when one is seen.

ext magic

Use the same filepath to access either a zipped or real file - it looks for a real file and there is none then every subdirectory of the path is checked, a ".zip" extension appended, and the zipped file transparently opened. This can speed up dat-file development dramatically.

io/xor magic

The access to the filesystem can be hooked up - examples are given for xor obfuscation which is great for game artwork and AI data. A small intro for SDLrwops usage is given as well.