Sophie

Sophie

distrib > Mandriva > 2010.0 > i586 > media > contrib-release > by-pkgid > c0b2316b5320756fc35b43f35335d7ce > files > 133

perl-AcePerl-1.920.0-1mdv2010.0.i586.rpm

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Ace - Object-Oriented Access to ACEDB Databases</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body style="background-color: white">


<!-- INDEX BEGIN -->
<div name="index">
<p><a name="__index__"></a></p>
<!--

<ul>

	<li><a href="#name">NAME</a></li>
	<li><a href="#synopsis">SYNOPSIS</a></li>
	<li><a href="#description">DESCRIPTION</a></li>
	<li><a href="#creating_new_database_connections">CREATING NEW DATABASE CONNECTIONS</a></li>
	<ul>

		<li><a href="#connect______multiple_argument_form"><code>connect()</code> - multiple argument form</a></li>
		<li><a href="#connect______single_argument_form"><code>connect()</code> - single argument form</a></li>
		<li><a href="#close___method"><code>close()</code> Method</a></li>
		<li><a href="#reopen___method"><code>reopen()</code> Method</a></li>
	</ul>

	<li><a href="#retrieving_acedb_objects">RETRIEVING ACEDB OBJECTS</a></li>
	<ul>

		<li><a href="#fetch___method"><code>fetch()</code> method</a></li>
		<li><a href="#aql___method"><code>aql()</code> method</a></li>
		<li><a href="#put___method"><code>put()</code> method</a></li>
		<li><a href="#parse___method"><code>parse()</code> method</a></li>
		<li><a href="#parse_longtext___method"><code>parse_longtext()</code> method</a></li>
		<li><a href="#parse_file___method"><code>parse_file()</code> method</a></li>
		<li><a href="#new___method"><code>new()</code> method</a></li>
		<li><a href="#list___method"><code>list()</code> method</a></li>
		<li><a href="#count___method"><code>count()</code> method</a></li>
		<li><a href="#find___method"><code>find()</code> method</a></li>
		<li><a href="#fetch_many___method"><code>fetch_many()</code> method</a></li>
		<li><a href="#find_many___method"><code>find_many()</code> method</a></li>
		<li><a href="#keyset___method"><code>keyset()</code> method</a></li>
		<li><a href="#grep___method"><code>grep()</code> method</a></li>
		<li><a href="#model___method"><code>model()</code> method</a></li>
		<li><a href="#new___method"><code>new()</code> method</a></li>
		<li><a href="#raw_query___method"><code>raw_query()</code> method</a></li>
		<li><a href="#classes___method"><code>classes()</code> method</a></li>
		<li><a href="#class_count___method"><code>class_count()</code> method</a></li>
		<li><a href="#status___method"><code>status()</code> method</a></li>
		<li><a href="#title___method"><code>title()</code> method</a></li>
		<li><a href="#version___method"><code>version()</code> method</a></li>
		<li><a href="#date_style___method"><code>date_style()</code> method</a></li>
		<li><a href="#timestamps___method"><code>timestamps()</code> method</a></li>
		<li><a href="#auto_save__"><code>auto_save()</code></a></li>
		<li><a href="#error___method"><code>error()</code> method</a></li>
		<li><a href="#datetime___and_date__"><code>datetime()</code> and <code>date()</code></a></li>
	</ul>

	<li><a href="#other_methods">OTHER METHODS</a></li>
	<ul>

		<li><a href="#debug__"><code>debug()</code></a></li>
		<li><a href="#name2db__">name2db()</a></li>
		<li><a href="#cache__"><code>cache()</code></a></li>
		<li><a href="#memory_cache_fetch__"><code>memory_cache_fetch()</code></a></li>
		<li><a href="#memory_cache_store__obj_"><code>memory_cache_store($obj)</code></a></li>
		<li><a href="#memory_cache_delete__obj_"><code>memory_cache_delete($obj)</code></a></li>
		<li><a href="#memory_cache_clear__"><code>memory_cache_clear()</code></a></li>
		<li><a href="#file_cache_fetch__"><code>file_cache_fetch()</code></a></li>
		<li><a href="#file_cache_store__obj_"><code>file_cache_store($obj)</code></a></li>
		<li><a href="#file_cache_delete__obj_"><code>file_cache_delete($obj)</code></a></li>
	</ul>

	<li><a href="#the_low_level_c_api">THE LOW LEVEL C API</a></li>
	<li><a href="#bugs">BUGS</a></li>
	<li><a href="#see_also">SEE ALSO</a></li>
	<li><a href="#author">AUTHOR</a></li>
</ul>

-->


</div>
<!-- INDEX END -->

<p>
</p>
<h1><a name="name">NAME</a></h1>
<p>Ace - Object-Oriented Access to ACEDB Databases</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
<pre>
    use Ace;
    # open a remote database connection
    $db = Ace-&gt;connect(-host =&gt; 'beta.crbm.cnrs-mop.fr',
                       -port =&gt; 20000100);</pre>
<pre>
    # open a local database connection
    $local = Ace-&gt;connect(-path=&gt;'~acedb/my_ace');</pre>
<pre>
    # simple queries
    $sequence  = $db-&gt;fetch(Sequence =&gt; 'D12345');
    $count     = $db-&gt;count(Sequence =&gt; 'D*');
    @sequences = $db-&gt;fetch(Sequence =&gt; 'D*');
    $i         = $db-&gt;fetch_many(Sequence=&gt;'*');  # fetch a cursor
    while ($obj = $i-&gt;next) {
       print $obj-&gt;asTable;
    }</pre>
<pre>
    # complex queries
    $query = &lt;&lt;END;
    find Annotation Ready_for_submission ; follow gene ; 
    follow derived_sequence ; &gt;DNA
    END
    @ready_dnas= $db-&gt;fetch(-query=&gt;$query);</pre>
<pre>
    $ready = $db-&gt;fetch_many(-query=&gt;$query);
    while ($obj = $ready-&gt;next) {
        # do something with obj
    }</pre>
<pre>
    # database cut and paste
    $sequence = $db-&gt;fetch(Sequence =&gt; 'D12345');
    $local_db-&gt;put($sequence);
    @sequences = $db-&gt;fetch(Sequence =&gt; 'D*');
    $local_db-&gt;put(@sequences);</pre>
<pre>
    # Get errors
    print Ace-&gt;error;
    print $db-&gt;error;</pre>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>AcePerl provides an interface to the ACEDB object-oriented database.
