Free performing software for linux

Querylog project is a console tool for performing SQL queries on a (log) file.

Lines from one or more text files or stdin are matched, using regular expressions to an in memory database on which SQL queries can be performed.

You also specify queries in the config file (SELECTs, INSERTs, CREATE VIEWs, etc). Queries that generate output are printed to stdout in plain text at the moment. In the future it will be possible to specify output formatters. The tool is written in C++ using the boost program options and regex library and the sqlite libraries for the in memory database.

I first wrote this tool to extract accounting information from cups page log files (in which accounting infomation was on different lines than job information), but due to the generic nature of the tool it can be used in many situations in which specific information needs to be retrieved from (in the future multiple) text files and presented in a more usable format.

Building:

Youll need the boost headers and libraries for (program_options and regex) which you can get at http://www.boost.org/, and the sqlite3 headers and libraries which you can get at http://www.sqlite.org/.

Im using boost build, so if you have that all you have to do is run:

> bjam

Alternativly, as the program now has only a single source file, you can just use g++ to compile and link it.

Ill create a nicer build enviroment one of these days.

Running:

Options must be specified on the commandline or in a config file (key = ["]value["]). Run querylog --help for details. The input file may be ommited, in which case data will be read from stdin until the eof.

Aterm is designed to provide pleasing visual effects, while performing such a mundane function as terminal emulation under X.
Main features:
- fast pseudo-transparency, that does not consume any additional resources.
- optional off-focus fading of text - when aterm looses focus its contents is dimmed.
- NeXT-ish scrollbar
- integration with AfterStep window manager, allowing for aterm looks to be determined by AfterStep theme, and allowing aterm do things like semitransparent gradiented background, JPEG, PNG and other images used as background, and more.
Enhancements:
- This release includes fixes for pasting large (16k) amounts into aterm, the borderless option, and several other issues.

QOF, the Query Object Framework, provides a set of C Language utilities for performing generic structured complex queries on a set of data held by a set of C/C++ objects.
Query Object Framework is unique in that it does NOT require SQL or any database at all to perform the query. Thus, it allows programmers to add query support to their applications without having to hook into an SQL Database.
Typically, if you have an app, and you want to add the ability to show a set of reports, you will need the ability to perform queries in order to get the data you need to show a report.
Of course, you can always write a set of ad-hoc subroutines to return the data that you need. But this kind of a programming style is not extensible: just wait till you get a user who wants a slightly different report.
The idea behind QOF is to provide a generic framework so that any query can be executed, including queries designed by the end-user.
Normally, this is possible only if you use a database that supports SQL, and then only if you deeply embed the database into your application. QOF provides simpler, more natural way to work with objects.
Enhancements:
- This release adds KVP_TYPE_BOOLEAN support, extensible error handling, and new Brazilian Portuguese and Indonesian translations.
- It fixes doxygen support (so that it can be disabled cleanly) and a sqlite error that resulted in spurious temporary files.
- It improves speed in the sqlite backend, packages the .pot file directly, and removes AM_MAINTAINER_MODE.
- QofError is designed for user-friendly messages and supports setting errors and error messages on-the-fly to provide user error messages that are as detailed, relevant, and helpful as possible.

SYNOPSIS

use HTML::TreeBuilder;
use HTML::WikiConverter::Normalizer;

my $tree = new HTML::TreeBuilder();
$tree->parse(

text

);

my $norm = new HTML::WikiConverter::Normalizer();
$norm->normalize($tree);

# Roughly gives "

text

"
print $tree->as_HTML();

HTML::WikiConverter dialects convert HTML into wiki markup. Most (if not all) know nothing about CSS, nor do they take it into consideration when performing html-to-wiki conversion. But there is no good reason for, say, text not to be converted into text in the MediaWiki dialect. The same is true of other dialects, all of which should be able to use CSS information to produce wiki markup.

The issue becomes especially problematic when considering that several WYSIWYG HTML editors (e.g. Mozillas) produce this sort of CSS-heavy HTML. Prior to HTML::WikiConverter::Normalizer, this HTML would have been essentially converted to text, the CSS information having been ignored by HTML::WikiConverter.

HTML::WikiConverter::Normalizer avoids this with a few simple transformations that convert CSS styles into HTML tags.

Primrose is a database connection pool which supports all databases that have JDBC drivers.
It provides control over SQL transaction monitoring, configuration, and dynamic pool management via a Web interface.
Main features:
- Optional notification of crisis events.
- Highly adaptable configuration file - see the config file for all the options.
- SQL statement monitoring for connections, including what connection is called from what code and the precise SQL it is performing, including ? parameters.
- Starting/Stopping pools without application restarts
- Adding / removing connections on the fly
- Automated retrieval of duff connections
- A web interface for pool management
- Queueing of connection requests during heavy load.
- Statistics for types of SQL statements executed and executiion times, to provide a complete overview of webapp-db interaction
- Multiple pool instances, managed through one interface.
- No more forgotton unclosed Statement and ResultSet objects - primrose closes them for you.
- Easy deployment and integration with your webapp container.
- No need to rewrite your client code to utilise the pool.
- Enhances debug of poor performing client code - if a connection hangs, the precise connection, and the exact SQL it is performing is logged, including what client Java code called it.
Enhancements:
- A bugfix for the waitForConnectionIfDatabaseIsDown and encryptionKeyFile properties.