CAM-SQLObject
view release on metacpan or search on metacpan
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<base href="http://www.clotho.com/code/CAM-SQLObject/index.html">
<title>CAM-SQLObject</title>
<link href="/css/demo.css" rel="stylesheet" type="text/css">
<script language="JavaScript" src="/js/demo.js" type="text/javascript"></script>
<style>
p.desc, td.links, a {
line-height: 17pt;
}
thead tr td {
align: left;
font-weight: bold;
font-style: italic;
}
a {
font-weight: bold;
text-decoration: none;
aborder-bottom: 1px dotted white;
}
a:hover {
font-weight: bold;
text-decoration: underline;
atext-decoration: none;
aborder-bottom: 1px solid white;
}
</style>
</head>
<body>
<div class="title">
<img src="/images/clotho.gif" alt="Clotho Advanced Media, Inc." width="339" height="117" border="0">
</div>
<div class="body">
<p class="title">CAM-SQLObject</p>
<p class="subtitle">Last update: <a href="perl/CAM-SQLObject-1.01-docs">v1.01</a>, 2005-04-22</p>
<p>
Subclasses of CAM:<!-- -->:SQLObject act as delegates for an SQL
infrastructure implemented by CAM:<!-- -->:SQLManager XML files. You name
your SQL queries in the XML files (kind of like stored procedures) and
call them by name from your SQLObject instance. The data retrieved
from or written to the database is reflected in the instance's data
structure. The goal of CAM:<!-- -->:SQLObject is to minimize the amount of
programming needed to build a full-power interface to an SQL data
record.
</p>
<p>
This class is not meant to be instantiated directly. Instead, it is
intended to be the superclass of real database frontend objects.
Those objects may add several get[field] and set[field] routines to
act as accessors and mutators for the database fields. Or, they can
be very thin layers where all of the implementation is done in the SQL
XML file.
</p>
<p>
See CAM:<!-- -->:SQLManager for XML file examples and a DTD.
</p>
<p>
The CPAN module that is most similar to CAM:<!-- -->:SQLObject is Class:<!-- -->:DBI.
The main difference is that CAM:<!-- -->:SQLObject abstracts as much of the
SQL away into external files as possible, while Class:<!-- -->:DBI embraces
the SQL and internalizes it as much as possible.
</p>
<p>
Advantages of CAM:<!-- -->:SQLObject vs. Class:<!-- -->:DBI:
</p>
<p>
* SQL commands are disconnected from the Perl code, allowing
database adjustments without rewriting code.
* Allows complex joins
* Allows Perl field names to be different from SQL column names
* Facilitates testing and benchmarking SQL queries
( run in 2.537 seconds using v1.01-cache-2.11-cpan-39a47a84364 )