Free no limit records software for linux

XML::Records is a Perl module for perlish record-oriented interface to XML.

SYNOPSIS

use XML::Records;
my $p=XML::Records->new(data.lst);
$p->set_records(credit,debit);
my ($t,$r)
while ( (($t,$r)=$p->get_record()) && $t) {
my $amt=$r->{Amount};
if ($t eq debit) {
...
}
}

XML::Records provides a single interface for processing XML data on a stream-oriented, tree-oriented, or record-oriented basis. A subclass of XML::TokeParser, it adds methods to read "records" and tree fragments from XML documents.

In many documents, the immediate children of the root element form a sequence of identically-named and independent elements such as log entries, transactions, etc., each of which consists of "field" child elements or attributes. You can access each such "record" as a simple Perl hash.

You can also read any element and its children into a lightweight tree implemented as a Perl hash, or feed the contents of any element and its children into a SAX handler (making it possible to process "records" with modules like XML::DOM or XML::XPath).

DBIx::Recordset is a Perl extension for DBI recordsets.

SYNOPSIS

use DBIx::Recordset;

# Setup a new object and select some recods...
*set = DBIx::Recordset -> Search ({!DataSource => dbi:Oracle:....,
!Table => users,
$where => name = ? and age > ?,
$values => [richter, 25] }) ;

# Get the values of field foo ...
print "First Records value of foo is $set[0]{foo}n" ;
print "Second Records value of foo is $set[1]{foo}n" ;
# Get the value of the field age of the current record ...
print "Age is $set{age}n" ;

# Do another select with the already created object...
$set -> Search ({name => bar}) ;

# Show the result...
print "All users with name bar:n" ;
while ($rec = $set -> Next)
{
print $rec -> {age} ;
}

# Setup another object and insert a new record
*set2 = DBIx::Recordset -> Insert ({!DataSource => dbi:Oracle:....,
!Table => users,
name => foo,
age => 25 }) ;


# Update this record (change age from 25 to 99)...
$set -> Update ({age => 99}, {name => foo}) ;

DBIx::Recordset is a perl module for abstraction and simplification of database access.

The goal is to make standard database access (select/insert/update/delete) easier to handle and independend of the underlying DBMS. Special attention is made on web applications to make it possible to handle the state-less access and to process the posted data of formfields, but DBIx::Recordset is not limited to web applications.

DBIx::Recordset uses the DBI API to access the database, so it should work with every database for which a DBD driver is available (see also DBIx::Compat).
Most public functions take a hash reference as parameter, which makes it simple to supply various different arguments to the same function. The parameter hash can also be taken from a hash containing posted formfields like those available with CGI.pm, mod_perl, HTML::Embperl and others.
Before using a recordset it is necessary to setup an object. Of course the setup step can be made with the same function call as the first database access, but it can also be handled separately.

Most functions which set up an object return a typglob. A typglob in Perl is an object which holds pointers to all datatypes with the same name. Therefore a typglob must always have a name and cant be declared with my. You can only use it as global variable or declare it with local. The trick for using a typglob is that setup functions can return a reference to an object, an array and a hash at the same time.

The object is used to access the objects methods, the array is used to access the records currently selected in the recordset and the hash is used to access the current record.

If you dont like the idea of using typglobs you can also set up the object, array and hash separately, or just set the ones you need.

cpulimit is a simple program that attempts to limit the cpu usage of a process (expressed in percentage, not in cpu time). This is useful to control batch jobs, when you dont want they eat too much cpu.

cpulimit project does not act on the nice value or other scheduling priority stuff, but on the real cpu usage. Also, it is able to adapt itself to the overall system load, dynamically and quickly.

EnsEMBL::Web::Record is a family of modules used for managing a users persistant data in a database.

SYNOPSIS

Many web sites now encourage users to register and login to access more advanced features, and to customise a site to their needs.

The EnsEMBL::Web::Record group of Perl modules is design to manage any arbitrary type of user created data in an SQL database. This module follows the Active Record design pattern, in that each new instantiated Record object represents a single row of a database.

That object can be manipulated programatically, and any changes made can be stored in the database with a single record->save function call.

Because arbitrary Perl data structures can be stored in this manner, EnsEMBL::Web::Record allows user preferences to be easily saved, and allows developers to implement new featurs quickly.

This module was first used (and has been abstracted from) the Ensembl genome browser (http://www.ensembl.org).

New user data can be added to the database:

use EnsEMBL::Web::Record;

my $bookmark = EnsEMBL::Web::Record->new();
$bookmark->url(http://www.ensembl.org);
$bookmark->name(Ensembl);
$bookmark->save;
...

The Record can be associated with an user id:

$record->user($id);

The same record can also be removed:

$bookmark->delete;

EnsEMBL::Web::Record also provides a number of methods for getting collections of records from the database, using a field selector.

EnsEMBL::Web::Record::find_bookmarks_by_user_id($id).

Google::Adwords::StatsRecord is a Google Adwords StatsRecord Object.

This object is a read-only object used in returned calls from Google Adwords API.

More info is available here -
http://www.google.com/apis/adwords/developer/StatsRecord.html

METHODS

Accessors (read only)

* averagePosition - The average position of impressions that were shown for this records entity
* clicks - The number of clicks collected by this records entity.
* conversionRate - The ratio of conversions over convertible clicks for this records entity.
* conversions - The number of clicks that were actually converted for this records entity.
* cost - The total cost incurred (in micro-units of currency) by this records entity.
* id - The Id of this records entity
* impressions - The number of impressions shown on behalf of this records entity

LMarbles is an Atomix clone with a slight change in concept. Instead of assembling molecules you create figures out of marbles. Nevertheless, the basic game play is the same: If a marble starts to move it will not stop until it hits a wall or another marble.

To make it more interesting there are obstacles like one-way streets, crumbling walls and portals.

As Marbles is meant as a puzzle game you play against a move limit and not a time limit. This way you have as much time as you need to think.

LPairs is a classical memory game. This means you have to find pairs of identical cards which will then be removed.

Your time and tries needed will be counted but there is no highscore chart or limit to this.