Free querying software for linux

Be::Query is a Perl module to do a query for a given filesystem.

SYNOPSIS

use Be::Query;
@files = Be::Query::Query($filesystem, $query);

do a Query for a given filesystem

USAGE

@files = Be::Query::Query("/boot", "name=lib*.so");

$filesystem is a path anywhere in the target filesystem; $query is a query construction, of the form attribute op value [connector attribute op value]

Such as (name = fido) || (size >= 500)

OurNet::Query is a Perl module for scriptable queries with template extraction.

SYNOPSIS

use OurNet::Query;

# Set query parameters
my ($query, $hits) = (autrijus, 10);
my @sites = (google, google); # XXX: write more templates!
my %found;

# Generate a new Query object
my $bot = OurNet::Query->new($query, $hits, @sites);

# Perform a query
my $found = $bot->begin(&callback, 30); # Timeout after 30 seconds

print *** . ($found ? $found : No) . match(es) found.;

sub callback {
my %entry = @_;
my $entry = %entry;

unless ($found{$entry{url}}) {
print "*** [$entry->{title}]" .
" ($entry->{score})" .
" - [$entry->{id}]n" .
" URL: [$entry->{url}]n";
}

$found{$entry{url}}++;
}

This module provides an easy interface to perform multiple queries to internet services, and wraps them into your own format at once. The results are processed on-the-fly and are returned via callback functions.

Its interfaces resembles that of WWW::Searchs, but implements it in a different fashion. While WWW::Search relies on additional subclasses to parse returned results, OurNet::Query uses site descriptors for search search engine, which makes it much easier to add new backends.

Site descriptors may be written in XML, Template toolkit format, or the .fmt format from the commercial Inforia Quest product.

Text::Query::BuildSQL is a base class for SQL query builders.

SYNOPSIS

package Text::Query::BuildSQLsqldb;

use Text::Query::BuildSQL;

use vars qw(@ISA);

@ISA = qw(Text::Query::BuildSQL);

Defines all the build_* functions to build a syntax tree. The tree nodes are [ operator scope operand operand... ]. The build_final_expression function translate the syntax tree in a where clause using the resolve method. If the scope of the search is not specified (simple query or advanced query without scope operator), the scope is set to the list of comma separated fields provided by the -fields_searched option. The resulting where clause is placed in the select order provided with the -select option, if any.

SYNTAX TREE

The string enclosed in single quotes must match exactly. The < string > token stands for an arbitrary string. A description enclosed in [something ...] means repeated 0 or N times.

expr: or scope expr [expr ...]
and scope expr [expr ...]
not scope expr
near scope expr_literal expr_literal
forbiden scope expr_literal [expr_literal ...]
mandatory scope expr_literal [expr_literal ...]
optional scope expr_literal [expr_literal ...]
literal scope < string >

expr_literal: literal scope < string >

scope: < string >

METHODS

resolve([], Q1)

Returns a where clause string corresponding to the Q1 syntax tree.

sortplusminus([], Q1)

Translate the mandatory and forbiden syntactic nodes to their boolean equivalents. If it has_relevance returns false and there is at least one mandatory word, the first mandatory word is added to the list of optional words.

has_relevance()

Returns true if relevance ranking is possible, false if not. It is used by the sortplusminus function. Returns false by default.

If relevance ranking is not possible, the semantic of the simple search is slighthly modified. When asking for +a b c it shows all the documents containing a and (b or c).

The normal behaviour is to return all the documents containing a and to sort them to show first those containing (b or c). When relevance ranking is not available the b, c search terms are therefore useless. That is why we decided to change the semantic of the query if no relevance ranking is available.

OPTIONS

-select STRING

If provided the string returned by build_final_expression substitutes the __WHERE__ tag with the where string generated by the resolve function. The substituted string is the return value of the build_final_expression.

If not set the return value of the build_final_expression is the result of the resolve function.

-fields_searched FIELDS_LIST

FIELDS_LIST is a list of comma separated field names. It is used as the default scope if no scope is provided in the query string. The build_final_expression function will croak if this option is not provided and no scope operator were used.

Practical Query Analyzer produces HTML reports on the most frequent queries, slowest queries, queries by type (select/insert/update/delete), and more for both PostgreSQL and MySQL log files.

Network Query Tool is a one-stop solution for obtaining information about a domain name or an IP address.
Instead of manually using a variety of shell commands, or visiting numerous websites to investigate a host, just load Network Query Tool in your browser and enter the hostname or IP. NQT does the rest, as is evidenced by this sample output.
Main features:
- Reverse lookup - resolves an IP address to a hostname (if one exists) or vice versa
- DNS query - aka Dig, requires a dig binary on your system
- Whois (WWW) - gets domain registration information. Now supporting just about every known TLD, gTLD, and ccTLD.
- Whois (IP) - gets IP owner information. Supports all IP blocks maintained by ARIN (US), RIPE (Europe), JPNIC (Japan), APNIC (China/Asia-Pacific), BRNIC (Brazil), LACNIC (Latin America), AFRINIC (Africa), and KRNIC (Korea).
- Check port - Determine whether or not a port on the target host is open. Defaults to port 80.
- Ping - performs a 5-packet ping to the target, requires a ping binary.
- Traceroute - performs a traceroute to the target, requires a traceroute binary.

MySQL Query Browser is a database querying tool.

MySQL Query Browser combines the simplicity of a Web-browser-like interface with powerful features like multiple result sets on tab sheets, query history, storing query "bookmarks", editing and comparing resultsets, SQL script debugging, and more.

MySQL Query Browser is available under the MySQL AB "dual licensing" model. Under this model, users may choose to use MySQL products under the free software/opensource GNU General Public License (commonly known as the "GPL") or under a commercial license.

mbridge provides a multicast DNS services bridge.

mbridge provides a bridge between LANs for multicast-announced services. As an example, you can use it to share iTunes libraries outside of your LAN with your peers.

It works by querying for and listening to announcements for instances of the desired service using the multicast DNS (mDNS) service discovery protocol.

Upon discovery of a new instance, it announces itself as the provider for that service on all the other LANs.

It then acts as a proxy between the clients and the real server.

How It Works

mbridge queries for and listens to announcements for instances of the desired service using the multicast DNS (mDNS) service discovery protocol.

Upon discovery of a new instance, mbridge announces itself as the provider for that service on all the other LANs. It then acts as a proxy between the clients and the real server.

Query-Oriented Model for XML is a lightweight XML processing framework for Java that promotes the use of XPath instead of Java code for consuming XML.

The resulting code from Query-Oriented Model for XML, is simple and expressive with no meaningless objects and no meaningless parameters - just pure business code.

Heres a sample of usage (from a testcase -- heres the used XML document):

public class BigTest extends TestCase {
public static final String[] CONTEXT = {"c urn:catalog", "n urn:name"};

@QUseContext("CONTEXT") // Use the namespace context specified by the CONTEXT field.
public void test() {

InputStream xml = QomTestResources.getTestXml("catalog.xml"); // Get the source.

QLocation root = new QBuilder().build(xml); // Build the root location.

// Test a deep query.
Assert.assertEquals("Harold", root.value("//c:maintainer/n:name[n:first_name = Elliotte]/n:last_name"));


QLocation[] composers = root.locateAll("c:composer"); // Test a multi-query.

Assert.assertEquals(4, composers.length);

String[] names = {"Julie", "Margaret", "Beth", "Linda"};

for (int i = 0; i < composers.length; ++i) {

Assert.assertEquals(names[i], composers[i].value("n:name/n:first_name")); // Test relative queries.

}
}
}