Module Author: Jeff Zucker <email@example.com>
Excellent tool for developing programs with limited "database" needs, prototyping full-on RDBMS applications and pulling in common data interchange formats. If you don't need /want the SQL baggage, try AnyData instead.
DBD::AnyData is a DBI/SQL wrapper around AnyData which
allows the author to use many SQL constructs on traditionally non-SQL data
sources. Descendant from DBD::RAM, DBD::AnyData also implements
that module's ability to load data from multiple formats and treat them as
if they were SQL tables. This table can be held entirely in memory or tied
to the underlying data file. Tables can also be exported in any format which
the module supports.
The variety and number of file formats in use
is staggeringly large and continues to grow. Perl hackers are often faced
with the job of being syntactic glue between applications, translating output
from one program into the necessary input for another. Abstracting the exact
format of these data allows the programmer to rise above mere hacking and
actually craft something (re)usable. Separating the logic from the
presentation improves the clarity of both.
DBD::AnyData attempts to provide this abstraction by presenting a DBI/SQL
interface. It layers over the required/companion AnyData module, which
presents a tied hash interface. The perl purist will most likely prefer
to stick with AnyData, minus the DBD. The extra layer of abstraction will
be most useful if you are more comfortable with SQL or your application
design requires it. To my mind, the niftiest use of this module is the
ability to prototype your code as if you had a whole relational database,
but have the ease of a few simple CSVs actually holding the data.
The list of supported formats is impressive, and continues to expand. CPAN
- perl data structures and __DATA__ segments
- Delimited text (Comma/Pipe/Tab/Colon/whatever separated)
- Fixed length records
- HTML Tables
- INI Files
- passwd Files
- MP3 Files (specifically, their ID3 tags)
- Paragraph Files
- Web Server Logs
- XML Files
- DBI Connections (to leverage existing modules)
on the way.
DBD::AnyData has three basic modes of operation: file access, in-memory
access and format conversion. These modes are implemented as five extension
methods over a standard DBD.
In file access mode, the data file is read on each request and written
on each change. The entire file is never read into memory (unless requested)
and so this method is suitable for large data files. Be aware that these
are not atomic commits, so your database could end up in an
inconsistent state. This mode is not supported for remote files or
certain formats (DBI, XML, HTMLtable, MP3 or perl ARRAYs).
In-Memory mode loads the entire data source into memory. Obviously a
problem for huge data sets, but then you probably have those in a relational
database already. This method is ideal for querying a remote data source,
handled in the background by good old LWP.
Conversion mode takes data from an input (which can be local or remote,
and in any supported format) and writes it to a local file, perl string or
perl array. This function alone would be reason enough for the module to
exist, and it's really more of an afterthought.
- Again, if you don't need SQL, use AnyData instead
Currently, DBD::AnyData will not allow SQL against multiple
tables in the same SQL statement (no JOINs) Updated: per jZed this feature is now available
- It isn't a real RDBMS. Don't expect atomicity, journals, etc etc
- Not all formats are fully featured, and most require more modules
DBD::AnyData is one of those fun modules that lets you shove the crud
work off on someone else (the author of the AnyData::Format:: module) and
get on with crafting good code. I've found it especially helpful when
putting together tiny web apps that might end up getting huge (and thus
require a moving to a true database). Anything that lets me stop writing
file format converters is worth checking out in my book.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.