Both read and write access is provided, and ACE objects are returned
as similarly-structured Perl objects.  Multiple databases can be
opened simultaneously.</p>
<p>You will interact with several Perl classes: <em>Ace</em>, <em>Ace::Object</em>,
<em>Ace::Iterator</em>, <em>Ace::Model</em>.  <em>Ace</em> is the database accessor, and
can be used to open both remote Ace databases (running aceserver or
gifaceserver), and local ones.</p>
<p><em>Ace::Object</em> is the superclass for all objects returned from the
database.  <em>Ace</em> and <em>Ace::Object</em> are linked: if you retrieve an
Ace::Object from a particular database, it will store a reference to
the database and use it to fetch any subobjects contained within it.
You may make changes to the <em>Ace::Object</em> and have those changes
written into the database.  You may also create <em>Ace::Object</em>s from
scratch and store them in the database.</p>
<p><em>Ace::Iterator</em> is a utility class that acts as a database cursor for
long-running ACEDB queries.  <em>Ace::Model</em> provides object-oriented
access to ACEDB's schema.</p>
<p>Internally, <em>Ace</em> uses the <em>Ace::Local</em> class for access to local
databases and <em>Ace::AceDB</em> for access to remote databases.
Ordinarily you will not need to interact directly with either of these
classes.</p>
<p>
</p>
<hr />
<h1><a name="creating_new_database_connections">CREATING NEW DATABASE CONNECTIONS</a></h1>
<p>
</p>
<h2><a name="connect______multiple_argument_form"><code>connect()</code> -- multiple argument form</a></h2>
<pre>
    # remote database
    $db = Ace-&gt;connect(-host  =&gt;  'beta.crbm.cnrs-mop.fr',
                       -port  =&gt;  20000100);</pre>
