dbix version 0.01
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 345
DBIx::Version 0.01
DBIx::Version is a Perl extension for getting database software name and version. more>>
DBIx::Version is a Perl extension for getting database software name and version.
SYNOPSIS
use DBIx::Version;
my $dbh = DBI->connect( ... );
my ($dbname, $dbver, $dbverfull) = DBIx::Version::Version($dbh);
DBIx::Version lets you query which database software and version you are connected to.
Return Examples:
(undef, undef, undef)
(mysql, 4.0.17, 4.0.17-standard-log)
(postgresql, 7.4.1, PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.2 20031107 (Red Hat Linux 3.3.2-2))
(oracle, 8.1.7.0.0, 8.1.7.0.0)
(sqlserver, 8.00.384, Microsoft SQL Server 2000 - 8.00.384 (Intel X86)
May 23 2001 00:02:52
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 2))
(sybase,12.5.0.1,Adaptive Server Enterprise/12.5.0.1/SWR 9982 IR/P/Sun_svr4/OS 5.8/rel12501/1776/ 64-bit/FBO/Tue Feb 26 01:22:10 2002)
(sybase,12.5.0.2,Adaptive Server Enterprise/12.5.0.2/EBF 14000 IR/P/Sun_svr4/OS 5.8/rel12502/1776/64-bit/FBO/Tue Jun 4 01:22:10 2002)
Answer 1: This module is useful for cross-platform coding, and in environments like shared hosting where you actually didnt install the database yourself and are curious.
<<lessSYNOPSIS
use DBIx::Version;
my $dbh = DBI->connect( ... );
my ($dbname, $dbver, $dbverfull) = DBIx::Version::Version($dbh);
DBIx::Version lets you query which database software and version you are connected to.
Return Examples:
(undef, undef, undef)
(mysql, 4.0.17, 4.0.17-standard-log)
(postgresql, 7.4.1, PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.2 20031107 (Red Hat Linux 3.3.2-2))
(oracle, 8.1.7.0.0, 8.1.7.0.0)
(sqlserver, 8.00.384, Microsoft SQL Server 2000 - 8.00.384 (Intel X86)
May 23 2001 00:02:52
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 2))
(sybase,12.5.0.1,Adaptive Server Enterprise/12.5.0.1/SWR 9982 IR/P/Sun_svr4/OS 5.8/rel12501/1776/ 64-bit/FBO/Tue Feb 26 01:22:10 2002)
(sybase,12.5.0.2,Adaptive Server Enterprise/12.5.0.2/EBF 14000 IR/P/Sun_svr4/OS 5.8/rel12502/1776/64-bit/FBO/Tue Jun 4 01:22:10 2002)
Answer 1: This module is useful for cross-platform coding, and in environments like shared hosting where you actually didnt install the database yourself and are curious.
Download (0.003MB)
Added: 2007-01-11 License: Perl Artistic License Price:
1020 downloads
DBIx::Wrapper::Config 0.01
DBIx::Wrapper::Config Perl module allows the use of a configuration file in XML specifying information. more>>
DBIx::Wrapper::Config Perl module allows the use of a configuration file in XML specifying information required to connect to databases using DBIx::Wrapper.
This way, your database connection specifications can be kept in one place.
Each "db" element specifies a key/name for the database connection, which should be passed as the $db_key argument to connect() in order to connect to that database.
The "db" elements children specify the dsn, authentication, and attribute information. dbi:mysql:database=test_db;host=example.com;port=3306 test_user test_pwd test_user test_pwd connect($db_key, $conf_path, %dbix_wrapper_attrs) Return a DBIx::Wrapper object connected to the database specified by $db_key in the file at $conf_path.
%dbix_wrapper_attrs is the optional 5th argument to DBIx::Wrappers connect() method, specifying handlers, etc. The file specified by $conf_path should be in the format specified in the DESCRIPTION section of this document.
Installation:
perl Makefile.PL
make
make test
make install
<<lessThis way, your database connection specifications can be kept in one place.
Each "db" element specifies a key/name for the database connection, which should be passed as the $db_key argument to connect() in order to connect to that database.
The "db" elements children specify the dsn, authentication, and attribute information. dbi:mysql:database=test_db;host=example.com;port=3306 test_user test_pwd test_user test_pwd connect($db_key, $conf_path, %dbix_wrapper_attrs) Return a DBIx::Wrapper object connected to the database specified by $db_key in the file at $conf_path.
%dbix_wrapper_attrs is the optional 5th argument to DBIx::Wrappers connect() method, specifying handlers, etc. The file specified by $conf_path should be in the format specified in the DESCRIPTION section of this document.
Installation:
perl Makefile.PL
make
make test
make install
Download (0.003MB)
Added: 2006-01-31 License: Perl Artistic License Price:
1361 downloads
DBIx::XMLServer 0.02
DBIx::XMLServer is a Perl module to serve data as XML in response to HTTP requests. more>>
DBIx::XMLServer is a Perl module to serve data as XML in response to HTTP requests.
SYNOPSIS
use XML::LibXML;
use DBIx::XMLServer;
my $xml_server = new DBIx::XMLServer($dbh, "template.xml");
my $doc = $xml_server->process($QUERY_STRING);
die "Error: $doc" unless ref $doc;
print "Content-type: application/xmlrnrn";
print $doc->toString(1);
This module implements the whole process of generating an XML document from a database query, in response to an HTTP request. The mapping from the DBI database to an XML structure is defined in a template file, also in XML; this template is used not only to turn the data into XML, but also to parse the query string. To the user, the format of the query string is very natural in relation to the XML data which they will receive.
All the methods of this object can take a hash of named parameters instead of a list of parameters.
One DBIx::XMLServer object can process several queries. The following steps take place in processing a query:
The query string is parsed. It contains search criteria together with other options about the format of the returned data.
The search criteria from the query string are converted, using the XML template, into an SQL SELECT statement.
The results of the SQL query are translated into XML, again using the template, and returned to the caller.
<<lessSYNOPSIS
use XML::LibXML;
use DBIx::XMLServer;
my $xml_server = new DBIx::XMLServer($dbh, "template.xml");
my $doc = $xml_server->process($QUERY_STRING);
die "Error: $doc" unless ref $doc;
print "Content-type: application/xmlrnrn";
print $doc->toString(1);
This module implements the whole process of generating an XML document from a database query, in response to an HTTP request. The mapping from the DBI database to an XML structure is defined in a template file, also in XML; this template is used not only to turn the data into XML, but also to parse the query string. To the user, the format of the query string is very natural in relation to the XML data which they will receive.
All the methods of this object can take a hash of named parameters instead of a list of parameters.
One DBIx::XMLServer object can process several queries. The following steps take place in processing a query:
The query string is parsed. It contains search criteria together with other options about the format of the returned data.
The search criteria from the query string are converted, using the XML template, into an SQL SELECT statement.
The results of the SQL query are translated into XML, again using the template, and returned to the caller.
Download (0.029MB)
Added: 2006-09-12 License: Perl Artistic License Price:
1137 downloads
DBIx::OO 0.0.4
DBIx::OO is a database to Perl objects abstraction. more>>
DBIx::OO is a database to Perl objects abstraction.
SYNOPSIS
package MyDB;
use base DBIx::OO;
# We need to overwrite get_dbh since its an abstract function.
# The way you connect to the DB is really your job; this function
# should return the database handle. The default get_dbh() croaks.
my $dbh;
sub get_dbh {
$dbh = DBI->connect_cached(dbi:mysql:test, user, passwd)
if !defined $dbh;
return $dbh;
}
package MyDB::Users;
use base MyDB;
__PACKAGE__->table(Users);
__PACKAGE__->columns(P => [ id ],
E => [qw/ first_name last_name email /]);
__PACKAGE__->has_many(pages => MyDB::Pages, user);
package MyDB::Pages;
use base MyDB;
__PACKAGE__->table(Pages);
__PACKAGE__->columns(P => [ id ],
E => [qw/ title content user /]);
__PACKAGE__->has_a(user => MyDB::Users);
package main;
my $u = MyDB::Users->create({ id => userid,
first_name => Q,
last_name => W });
my $foo = MyDB::Users->retrieve(userid);
my @p = @{ $foo->fk_pages };
print "User: ", $foo->first_name, " ", $foo->last_name, " pages:n";
foreach (@p) {
print $_->title, "n";
}
$foo->first_name(John);
$foo->last_name(Doe);
# or
$foo->set(first_name => John, last_name => Doe);
$foo->update;
<<lessSYNOPSIS
package MyDB;
use base DBIx::OO;
# We need to overwrite get_dbh since its an abstract function.
# The way you connect to the DB is really your job; this function
# should return the database handle. The default get_dbh() croaks.
my $dbh;
sub get_dbh {
$dbh = DBI->connect_cached(dbi:mysql:test, user, passwd)
if !defined $dbh;
return $dbh;
}
package MyDB::Users;
use base MyDB;
__PACKAGE__->table(Users);
__PACKAGE__->columns(P => [ id ],
E => [qw/ first_name last_name email /]);
__PACKAGE__->has_many(pages => MyDB::Pages, user);
package MyDB::Pages;
use base MyDB;
__PACKAGE__->table(Pages);
__PACKAGE__->columns(P => [ id ],
E => [qw/ title content user /]);
__PACKAGE__->has_a(user => MyDB::Users);
package main;
my $u = MyDB::Users->create({ id => userid,
first_name => Q,
last_name => W });
my $foo = MyDB::Users->retrieve(userid);
my @p = @{ $foo->fk_pages };
print "User: ", $foo->first_name, " ", $foo->last_name, " pages:n";
foreach (@p) {
print $_->title, "n";
}
$foo->first_name(John);
$foo->last_name(Doe);
# or
$foo->set(first_name => John, last_name => Doe);
$foo->update;
Download (0.023MB)
Added: 2007-01-13 License: Perl Artistic License Price:
1014 downloads
DBIx::Perlish 0.27
DBIx::Perlish module provides the ability to work with databases supported by the DBI module. more>>
DBIx::Perlish is a Perl module that provides the ability to work with databases supported by the DBI module using Perls own syntax for four most common operations: SELECT, UPDATE, DELETE, and INSERT.
By using DBIx::Perlish, you can write most of your database queries using a domain-specific language with Perl syntax. Since a Perl programmer knows Perl by definition, and might not know SQL to the same degree, this approach generally leads to a more comprehensible and maintainable code.
The module is not intended to replace 100% of SQL used in your program. There is a hope, however, that it can be used to replace a substantial portion of it.
The DBIx::Perlish module quite intentionally neither implements nor cares about database administration tasks like schema design and management. The plain DBI interface is quite sufficient for that. Similarly, and for the same reason, it does not take care of establishing database connections or handling transactions. All this is outside the scope of this module.
<<lessBy using DBIx::Perlish, you can write most of your database queries using a domain-specific language with Perl syntax. Since a Perl programmer knows Perl by definition, and might not know SQL to the same degree, this approach generally leads to a more comprehensible and maintainable code.
The module is not intended to replace 100% of SQL used in your program. There is a hope, however, that it can be used to replace a substantial portion of it.
The DBIx::Perlish module quite intentionally neither implements nor cares about database administration tasks like schema design and management. The plain DBI interface is quite sufficient for that. Similarly, and for the same reason, it does not take care of establishing database connections or handling transactions. All this is outside the scope of this module.
Download (0.039MB)
Added: 2007-07-12 License: BSD License Price:
834 downloads
DBIx::Timeout 1.01
DBIx::Timeout is a Perl module that provides a safe method of timing out DBI requests. more>>
DBIx::Timeout is a Perl module that provides a safe method of timing out DBI requests.
The method described in the DBI documentation uses unsafe signals, which may cause memory corruption. DBIx::Timeout instead uses a separate timeout process.
The problem with using POSIX sigaction() is that it relies on unsafe signals to work. Unsafe signals are well known to cause instability. For example, imagine your DB client code is in the middle of updating some global state when the signal arrives. That global state could be left in an inconsitent state, just wait for the next time it is needed to cause problems. Since this will likely occur far from the cause, and only ocur rarely, it can be a very difficult problem to track down.
Instead, this module:
- Forks a child process which sleeps for $timeout seconds.
- Runs your long-running query in the parent process.
- If the parent process finishes first it kills the child and returns.
- If the child process wakes up it kills the parents DB thread and exits with a code so the parent knows it was timed out.
NOTE: After this call your database connection may be killed even if no timeout occurred. This is due to a race condition - the child may wake up just as parent process finishes. Patches addressing this bug are welcome. Until this is fixed you should be ready to reconnect after call_with_timeout().
<<lessThe method described in the DBI documentation uses unsafe signals, which may cause memory corruption. DBIx::Timeout instead uses a separate timeout process.
The problem with using POSIX sigaction() is that it relies on unsafe signals to work. Unsafe signals are well known to cause instability. For example, imagine your DB client code is in the middle of updating some global state when the signal arrives. That global state could be left in an inconsitent state, just wait for the next time it is needed to cause problems. Since this will likely occur far from the cause, and only ocur rarely, it can be a very difficult problem to track down.
Instead, this module:
- Forks a child process which sleeps for $timeout seconds.
- Runs your long-running query in the parent process.
- If the parent process finishes first it kills the child and returns.
- If the child process wakes up it kills the parents DB thread and exits with a code so the parent knows it was timed out.
NOTE: After this call your database connection may be killed even if no timeout occurred. This is due to a race condition - the child may wake up just as parent process finishes. Patches addressing this bug are welcome. Until this is fixed you should be ready to reconnect after call_with_timeout().
Download (0.006MB)
Added: 2006-09-22 License: Perl Artistic License Price:
1127 downloads
DBIx::EnumConstraints 0.01
DBIx::EnumConstraints is a Perl module that generates enum-like SQL constraints. more>>
DBIx::EnumConstraints is a Perl module that generates enum-like SQL constraints.
SYNOPSIS
use DBIx::EnumConstraints;
my $ec = DBIx::EnumConstraints->new({
name => kind, fields => [ [ k1, a, b ]
, [ k2, b ] ]
});
# get enum field definition
my $edef = $ec->enum_definition;
# $edef is now kind smallint not null check (kind > 0 and kind < 2)
# get constraints array
my @cons = $ec->constraints;
# @cons is now (
# constraint k1_has_a check (kind 1 or a is not null)
# , constraint k1_has_b check (kind 1 or a is not null)
# , constraint k2_has_b check (kind 2 or b is not null)
# , constraint k2_has_no_a check (kind 2 or a is null))
This module generates SQL statements for enforcing enum semantics on the database columns.
Enum columns is the column which can get one of 1 .. k values. For each of those values there are other columns which should or should not be null.
For example in the SYNOPSIS above, when kind column is 1 the row should have both of a and b columns not null. When kind column is 2 the row should have a but no b columns.
CONSTRUCTORS
$class->new($args)
$args should be HASH reference containing the following parameters:
name
The name of the enum.
fields
Array of arrays describing fields dependent on the enum. Each row is index is the possible value of enum minus 1 (e.g. row number 1 is for enum value 2).
First item in the array is the state name. The rest of the items are field names. There is a possibility to mark optional fields by using trailing ? (e.g. b? denotes an optional b field.
METHODS
$self->enum_definition
Returns the definition of enum column. See SYNOPSIS for example.
$self->for_each_kind($callback)
Runs $callback over registered enum states. For each state passes state name, fields which are in the state and fields which are out of the state.
The fields are passed as ARRAY references.
$self->constraints
Returns the list of generated constraints. See SYNOPSIS above for an example.
<<lessSYNOPSIS
use DBIx::EnumConstraints;
my $ec = DBIx::EnumConstraints->new({
name => kind, fields => [ [ k1, a, b ]
, [ k2, b ] ]
});
# get enum field definition
my $edef = $ec->enum_definition;
# $edef is now kind smallint not null check (kind > 0 and kind < 2)
# get constraints array
my @cons = $ec->constraints;
# @cons is now (
# constraint k1_has_a check (kind 1 or a is not null)
# , constraint k1_has_b check (kind 1 or a is not null)
# , constraint k2_has_b check (kind 2 or b is not null)
# , constraint k2_has_no_a check (kind 2 or a is null))
This module generates SQL statements for enforcing enum semantics on the database columns.
Enum columns is the column which can get one of 1 .. k values. For each of those values there are other columns which should or should not be null.
For example in the SYNOPSIS above, when kind column is 1 the row should have both of a and b columns not null. When kind column is 2 the row should have a but no b columns.
CONSTRUCTORS
$class->new($args)
$args should be HASH reference containing the following parameters:
name
The name of the enum.
fields
Array of arrays describing fields dependent on the enum. Each row is index is the possible value of enum minus 1 (e.g. row number 1 is for enum value 2).
First item in the array is the state name. The rest of the items are field names. There is a possibility to mark optional fields by using trailing ? (e.g. b? denotes an optional b field.
METHODS
$self->enum_definition
Returns the definition of enum column. See SYNOPSIS for example.
$self->for_each_kind($callback)
Runs $callback over registered enum states. For each state passes state name, fields which are in the state and fields which are out of the state.
The fields are passed as ARRAY references.
$self->constraints
Returns the list of generated constraints. See SYNOPSIS above for an example.
Download (0.010MB)
Added: 2007-07-24 License: Perl Artistic License Price:
822 downloads
DBIx::Log4perl 0.09
DBIx::Log4perl is a Perl extension for DBI to selectively log SQL, parameters, result-sets, etc. more>>
DBIx::Log4perl is a Perl extension for DBI to selectively log SQL, parameters, result-sets, transactions etc to a Log::Log4perl handle.
SYNOPSIS
use Log::Log4perl;
use DBIx::Log4perl;
Log::Log4perl->init("/etc/mylog.conf");
my $dbh = DBIx::Log4perl->connect(DBI:odbc:mydsn, $user, $pass);
$dbh->DBI_METHOD(args);
or
use DBIx::Log4perl;
my $dbh = DBIX::Log4perl->connect(DBI:odbc:mydsn, $user, $pass
{DBIx_l4p_init => "/etc/mylog.conf",
DBIx_l4p_class => "My::Package");
$dbh->DBI_METHOD(args);
DBIx::Log4perl is a wrapper over DBI which adds logging of your DBI activity via a Log::Log4perl handle. Log::Log4perl has many advantages for logging but the ones probably most attractive are:
The ability to turn logging on or off or change the logging you see without changing your code.
Different log levels allowing you to separate warnings, errors and fatals to different files.
<<lessSYNOPSIS
use Log::Log4perl;
use DBIx::Log4perl;
Log::Log4perl->init("/etc/mylog.conf");
my $dbh = DBIx::Log4perl->connect(DBI:odbc:mydsn, $user, $pass);
$dbh->DBI_METHOD(args);
or
use DBIx::Log4perl;
my $dbh = DBIX::Log4perl->connect(DBI:odbc:mydsn, $user, $pass
{DBIx_l4p_init => "/etc/mylog.conf",
DBIx_l4p_class => "My::Package");
$dbh->DBI_METHOD(args);
DBIx::Log4perl is a wrapper over DBI which adds logging of your DBI activity via a Log::Log4perl handle. Log::Log4perl has many advantages for logging but the ones probably most attractive are:
The ability to turn logging on or off or change the logging you see without changing your code.
Different log levels allowing you to separate warnings, errors and fatals to different files.
Download (0.017MB)
Added: 2007-07-31 License: Perl Artistic License Price:
815 downloads
pDonkey Server 0.01
pDonkeyS is Perl implementation of an eDonkey server. more>>
pDonkeyS is Perl implementation of an eDonkey server. The main goal of the server is to provide framework for further eDonkey protocol exploration, but it could be useful in testing of client software, since the server can be configured to output very detailed debugging info about eDonkey traffic.
This server was made to provide framework for further eDonkey protocol exploration, but it could be usefull in testing of client software, since the server can be configured to output very detailed debug info about eDonkey traffic.
<<lessThis server was made to provide framework for further eDonkey protocol exploration, but it could be usefull in testing of client software, since the server can be configured to output very detailed debug info about eDonkey traffic.
Download (0.011MB)
Added: 2006-06-20 License: GPL (GNU General Public License) Price:
1228 downloads
Lexi 0.01
Lexi project is a dict client and vocabulary builder. more>>
Lexi project is a dict client and vocabulary builder.
Lexi is a dict client that also serves as a personalized vocabulary builder.
It caches definitions and has a persistent word list.
The interface is structured to be quick and easy and features synonym clicking, drag and drop word queries, and spelling suggestions.
<<lessLexi is a dict client that also serves as a personalized vocabulary builder.
It caches definitions and has a persistent word list.
The interface is structured to be quick and easy and features synonym clicking, drag and drop word queries, and spelling suggestions.
Download (0.025MB)
Added: 2006-10-31 License: GPL (GNU General Public License) Price:
1089 downloads
DBIx::DBStag 0.08
DBIx::DBStag is a Perl module for Relational Database to Hierarchical (Stag/XML) Mapping. more>>
DBIx::DBStag is a Perl module for Relational Database to Hierarchical (Stag/XML) Mapping.
SYNOPSIS
use DBIx::DBStag;
my $dbh = DBIx::DBStag->connect("dbi:Pg:dbname=moviedb");
my $sql = q[
SELECT
studio.*,
movie.*,
star.*
FROM
studio NATURAL JOIN
movie NATURAL JOIN
movie_to_star NATURAL JOIN
star
WHERE
movie.genre = sci-fi AND star.lastname = Fisher
USE NESTING
(set(studio(movie(star))))
];
my $dataset = $dbh->selectall_stag($sql);
my @studios = $dataset->get_studio;
# returns nested data that looks like this -
#
# (studio
# (name "20th C Fox")
# (movie
# (name "star wars") (genre "sci-fi")
# (star
# (firstname "Carrie")(lastname "Fisher")))))
# iterate through result tree -
foreach my $studio (@studios) {
printf "STUDIO: %sn", $studio->get_name;
my @movies = $studio->get_movie;
foreach my $movie (@movies) {
printf " MOVIE: %s (genre:%s)n",
$movie->get_name, $movie->get_genre;
my @stars = $movie->get_star;
foreach my $star (@stars) {
printf " STARRING: %s:%sn",
$star->get_firstname, $star->get_lastname;
}
}
}
# manipulate data then store it back in the database
my @allstars = $dataset->get("movie/studio/star");
$_->set_fullname($_->get_firstname. .$_->get_lastname)
foreach(@allstars);
$dbh->storenode($dataset);
exit 0;
Or from the command line:
unix> selectall_xml.pl -d dbi:Pg:dbname=moviebase
SELECT * FROM studio NATURAL JOIN movie NATURAL
JOIN movie_to_star NATURAL JOIN star
USE NESTING (set(studio(movie(star))))
Or using a predefined template:
unix> selectall_xml.pl -d moviebase /mdb-movie genre=sci-fi
<<lessSYNOPSIS
use DBIx::DBStag;
my $dbh = DBIx::DBStag->connect("dbi:Pg:dbname=moviedb");
my $sql = q[
SELECT
studio.*,
movie.*,
star.*
FROM
studio NATURAL JOIN
movie NATURAL JOIN
movie_to_star NATURAL JOIN
star
WHERE
movie.genre = sci-fi AND star.lastname = Fisher
USE NESTING
(set(studio(movie(star))))
];
my $dataset = $dbh->selectall_stag($sql);
my @studios = $dataset->get_studio;
# returns nested data that looks like this -
#
# (studio
# (name "20th C Fox")
# (movie
# (name "star wars") (genre "sci-fi")
# (star
# (firstname "Carrie")(lastname "Fisher")))))
# iterate through result tree -
foreach my $studio (@studios) {
printf "STUDIO: %sn", $studio->get_name;
my @movies = $studio->get_movie;
foreach my $movie (@movies) {
printf " MOVIE: %s (genre:%s)n",
$movie->get_name, $movie->get_genre;
my @stars = $movie->get_star;
foreach my $star (@stars) {
printf " STARRING: %s:%sn",
$star->get_firstname, $star->get_lastname;
}
}
}
# manipulate data then store it back in the database
my @allstars = $dataset->get("movie/studio/star");
$_->set_fullname($_->get_firstname. .$_->get_lastname)
foreach(@allstars);
$dbh->storenode($dataset);
exit 0;
Or from the command line:
unix> selectall_xml.pl -d dbi:Pg:dbname=moviebase
SELECT * FROM studio NATURAL JOIN movie NATURAL
JOIN movie_to_star NATURAL JOIN star
USE NESTING (set(studio(movie(star))))
Or using a predefined template:
unix> selectall_xml.pl -d moviebase /mdb-movie genre=sci-fi
Download (0.13MB)
Added: 2006-10-04 License: Perl Artistic License Price:
1115 downloads
DBIx::XMLMessage 0.05
DBIx::XMLMessage is a Perl module for XML Message exchange between DBI data sources. more>>
DBIx::XMLMessage is a Perl module for XML Message exchange between DBI data sources.
The package maintains simple XML templates that describe object structure.
The package is capable of generating SQL statements based on these templates and executing them against DBI data sources. After executing the SQL, the package formats the data results into XML strings. E.g. the following simple template
< TEMPLATE NAME=SysLogins TYPE=XML VERSION=1.0 TABLE=syslogins
ACTION=SAVE >
< KEY NAME=suid DATATYPE=NUMERIC PARENT_NAME=OBJECT_ID / >
< COLUMN NAME=LoginId EXPR=suid DATATYPE=NUMERIC / >
< /TEMPLATE >
being executed with key value = 1, will be tranlated into this SQL:
SELECT suid LoginId FROM syslogins where suid = 1
and the result will be formatted into this XML string:
< SysLogins >
< LoginId >1< LoginId >
< /SysLogins >
Inbound messages can be processed according to the same kind of templates and the database is updated accordingly. Templates are capable of defining the SQL operators, plus new SAVE operation which is basically a combination of SELECT and either INSERT or UPDATE depending on whether the record was found by the compound key value or not.
<<lessThe package maintains simple XML templates that describe object structure.
The package is capable of generating SQL statements based on these templates and executing them against DBI data sources. After executing the SQL, the package formats the data results into XML strings. E.g. the following simple template
< TEMPLATE NAME=SysLogins TYPE=XML VERSION=1.0 TABLE=syslogins
ACTION=SAVE >
< KEY NAME=suid DATATYPE=NUMERIC PARENT_NAME=OBJECT_ID / >
< COLUMN NAME=LoginId EXPR=suid DATATYPE=NUMERIC / >
< /TEMPLATE >
being executed with key value = 1, will be tranlated into this SQL:
SELECT suid LoginId FROM syslogins where suid = 1
and the result will be formatted into this XML string:
< SysLogins >
< LoginId >1< LoginId >
< /SysLogins >
Inbound messages can be processed according to the same kind of templates and the database is updated accordingly. Templates are capable of defining the SQL operators, plus new SAVE operation which is basically a combination of SELECT and either INSERT or UPDATE depending on whether the record was found by the compound key value or not.
Download (0.025MB)
Added: 2006-09-15 License: Perl Artistic License Price:
1134 downloads
DBIx::CGITables 0.001
DBIx::CGITables is a Perl module for easy DB access from a CGI. more>>
DBIx::CGITables is a Perl module for easy DB access from a CGI.
SYNOPSIS
use DBIx::CGITables;
my %parameters=();
my $query=DBIx::CGITables->new(%parameters));
$query->search_execute_and_do_everything_even_parse_the_template();
This module is under development - and this version is not tested very well. The documentation might not be completely in sync with the latest changes, and the documentation is not optimized for easy understanding at the moment. Sorry.
DBIx::CGITables is made for making database access through CGIs really easy.
Its completely template-oriented. The templates are in HTML::Template format. Some templates might be set up quickly by using DBIx::CGITables::MakeTemplates; see the doc for this module. Some web designer should fix the templates a bit.
The template approach might make the system a bit "static". Gerald Richter has another approach based upon HTML::Embperl (not published at the time I write this), if youd better like a more dynamic system. Anyway, I find it quite important not to mix HTML and code - the HTML documents should be easy to manipulate by non-technical web editors.
Ideally, HTML and (language-dependent) content should be splitted. I think such things might be done better by using Zope than cgis.
The database handling is done by DBIx::Recordset - this module gets its parametres first from a CGI query, then it might be overridden or completed by a parameter file, and the caller (your .cgi script or whatever) is also free to modify or add parameters.
Im hoping that anybody should get a working (though, probably ugly) CGI interface to any kind of database simply:
1. Run DBIx::CGITables::MakeTemplates (see the pod)
2. Create the script given above at SYNOPSIS
3. Set up the webserver correct.
4. If youre not satisfied with the look, try to edit the html templates.
5. If youre not satisfied with the functionality, try reading the rest of this documentation, and the DBIx::Recordset documentation.
6. If youre still not satisfied with the functionality and/or you find bugs, hack the code and submit the patches to the mailinglist and/or me and/or (if DBIx::Recordset is affected) Gerhard Richter. If youre not a perl hacker, or if you dont have time, send a mail about whats wrong and/or whats missing to the mailinglist anyway. Or privately to me if you dont want to write to a mailinglist.
<<lessSYNOPSIS
use DBIx::CGITables;
my %parameters=();
my $query=DBIx::CGITables->new(%parameters));
$query->search_execute_and_do_everything_even_parse_the_template();
This module is under development - and this version is not tested very well. The documentation might not be completely in sync with the latest changes, and the documentation is not optimized for easy understanding at the moment. Sorry.
DBIx::CGITables is made for making database access through CGIs really easy.
Its completely template-oriented. The templates are in HTML::Template format. Some templates might be set up quickly by using DBIx::CGITables::MakeTemplates; see the doc for this module. Some web designer should fix the templates a bit.
The template approach might make the system a bit "static". Gerald Richter has another approach based upon HTML::Embperl (not published at the time I write this), if youd better like a more dynamic system. Anyway, I find it quite important not to mix HTML and code - the HTML documents should be easy to manipulate by non-technical web editors.
Ideally, HTML and (language-dependent) content should be splitted. I think such things might be done better by using Zope than cgis.
The database handling is done by DBIx::Recordset - this module gets its parametres first from a CGI query, then it might be overridden or completed by a parameter file, and the caller (your .cgi script or whatever) is also free to modify or add parameters.
Im hoping that anybody should get a working (though, probably ugly) CGI interface to any kind of database simply:
1. Run DBIx::CGITables::MakeTemplates (see the pod)
2. Create the script given above at SYNOPSIS
3. Set up the webserver correct.
4. If youre not satisfied with the look, try to edit the html templates.
5. If youre not satisfied with the functionality, try reading the rest of this documentation, and the DBIx::Recordset documentation.
6. If youre still not satisfied with the functionality and/or you find bugs, hack the code and submit the patches to the mailinglist and/or me and/or (if DBIx::Recordset is affected) Gerhard Richter. If youre not a perl hacker, or if you dont have time, send a mail about whats wrong and/or whats missing to the mailinglist anyway. Or privately to me if you dont want to write to a mailinglist.
Download (0.020MB)
Added: 2007-06-19 License: Perl Artistic License Price:
857 downloads
DBIx::Wrapper 0.24
DBIx::Wrapper is a Perl module that serves as a wrapper around DBI. more>>
DBIx::Wrapper library is a Perl module that serves as a wrapper around DBI, providing additional functionality and convenience methods.
Enhancements:
- This release adds convenience methods for generating CSV, XML, and bencoded strings from query results.
- The connect_from_config() method was added in version 0.23, allowing database connection parameters to be specified in a file rather than in your code.
<<lessEnhancements:
- This release adds convenience methods for generating CSV, XML, and bencoded strings from query results.
- The connect_from_config() method was added in version 0.23, allowing database connection parameters to be specified in a file rather than in your code.
Download (0.027MB)
Added: 2006-03-27 License: Perl Artistic License Price:
1307 downloads
Qubit 0.01
Qubit (Qmail Ultimate Backend Integration Tool) is a fully Web-based qmail server configuration and administration suite. more>>
Qubit (Qmail Ultimate Backend Integration Tool) is a fully Web-based qmail server configuration and administration suite.
Qubit project is based on the qmailrules qmail server installation style. It has the same features as other similar tools (like vqadmin and qmailadmin), and it also gives you full control to administer your server with all sorts of features and applications.
<<lessQubit project is based on the qmailrules qmail server installation style. It has the same features as other similar tools (like vqadmin and qmailadmin), and it also gives you full control to administer your server with all sorts of features and applications.
Download (0.038MB)
Added: 2006-02-22 License: GPL (GNU General Public License) Price:
1341 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above dbix version 0.01 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
