stag-announce — Announcements

[Stag-announce] New releases: DBIx::DBStag-0.03 and Data::Stag-0.04

[Chris M. <cj...@fr...>]

On February 2 2004, version 0.04 of Data::Stag was released

This release provides a lot of new documentation on how to use
parsers/handlers

Added error handler

On April 2 2004, version 0.03 of DBIx::DBStag was released

This release includes SQLTemplates and much more

Enjoy,
Chris

[Stag-announce] Data-Stag-0.04 released

[Chris M. <cj...@fr...>]

Available from CPAN (shortly) or stag.sf.net

[Stag-announce] DBStag initial release

[Chris M. <cj...@fr...>]

DBStag initial release
~~~~~~~~~~~~~~~~~~~~~~

the first release of DBIx::DBStag is available from either CPAN or
sourceforge, see http://stag.sf.net for details. This is timed to
coincide with a much imporved version (0.03) of the Data::Stag module.

DBStag is a perl module for turning the results of SQL queries into
nested tag-value data structures (Stag objects) that reflect the
foreign key relationships of the underlying database.

For instance, given a relational schema with the 1-to-many FK
relationships below,

  gene --------< transcript ----< exon_to_transcript
    |                v                  v
    |                |                  |
    ^                |                  |
  gene_func       protein              exon

a query that does a join over all these tables will return results as
a denormalised relation, that is, a list of records. this is a
difficult datastructure for applications to work with.

DBStag will take the results of that query and will produce nested
structures (which can be represented as perl objects, XML or in a
native Stag format) like this:

 gene
   gene_func
   transcript
     protein
   exon_to_transcript
     exon

or if a different focus is required, like this:

  protein
    transcript
      gene
        gene_func
      exon_to_transcript
        exon

No object model is required - everything is driven by the relational
schema and the contents of the SQL query. Optional guidance can also
be given in choosing the nesting of the tree to be constructed.

Stag objects or XML can also be stored back in a database. DBStag
comes with a script for reverse engineering XML files into relational
schemas.

The module is still alpha quality but it works with most queries and
schemas, and the API should be fairly stable. I test mostly on
PostgreSQL but MySQL seems to work fine.

For more details, see http://stag.sf.net