<pre>
    # local (non-server) database
    $db = Ace-&gt;connect(-path  =&gt;  '/usr/local/acedb);</pre>
<p>Use Ace::connect() to establish a connection to a networked or local
AceDB database.  To establish a connection to an AceDB server, use the
<strong>-host</strong> and/or <strong>-port</strong> arguments.  For a local server, use the
<strong>-port</strong> argument.  The database must be up and running on the
indicated host and port prior to connecting to an AceDB server.  The
full syntax is as follows:</p>
<pre>
    $db = Ace-&gt;connect(-host  =&gt;  $host,
                       -port  =&gt;  $port,
                       -path  =&gt;  $database_path,
                       -program     =&gt; $local_connection_program
                       -classmapper =&gt;  $object_class,
                       -timeout     =&gt; $timeout,
                       -query_timeout =&gt; $query_timeout
                       -cache        =&gt; {cache parameters},
                      );</pre>
<p>The <code>connect()</code> method uses a named argument calling style, and
recognizes the following arguments:</p>
<dl>
<dt><strong><a name="host_port" class="item"><strong>-host</strong>, <strong>-port</strong></a></strong>

<dd>
<p>These arguments point to the host and port of an AceDB server.
AcePerl will use its internal compiled code to establish a connection
to the server unless explicitly overridden with the <strong>-program</strong>
argument.</p>
</dd>
</li>
<dt><strong><a name="path" class="item"><strong>-path</strong></a></strong>

<dd>
<p>This argument indicates the path of an AceDB directory on the local
system.  It should point to the directory that contains the <em>wspec</em>
subdirectory.  User name interpolations (~acedb) are OK.</p>
</dd>
</li>
<dt><strong><a name="user" class="item"><strong>-user</strong></a></strong>

<dd>
<p>Name of user to log in as (when using socket server <strong>only</strong>).  If not
provided, will attempt an anonymous login.</p>
</dd>
</li>
<dt><strong><a name="pass" class="item"><strong>-pass</strong></a></strong>

<dd>
<p>Password to log in with (when using socket server).</p>
</dd>
</li>
<dt><strong><a name="url" class="item"><strong>-url</strong></a></strong>

<dd>
<p>An Acedb URL that combines the server type, host, port, user and
password in a single string.  See the <code>connect()</code> method's &quot;single
argument form&quot; description.</p>
</dd>
</li>
<dt><strong><a name="cache" class="item"><strong>-cache</strong></a></strong>

<dd>
<p>AcePerl can use the Cache::SizeAwareFileCache module to cache objects
to disk. This can result in dramatically increased performance in
environments such as web servers in which the same Acedb objects are
frequently reused.  To activate this mechanism, the
Cache::SizeAwareFileCache module must be installed, and you must pass
the -cache argument during the <code>connect()</code> call.</p>
</dd>
<dd>
<p>The value of -cache is a hash reference containing the arguments to be
passed to Cache::SizeAwareFileCache.  For example:</p>
</dd>
<dd>
<pre>
   -cache =&gt; {
              cache_root         =&gt; '/usr/tmp/acedb',
              cache_depth        =&gt; 4,
              default_expires_in =&gt; '1 hour'
              }</pre>
</dd>
<dd>
<p>If not otherwise specified, the following cache parameters are assumed:</p>
</dd>
<dd>
<pre>
       Parameter               Default Value
       ---------               -------------
       namespace               Server URL (e.g. sace://localhost:2005)
       cache_root              /tmp/FileCache (dependent on system temp directory)
       default_expires_in      1 day
       auto_purge_interval     12 hours</pre>
</dd>
<dd>
<p>By default, the cache is not size limited (the &quot;max_size&quot; property is
set to $NO_MAX_SIZE).  To adjust the size you may consider calling the
Ace object's <a href="#cache"><code>cache()</code></a> method to retrieve the physical cache and then
calling the cache object's <code>limit_size($max_size)</code> method from time to
time.  See <a href="/AcePerl/docs/Cache/SizeAwareFileCache.html">the Cache::SizeAwareFileCache manpage</a> for more details.</p>
</dd>
</li>
<dt><strong><a name="program" class="item"><strong>-program</strong></a></strong>

<dd>
<p>By default AcePerl will use its internal compiled code calls to
establish a connection to Ace servers, and will launch a <em>tace</em>
subprocess to communicate with local Ace databases.  The <strong>-program</strong>
argument allows you to customize this behavior by forcing AcePerl to
use a local program to communicate with the database.  This argument
should point to an executable on your system.  You may use either a
complete path or a bare command name, in which case the PATH
environment variable will be consulted.  For example, you could force
AcePerl to use the <em>aceclient</em> program to connect to the remote host
by connecting this way:</p>
</dd>
<dd>
<pre>
  $db = Ace-&gt;connect(-host =&gt; 'beta.crbm.cnrs-mop.fr',
                     -port =&gt; 20000100,
                     -program=&gt;'aceclient');</pre>
</dd>
</li>
<dt><strong><a name="classmapper" class="item"><strong>-classmapper</strong></a></strong>

<dd>
<p>The optional <strong>-classmapper</strong> argument (alias <strong>-class</strong>) points to the
class you would like to return from database queries.  It is provided
for your use if you subclass Ace::Object.  For example, if you have
created a subclass of Ace::Object called Ace::Object::Graphics, you
can have the database return this subclass by default by connecting
this way:</p>
</dd>
<dd>
<pre>
  $db = Ace-&gt;connect(-host =&gt; 'beta.crbm.cnrs-mop.fr',
                     -port =&gt; 20000100,
                     -class=&gt;'Ace::Object::Graphics');</pre>
</dd>
<dd>
<p>The value of <strong>-class</strong> can be a hash reference consisting of AceDB
class names as keys and Perl class names as values.  If a class name
does not exist in the hash, a key named _DEFAULT_ will be looked for.
If that does not exist, then Ace will default to Ace::Object.</p>
</dd>
<dd>
<p>The value of <strong>-class</strong> can also be an object or a classname that
implements a <code>class_for()</code> method.  This method will receive three
arguments containing the AceDB class name, object ID and database
handle.  It should return a string indicating the perl class to
create.</p>
</dd>
</li>
<dt><strong><a name="timeout" class="item"><strong>-timeout</strong></a></strong>

<dd>
<p>If no response from the server is received within $timeout seconds,
the call will return an undefined value.  Internally timeout sets an
alarm and temporarily intercepts the ALRM signal.  You should be aware
of this if you use ALRM for your own purposes.</p>
</dd>
<dd>
<p>NOTE: this feature is temporarily disabled (as of version 1.40)
because it is generating unpredictable results when used with
Apache/mod_perl.</p>
</dd>
</li>
<dt><strong><a name="query_timeout" class="item"><strong>-query_timeout</strong></a></strong>

<dd>
<p>If any query takes longer than $query_timeout seconds, will return an
undefined value.  This value can only be set at connect time, and cannot
be changed once set.</p>
</dd>
</li>
</dl>
<p>If arguments are omitted, they will default to the following values:</p>
<pre>
    -host          localhost
    -port          200005;
    -path          no default
    -program       tace
    -class         Ace::Object
    -timeout       25
    -query_timeout 120</pre>
<p>If you prefer to use a more Smalltalk-like message-passing syntax, you
can open a connection this way too:</p>
<pre>
  $db = connect Ace -host=&gt;'beta.crbm.cnrs-mop.fr',-port=&gt;20000100;</pre>
<p>The return value is an Ace handle to use to access the database, or
undef if the connection fails.  If the connection fails, an error
message can be retrieved by calling Ace-&gt;error.</p>
<p>You may check the status of a connection at any time with <code>ping()</code>.  It
will return a true value if the database is still connected.  Note
that Ace will timeout clients that have been inactive for any length
of time.  Long-running clients should attempt to reestablish their 
connection if <code>ping()</code> returns false.</p>
<pre>
    $db-&gt;ping() || die &quot;not connected&quot;;</pre>
<p>You may perform low-level calls using the Ace client C API by calling
<code>db()</code>.  This fetches an Ace::AceDB object.  See THE LOW LEVEL C API for
details on using this object.</p>
<pre>

    $low_level = $db-&gt;db();</pre>
<p>
</p>
<h2><a name="connect______single_argument_form"><code>connect()</code> -- single argument form</a></h2>
<pre>
  $db = Ace-&gt;connect('sace://stein.cshl.org:1880')</pre>
<p>Ace-&gt;<code>connect()</code> also accepts a single argument form using a URL-type
syntax.  The general syntax is:</p>
<pre>
   protocol://hostname:port/path</pre>
<p>The <em>:port</em> and <em>/path</em> parts are protocol-dependent as described
above.</p>
<p>Protocols:</p>
<dl>
<dt><strong><a name="sace_hostname_port" class="item"><a href="sace://hostname:port">sace://hostname:port</a></a></strong>

<dd>
<p>Connect to a socket server at the indicated hostname and port.  Example:</p>
</dd>
<dd>
<pre>
   sace://stein.cshl.org:1880</pre>
</dd>
<dd>
<p>If not provided, the port defaults to 2005.</p>
</dd>
</li>
<dt><strong><a name="rpcace_hostname_port" class="item"><a href="rpcace://hostname:port">rpcace://hostname:port</a></a></strong>

<dd>
<p>Connect to an RPC server at the indicated hostname and RPC service number.  Example:</p>
</dd>
<dd>
<pre>
  rpcace://stein.cshl.org:400000</pre>
</dd>
<dd>
<p>If not provided, the port defaults to 200005</p>
</dd>
</li>
<dt><strong><a name="tace_path_to_database" class="item">tace:/path/to/database</a></strong>

<dd>
<p>Open up the local database at <em class="file">/path/to/database</em> using tace.  Example:</p>
</dd>
<dd>
<pre>
  tace:/~acedb/elegans</pre>
</dd>
</li>
<dt><strong><a name="path_to_database" class="item">/path/to/database</a></strong>

<dd>
<p>Same as the previous.</p>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="close___method"><code>close()</code> Method</a></h2>
<p>You can explicitly close a database by calling its <code>close()</code> method:</p>
<pre>
   $db-&gt;close();</pre>
<p>This is not ordinarily necessary because the database will be
automatically close when it -- and all objects retrieved from it -- go
out of scope.</p>
<p>
</p>
<h2><a name="reopen___method"><code>reopen()</code> Method</a></h2>
<p>The ACeDB socket server can time out.  The <code>reopen()</code> method will ping
the server and if it is not answering will reopen the connection.  If
the database is live (or could be resurrected), this method returns
true.</p>
<p>
</p>
<hr />
<h1><a name="retrieving_acedb_objects">RETRIEVING ACEDB OBJECTS</a></h1>
<p>Once you have established a connection and have an Ace databaes
handle, several methods can be used to query the ACE database to
retrieve objects.  You can then explore the objects, retrieve specific
fields from them, or update them using the <em>Ace::Object</em> methods.
Please see <a href="/AcePerl/docs/./Ace/Object.html">the Ace::Object manpage</a>.</p>
<p>
</p>
<h2><a name="fetch___method"><code>fetch()</code> method</a></h2>
<pre>
    $count   = $db-&gt;fetch($class,$name_pattern);
    $object  = $db-&gt;fetch($class,$name);
    @objects = $db-&gt;fetch($class,$name_pattern,[$count,$offset]);
    @objects = $db-&gt;fetch(-name=&gt;$name_pattern,
                          -class=&gt;$class
                          -count=&gt;$count,
                          -offset=&gt;$offset,
                          -fill=&gt;$fill,
                          -filltag=&gt;$tag,
                          -total=&gt;\$total);
    @objects = $db-&gt;fetch(-query=&gt;$query);</pre>
<p>Ace::fetch() retrieves objects from the database based on their class
and name.  You may retrieve a single object by requesting its name, or
a group of objects by fetching a name <em>pattern</em>.  A pattern contains
one or more wildcard characters, where &quot;*&quot; stands for zero or more
characters, and &quot;?&quot; stands for any single character.</p>
<p>This method behaves differently depending on whether it is called in a
scalar or a list context, and whether it is asked to search for a name
pattern or a simple name.</p>
<p>When called with a class and a simple name, it returns the object
referenced by that time, or undef, if no such object exists.  In an
array context, it will return an empty list.</p>
<p>When called with a class and a name pattern in a list context, <code>fetch()</code>
returns the list of objects that match the name.  When called with a
pattern in a scalar context, <code>fetch()</code> returns the <em>number</em> of objects
that match without actually retrieving them from the database.  Thus,
it is similar to <code>count()</code>.</p>
<p>In the examples below, the first line of code will fetch the Sequence
object whose database ID is <em>D12345</em>.  The second line will retrieve
all objects matching the pattern <em>D1234*</em>.  The third line will
return the count of objects that match the same pattern.</p>
<pre>
   $object =  $db-&gt;fetch(Sequence =&gt; 'D12345');
   @objects = $db-&gt;fetch(Sequence =&gt; 'D1234*');
   $cnt =     $db-&gt;fetch(Sequence =&gt;'D1234*');</pre>
<p>A variety of communications and database errors may occur while
processing the request.  When this happens, undef or an empty list
will be returned, and a string describing the error can be retrieved
by calling Ace-&gt;error.</p>
<p>When retrieving database objects, it is possible to retrieve a
&quot;filled&quot; or an &quot;unfilled&quot; object.  A filled object contains the entire
contents of the object, including all tags and subtags.  In the case
of certain Sequence objects, this may be a significant amount of data.
Unfilled objects consist just of the object name.  They are filled in
from the database a little bit at a time as tags are requested.  By
default, <code>fetch()</code> returns the unfilled object.  This is usually a
performance win, but if you know in advance that you will be needing
the full contents of the retrieved object (for example, to display
them in a tree browser) it can be more efficient to fetch them in
filled mode. You do this by calling <code>fetch()</code> with the argument of
<strong>-fill</strong> set to a true value.</p>
<p>The <strong>-filltag</strong> argument, if provided, asks the database to fill in
the subtree anchored at the indicated tag.  This will improve
performance for frequently-accessed subtrees.  For example:</p>
<pre>
   @objects = $db-&gt;fetch(-name    =&gt; 'D123*',
                         -class   =&gt; 'Sequence',
                         -filltag =&gt; 'Visible');</pre>
<p>This will fetch all Sequences named D123* and fill in their Visible
trees in a single operation.</p>
<p>Other arguments in the named parameter calling form are <strong>-count</strong>, to
retrieve a certain maximum number of objects, and <strong>-offset</strong>, to
retrieve objects beginning at the indicated offset into the list.  If
you want to limit the number of objects returned, but wish to learn
how many objects might have been retrieved, pass a reference to a
scalar variable in the <strong>-total</strong> argument.  This will return the
object count.  This example shows how to fetch 100 Sequence
objects, starting at Sequence number 500:</p>
<pre>
  @some_sequences = $db-&gt;fetch('Sequence','*',100,500);</pre>
<p>The next example uses the named argument form to fetch 100 Sequence
objects starting at Sequence number 500, and leave the total number of
Sequences in $total:</p>
<pre>
  @some_sequences = $db-&gt;fetch(-class  =&gt; 'Sequence',
                               -count  =&gt; 100,
                               -offset =&gt; 500,
                               -total  =&gt; \$total);</pre>
<p>Notice that if you leave out the <strong>-name</strong> argument the &quot;*&quot; wildcard is 
assumed.</p>
<p>You may also pass an arbitrary Ace query string with the <strong>-query</strong>
argument.  This will supersede any name and class you provide.
Example:</p>
<pre>
  @ready_dnas= $db-&gt;fetch(-query=&gt;
      'find Annotation Ready_for_submission ; follow gene ; 
       follow derived_sequence ; &gt;DNA');</pre>
<p>If your request is likely to retrieve very many objects, <code>fetch()</code> many
consume a lot of memory, even if <strong>-fill</strong> is false.  Consider using
<strong>fetch_many()</strong> instead (see below).  Also see the <a href="#get"><code>get()</code></a> method, which
is equivalent to the simple two-argument form of <code>fetch()</code>.</p>
<dl>
<dt><strong><a name="get" class="item"><code>get()</code> method</a></strong>

<dd>
<pre>
   $object = $db-&gt;get($class,$name [,$fill]);</pre>
</dd>
<dd>
<p>The <a href="#get"><code>get()</code></a> method will return one and only one AceDB object
identified by its class and name.  The optional $fill argument can be
used to control how much data is retrieved from the database. If $fill
is absent or undefined, then the method will return a lightweight
&quot;stub&quot; object that is filled with information as requested in a lazy
fashion. If $fill is the number &quot;1&quot; then the retrieved object contains
all the relevant information contained within the database.  Any other
true value of $fill will be treated as a tag name: the returned object
will be prefilled with the subtree to the right of that tag.</p>
</dd>
<dd>
<p>Examples:</p>
</dd>
<dd>
<pre>
   # return lightweight stub for Author object &quot;Sulston JE.&quot;
   $author = $db-&gt;get(Author=&gt;'Sulston JE');</pre>
</dd>
<dd>
<pre>
   # return heavyweight object
   $author = $db-&gt;get(Author=&gt;'Sulston JE',1);</pre>
</dd>
<dd>
<pre>
   # return object containing the Address subtree
   $author = $db-&gt;get(Author=&gt;'Sulston JE','Address');</pre>
</dd>
<dd>
<p>The <a href="#get"><code>get()</code></a> method is equivalent to this form of the <code>fetch()</code>
method:</p>
</dd>
<dd>
<pre>
   $object = $db-&gt;fetch($class=&gt;$name);</pre>
</dd>
</dl>
<p>
</p>
<h2><a name="aql___method"><code>aql()</code> method</a></h2>
<pre>
    $count   = $db-&gt;aql($aql_query);
    @objects = $db-&gt;aql($aql_query);</pre>
<p>Ace::aql() will perform an AQL query on the database.  In a scalar
context it returns the number of rows returned.  In an array context
it returns a list of rows.  Each row is an anonymous array containing
the columns returned by the query as an Ace::Object.</p>
<p>If an AQL error is encountered, will return undef or an empty list and
set Ace-&gt;error to the error message.</p>
<p>Note that this routine is not optimized -- there is no iterator
defined.  All results are returned synchronously, leading to large
memory consumption for certain queries.</p>
<p>
</p>
<h2><a name="put___method"><code>put()</code> method</a></h2>
<pre>
   $cnt = $db-&gt;put($obj1,$obj2,$obj3);</pre>
<p>This method will put the list of objects into the database,
overwriting like-named objects if they are already there.  This can
be used to copy an object from one database to another, provided that
the models are compatible.</p>
<p>The method returns the count of objects successfully written into the
database.  In case of an error, processing will stop at the last
object successfully written and an error message will be placed in
Ace-&gt;<a href="#error"><code>error()</code></a>;</p>
<p>
</p>
<h2><a name="parse___method"><code>parse()</code> method</a></h2>
<pre>
  $object = $db-&gt;parse('data to parse');</pre>
<p>This will parse the Ace tags contained within the &quot;data to parse&quot;
string, convert it into an object in the databse, and return the
resulting Ace::Object.  In case of a parse error, the undefined value
will be returned and a (hopefully informative) description of the
error will be returned by Ace-&gt;<a href="#error"><code>error()</code></a>.</p>
<p>For example:</p>
<pre>
  $author = $db-&gt;parse(&lt;&lt;END);
  Author : &quot;Glimitz JR&quot;
  Full_name &quot;Jonathan R. Glimitz&quot;
  Mail  &quot;128 Boylston Street&quot;
  Mail  &quot;Boston, MA&quot;
  Mail  &quot;USA&quot;
  Laboratory GM
  END</pre>
<p>This method can also be used to parse several objects, but only the
last object successfully parsed will be returned.</p>
<p>
</p>
<h2><a name="parse_longtext___method"><code>parse_longtext()</code> method</a></h2>
<pre>
  $object = $db-&gt;parse($title,$text);</pre>
<p>This will parse the long text (which may contain carriage returns and
other funny characters) and place it into the database with the given
title.  In case of a parse error, the undefined value will be returned
and a (hopefully informative) description of the error will be
returned by Ace-&gt;<a href="#error"><code>error()</code></a>; otherwise, a LongText object will be returned.</p>
<p>For example:</p>
<pre>
  $author = $db-&gt;parse_longtext('A Novel Inhibitory Domain',&lt;&lt;END);
  We have discovered a novel inhibitory domain that inhibits
  many classes of proteases, including metallothioproteins.
  This inhibitory domain appears in three different gene families studied
  to date...
  END</pre>
<p>
</p>
<h2><a name="parse_file___method"><code>parse_file()</code> method</a></h2>
<pre>
  @objects = $db-&gt;parse_file('/path/to/file');
  @objects = $db-&gt;parse_file('/path/to/file',1);</pre>
<p>This will call <code>parse()</code> to parse each of the objects found in the
indicated .ace file, returning the list of objects successfully loaded
into the database.</p>
<p>By default, parsing will stop at the first object that causes a parse
error.  If you wish to forge on after an error, pass a true value as
the second argument to this method.</p>
<p>Any parse error messages are accumulated in Ace-&gt;<a href="#error"><code>error()</code></a>.</p>
<p>
</p>
<h2><a name="new___method"><a href="#new"><code>new()</code></a> method</a></h2>
<pre>
  $object = $db-&gt;new($class =&gt; $name);</pre>
<p>This method creates a new object in the database of type $class and
name $name.  If successful, it returns the newly-created object.
Otherwise it returns undef and sets $db-&gt;<a href="#error"><code>error()</code></a>.</p>
<p>$name may contain sprintf()-style patterns.  If one of the patterns is
%d (or a variant), Acedb uses a class-specific unique numbering to return
a unique name.  For example:</p>
<pre>
  $paper = $db-&gt;new(Paper =&gt; 'wgb%06d');</pre>
<p>The object is created in the database atomically.  There is no chance to rollback as there is
in Ace::Object's object editing methods.</p>
<p>See also the Ace::Object-&gt;<code>add()</code> and <code>replace()</code> methods.</p>
<p>
</p>
<h2><a name="list___method"><code>list()</code> method</a></h2>
<pre>
    @objects = $db-&gt;list(class,pattern,[count,offset]);
    @objects = $db-&gt;list(-class=&gt;$class,
                         -name=&gt;$name_pattern,
                         -count=&gt;$count,
                         -offset=&gt;$offset);</pre>
<p>This is a deprecated method.  Use <code>fetch()</code> instead.</p>
<p>
</p>
<h2><a name="count___method"><code>count()</code> method</a></h2>
<pre>
    $count = $db-&gt;count($class,$pattern);
    $count = $db-&gt;count(-query=&gt;$query);</pre>
<p>This function queries the database for a list of objects matching the
specified class and pattern, and returns the object count.  For large
sets of objects this is much more time and memory effective than
fetching the entire list.</p>
<p>The class and name pattern are the same as the <code>list()</code> method above.</p>
<p>You may also provide a <strong>-query</strong> argument to instead specify an
arbitrary ACE query such as &quot;find Author COUNT Paper &gt; 80&quot;.  See
<code>find()</code> below.</p>
<p>
</p>
<h2><a name="find___method"><code>find()</code> method</a></h2>
<pre>
    @objects = $db-&gt;find($query_string);
    @objects = $db-&gt;find(-query =&gt; $query_string,
                         -offset=&gt; $offset,
                         -count =&gt; $count
                         -fill  =&gt; $fill);</pre>
<p>This allows you to pass arbitrary Ace query strings to the server and
retrieve all objects that are returned as a result.  For example, this
code fragment retrieves all papers written by Jean and Danielle
Thierry-Mieg.</p>
<pre>
    @papers = $db-&gt;find('author IS &quot;Thierry-Mieg *&quot; ; &gt;Paper');</pre>
<p>You can find the full query syntax reference guide plus multiple
examples at <a href="http://probe.nalusda.gov:8000/acedocs/index.html#query.">http://probe.nalusda.gov:8000/acedocs/index.html#query.</a></p>
<p>In the named parameter calling form, <strong>-count</strong>, <strong>-offset</strong>, and
<strong>-fill</strong> have the same meanings as in <strong>fetch()</strong>.</p>
<p>
</p>
<h2><a name="fetch_many___method"><code>fetch_many()</code> method</a></h2>
<pre>
    $obj = $db-&gt;fetch_many($class,$pattern);</pre>
<pre>
    $obj = $db-&gt;fetch_many(-class=&gt;$class,
                           -name =&gt;$pattern,
                           -fill =&gt;$filled,
                           -chunksize=&gt;$chunksize);</pre>
<pre>
    $obj = $db-&gt;fetch_many(-query=&gt;$query);</pre>
<p>If you expect to retrieve many objects, you can fetch an iterator
across the data set.  This is friendly both in terms of network
bandwidth and memory consumption.  It is simple to use:</p>
<pre>
    $i = $db-&gt;fetch_many(Sequence,'*');  # all sequences!!!!
    while ($obj = $i-&gt;next) {
       print $obj-&gt;asTable;
    }</pre>
<p>The iterator will return undef when it has finished iterating, and
cannot be used again.  You can have multiple iterators open at once
and they will operate independently of each other.</p>
<p>Like <strong>fetch()</strong>, <strong>fetch_many()</strong> takes an optional <strong>-fill</strong> (or
<strong>-filled</strong>) argument which retrieves the entire object rather than
just its name.  This is efficient on a network with high latency if 
you expect to be touching many parts of the object (rather than
just retrieving the value of a few tags).</p>
<p><strong>fetch_many()</strong> retrieves objects from the database in groups of a
certain maximum size, 40 by default.  This can be tuned using the
optional <strong>-chunksize</strong> argument.  Chunksize is only a hint to the
database.  It may return fewer objects per transaction, particularly
if the objects are large.</p>
<p>You may provide raw Ace query string with the <strong>-query</strong> argument.  If
present the <strong>-name</strong> and <strong>-class</strong> arguments will be ignored.</p>
<p>
</p>
<h2><a name="find_many___method"><code>find_many()</code> method</a></h2>
<p>This is an alias for <code>fetch_many()</code>.  It is now deprecated.</p>
<p>
</p>
<h2><a name="keyset___method"><code>keyset()</code> method</a></h2>
<pre>
    @objects = $db-&gt;keyset($keyset_name);</pre>
<p>This method returns all objects in a named keyset.  Wildcard
characters are accepted, in which case all keysets that match the
pattern will be retrieved and merged into a single list of unique
objects.</p>
<p>
</p>
<h2><a name="grep___method"><code>grep()</code> method</a></h2>
<pre>
    @objects = $db-&gt;grep($grep_string);
    $count   = $db-&gt;grep($grep_string);
    @objects = $db-&gt;grep(-pattern =&gt; $grep_string,
                         -offset=&gt; $offset,
                         -count =&gt; $count,
                         -fill  =&gt; $fill,
                         -filltag =&gt; $filltag,
                         -total =&gt; \$total,
                         -long  =&gt; 1,
                        );</pre>
<p>This performs a &quot;grep&quot; on the database, returning all object names or
text that contain the indicated grep pattern.  In a scalar context
this call will return the number of matching objects.  In an array
context, the list of matching objects are retrieved.  There is also a
named-parameter form of the call, which allows you to specify the
number of objects to retrieve, the offset from the beginning of the
list to retrieve from, whether the retrieved objects should be filled
initially.  You can use <strong>-total</strong> to discover the total number of
objects that match, while only retrieving a portion of the list.</p>
<p>By default, grep uses a fast search that only examines class names and
lexiques.  By providing a true value to the <strong>-long</strong> parameter, you
can search inside LongText and other places that are not usually
touched on, at the expense of much more CPU time.</p>
<p>Due to &quot;not listable&quot; objects that may match during grep, the list of
objects one can retrieve may not always match the count.</p>
<p>
</p>
<h2><a name="model___method"><code>model()</code> method</a></h2>
<pre>
  $model = $db-&gt;model('Author');</pre>
<p>This will return an <em>Ace::Model</em> object corresponding to the
indicated class.</p>
<p>
</p>
<h2><a name="new___method"><a href="#new"><code>new()</code></a> method</a></h2>
<pre>
   $obj = $db-&gt;new($class,$name);
   $obj = $db-&gt;new(-class=&gt;$class,
                   -name=&gt;$name);</pre>
<p>Create a new object in the database with the indicated class and name
and return a pointer to it.  Will return undef if the object already
exists in the database.  The object isn't actually written into the database
until you call Ace::Object::commit().</p>
<p>
</p>
<h2><a name="raw_query___method"><code>raw_query()</code> method</a></h2>
<pre>
    $r = $db-&gt;raw_query('Model');</pre>
<p>Send a command to the database and return its unprocessed output.
This method is necessary to gain access to features that are not yet
implemented in this module, such as model browsing and complex
queries.</p>
<p>
</p>
<h2><a name="classes___method"><code>classes()</code> method</a></h2>
<pre>
   @classes = $db-&gt;classes();
   @all_classes = $db-&gt;classes(1);</pre>
<p>This method returns a list of all the object classes known to the
server.  In a list context it returns an array of class names.  In a
scalar context, it the number of classes defined in the database.</p>
<p>Ordinarily <em>classes()</em> will return only those classes that are
exposed to the user interface for browsing, the so-called &quot;visible&quot;
classes.  Pass a true argument to the call to retrieve non-visible
classes as well.</p>
<p>
</p>
<h2><a name="class_count___method"><code>class_count()</code> method</a></h2>
<pre>
   %classes = $db-&gt;class_count()</pre>
<p>This returns a hash in which the keys are the class names and the
values are the total number of objects in that class.  All classes
are returned, including invisible ones.  Use this method if you need
to count all classes simultaneously.  If you only want to count one
or two classes, it may be more efficient to call <em>count($class_name)</em>
instead.</p>
<p>This method transiently uses a lot of memory.  It should not be used
with Ace 4.5 servers, as they contain a memory leak in the counting
routine.</p>
<p>
</p>
<h2><a name="status___method"><a href="#status"><code>status()</code></a> method</a></h2>
<pre>
    %status = $db-&gt;status;
    $status = $db-&gt;status;</pre>
<p>Returns various bits of status information from the server.  In an
array context, returns a hash of hashes.  In a scalar context, returns a
reference to a hash of hashes.  Keys and subkeys are as follows</p>
<pre>
   code
           program     name of acedb binary
           version     version of acedb binary
           build       build date of acedb binary in format Jan 25 2003 16:21:24</pre>
<pre>
   database
           title       name of the database
           version     version of the database
           dbformat    database format version number
           directory   directory in which the database is stored
           session     session number
           user        user under which server is running
           write       whether the server has write access
           address     global address - not known if this is useful</pre>
<pre>
   resources
           classes     number of classes defined
           keys        number of keys defined
           memory      amount of memory used by acedb objects (bytes)</pre>
<p>For example, to get the program version:</p>
<pre>
   my $version = $db-&gt;status-&gt;{code}{version};</pre>
<p>
</p>
<h2><a name="title___method"><code>title()</code> method</a></h2>
<pre>
    my $title = $db-&gt;title</pre>
<p>Returns the version of the current database, equivalent
to $db-&gt;status-&gt;{database}{title};</p>
<p>
</p>
<h2><a name="version___method"><code>version()</code> method</a></h2>
<pre>
    my $version = $db-&gt;version;</pre>
<p>Returns the version of the current database, equivalent 
to $db-&gt;status-&gt;{database}{version};</p>
<p>
</p>
<h2><a name="date_style___method"><code>date_style()</code> method</a></h2>
<pre>
  $style = $db-&gt;date_style();
  $style = $db-&gt;date_style('ace');
  $style = $db-&gt;date_style('java');</pre>
<p>For historical reasons, AceDB can display dates using either of two
different formats.  The first format, which I call &quot;ace&quot; style, puts
the year first, as in &quot;1997-10-01&quot;.  The second format, which I call
&quot;java&quot; style, puts the day first, as in &quot;01 Oct 1997 00:00:00&quot; (this
is also the style recommended for Internet dates).  The default is to
use the latter notation.</p>
<p><strong>date_style()</strong> can be used to set or retrieve the current style.
Called with no arguments, it returns the current style, which will be
one of &quot;ace&quot; or &quot;java.&quot;  Called with an argument, it will set the
style to one or the other.</p>
<p>
</p>
<h2><a name="timestamps___method"><code>timestamps()</code> method</a></h2>
<pre>
  $timestamps_on = $db-&gt;timestamps();
  $db-&gt;timestamps(1);</pre>
<p>Whenever a data object is updated, AceDB records the time and date of
the update, and the user ID it was running under.  Ordinarily, the
retrieval of timestamp information is suppressed to conserve memory
and bandwidth.  To turn on timestamps, call the <strong>timestamps()</strong> method 
with a true value.  You can retrieve the current value of the setting
by calling the method with no arguments.</p>
<p>Note that activating timestamps disables some of the speed
optimizations in AcePerl.  Thus they should only be activated if you
really need the information.</p>
<p>
</p>
<h2><a name="auto_save__"><code>auto_save()</code></a></h2>
<p>Sets or queries the <em>auto_save</em> variable.  If true, the &quot;save&quot;
command will be issued automatically before the connection to the
database is severed.  The default is true.</p>
<p>Examples:</p>
<pre>
   $db-&gt;auto_save(1);
   $flag = $db-&gt;auto_save;</pre>
<p>
</p>
<h2><a name="error___method"><a href="#error"><code>error()</code></a> method</a></h2>
<pre>
    Ace-&gt;error;</pre>
<p>This returns the last error message.  Like UNIX errno, this variable
is not reset between calls, so its contents are only valid after a
method call has returned a result value indicating a failure.</p>
<p>For your convenience, you can call <a href="#error"><code>error()</code></a> in any of several ways:</p>
<pre>
    print Ace-&gt;error();
    print $db-&gt;error();  # $db is an Ace database handle
    print $obj-&gt;error(); # $object is an Ace::Object</pre>
<p>There's also a global named $Ace::Error that you are free to use.</p>
<p>
</p>
<h2><a name="datetime___and_date__"><code>datetime()</code> and <code>date()</code></a></h2>
<pre>
  $datetime = Ace-&gt;datetime($time);
  $today    = Ace-&gt;datetime();
  $date     = Ace-&gt;date($time);
  $today    = Ace-&gt;date([$time]);</pre>
<p>These convenience functions convert the UNIX timestamp given by $time
(seconds since the epoch) into a datetime string in the format that
ACEDB requires.  <code>date()</code> will truncate the time portion.</p>
<p>If not provided, $time defaults to <code>localtime()</code>.</p>
<p>
</p>
<hr />
<h1><a name="other_methods">OTHER METHODS</a></h1>
<p>
</p>
<h2><a name="debug__"><code>debug()</code></a></h2>
<pre>
  $debug_level = Ace-&gt;debug([$new_level])</pre>
<p>This class method gets or sets the debug level.  Higher integers
increase verbosity.  0 or undef turns off debug messages.</p>
<p>
</p>
<h2><a name="name2db__">name2db()</a></h2>
<pre>
 $db = Ace-&gt;name2db($name [,$database])</pre>
<p>This class method associates a database URL with an Ace database
object. This is used internally by the Ace::Object class in order to
discover what database they &quot;belong&quot; to.</p>
<p>
</p>
<h2><a name="cache__"><a href="#cache"><code>cache()</code></a></a></h2>
<p>Get or set the Cache::SizeAwareFileCache object, if one has been
created.</p>
<p>
</p>
<h2><a name="memory_cache_fetch__"><code>memory_cache_fetch()</code></a></h2>
<pre>
  $obj = $db-&gt;memory_cache_fetch($class,$name)</pre>
<p>Given an object class and name return a copy of the object from the
in-memory cache.  The object will only be cached if a copy of the
object already exists in memory space.  This is ordinarily called
internally.</p>
<p>
</p>
<h2><a name="memory_cache_store__obj_"><code>memory_cache_store($obj)</code></a></h2>
<p>Store an object into the memory cache.  This is ordinarily called
internally.</p>
<p>
</p>
<h2><a name="memory_cache_delete__obj_"><code>memory_cache_delete($obj)</code></a></h2>
<p>Delete an object from the memory cache. This is ordinarily called
internally.</p>
<p>
</p>
<h2><a name="memory_cache_clear__"><code>memory_cache_clear()</code></a></h2>
<p>Completely clears the memory cache.</p>
<p>
</p>
<h2><a name="file_cache_fetch__"><code>file_cache_fetch()</code></a></h2>
<pre>
  $obj = $db-&gt;file_cache_fetch($class,$name)</pre>
<p>Given an object class and name return a copy of the object from the
file cache.  This is ordinarily called internally.</p>
<p>
</p>
<h2><a name="file_cache_store__obj_"><code>file_cache_store($obj)</code></a></h2>
<p>Store an object into the file cache.  This is ordinarily called
internally.</p>
<p>
</p>
<h2><a name="file_cache_delete__obj_"><code>file_cache_delete($obj)</code></a></h2>
<p>Delete an object from the file cache.  This is ordinarily called
internally.</p>
<p>
</p>
<hr />
<h1><a name="the_low_level_c_api">THE LOW LEVEL C API</a></h1>
<p>Internally Ace.pm makes C-language calls to libace to send query
strings to the server and to retrieve the results.  The class that
exports the low-level calls is named Ace::AceDB.</p>
<p>The following methods are available in Ace::AceDB:</p>
<dl>
<dt><strong><a name="new" class="item"><code>new($host,$port,$query_timeout)</code></a></strong>

<dd>
<p>Connect to the host $host at port $port. Queries will time out after
$query_timeout seconds.  If timeout is not specified, it defaults to
120 (two minutes).</p>
</dd>
<dd>
<p>If successful, this call returns an Ace::AceDB connection object.
Otherwise, it returns undef.  Example:</p>
</dd>
<dd>
<pre>
  $acedb = Ace::AceDB-&gt;new('localhost',200005,5) 
           || die &quot;Couldn't connect&quot;;</pre>
</dd>
<dd>
<p>The Ace::AceDB object can also be accessed from the high-level Ace
interface by calling the ACE::db() method:</p>
</dd>
<dd>
<pre>
  $db = Ace-&gt;new(-host=&gt;'localhost',-port=&gt;200005);
  $acedb = $db-&gt;db();</pre>
</dd>
</li>
<dt><strong><a name="query" class="item"><code>query($request)</code></a></strong>

<dd>
<p>Send the query string $request to the server and return a true value
if successful.  You must then call <a href="#read"><code>read()</code></a> repeatedly in order to fetch
the query result.</p>
</dd>
</li>
<dt><strong><a name="read" class="item"><code>read()</code></a></strong>

<dd>
<p>Read the result from the last query sent to the server and return it
as a string.  ACE may return the result in pieces, breaking between
whole objects.  You may need to read repeatedly in order to fetch the
entire result.  Canonical example:</p>
</dd>
<dd>
<pre>
  $acedb-&gt;query(&quot;find Sequence D*&quot;);
  die &quot;Got an error &quot;,$acedb-&gt;error() if $acedb-&gt;status == STATUS_ERROR;
  while ($acedb-&gt;status == STATUS_PENDING) {
     $result .= $acedb-&gt;read;
  }</pre>
</dd>
</li>
<dt><strong><a name="status" class="item"><code>status()</code></a></strong>

<dd>
<p>Return the status code from the last operation.  Status codes are
exported by default when you <strong>use</strong> Ace.pm.  The status codes you may
see are:</p>
</dd>
<dd>
<pre>
  STATUS_WAITING    The server is waiting for a query.
  STATUS_PENDING    A query has been sent and Ace is waiting for
                    you to read() the result.
  STATUS_ERROR      A communications or syntax error has occurred</pre>
</dd>
</li>
<dt><strong><a name="error" class="item"><code>error()</code></a></strong>

<dd>
<p>Returns a more detailed error code supplied by the Ace server.  Check
this value when STATUS_ERROR has been returned.  These constants are
also exported by default.  Possible values:</p>
</dd>
<dd>
<pre>
 ACE_INVALID
 ACE_OUTOFCONTEXT
 ACE_SYNTAXERROR
 ACE_UNRECOGNIZED</pre>
</dd>
<dd>
<p>Please see the ace client library documentation for a full description
of these error codes and their significance.</p>
</dd>
</li>
<dt><strong><a name="encore" class="item"><code>encore()</code></a></strong>

<dd>
<p>This method may return true after you have performed one or more
<a href="#read"><code>read()</code></a> operations, and indicates that there is more data to read.  You
will not ordinarily have to call this method.</p>
</dd>
</li>
</dl>
<p>
</p>
<hr />
<h1><a name="bugs">BUGS</a></h1>
<p>1. The ACE model should be consulted prior to updating the database.</p>
<p>2. There is no automatic recovery from connection errors.</p>
<p>3. Debugging has only one level of verbosity, despite the best
of intentions.</p>
<p>4. Performance is poor when fetching big objects, because of 
many object references that must be created.  This could be
improved.</p>
<p>5. When called in an array context at(&quot;tag[0]&quot;) should return the
current tag's entire column.  It returns the current subtree instead.</p>
<p>6. There is no way to add comments to objects.</p>
<p>7. When timestamps are active, many optimizations are disabled.</p>
<p>8. Item number eight is still missing.</p>
<p>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
<p><a href="/AcePerl/docs/./Ace/Object.html">the Ace::Object manpage</a>, <a href="/AcePerl/docs/./Ace/Local.html">the Ace::Local manpage</a>, <a href="/AcePerl/docs/./Ace/Model.html">the Ace::Model manpage</a>,
<a href="/AcePerl/docs/./Ace/Sequence.html">the Ace::Sequence manpage</a>,<a href="/AcePerl/docs/./Ace/Sequence/Multi.html">the Ace::Sequence::Multi manpage</a>.</p>
<p>
</p>
<hr />
<h1><a name="author">AUTHOR</a></h1>
<p>Lincoln Stein &lt;<a href="mailto:lstein@cshl.org">lstein@cshl.org</a>&gt; with extensive help from Jean
Thierry-Mieg &lt;<a href="mailto:mieg@kaa.crbm.cnrs-mop.fr">mieg@kaa.crbm.cnrs-mop.fr</a>&gt;</p>
<p>Copyright (c) 1997-1998 Cold Spring Harbor Laboratory</p>
<p>This library is free software; you can redistribute it and/or modify
it under the same terms as Perl itself.  See DISCLAIMER.txt for
disclaimers of warranty.</p>

</body>

</html>