| 1 |
Source: libdbix-dbstag-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Section: perl |
| 4 |
Testsuite: autopkgtest-pkg-perl |
| 5 |
Priority: optional |
| 6 |
Build-Depends: debhelper-compat (= 13) |
| 7 |
Build-Depends-Indep: perl, |
| 8 |
libdata-stag-perl, |
| 9 |
libdbi-perl, |
| 10 |
libdbix-dbschema-perl, |
| 11 |
libparse-recdescent-perl, |
| 12 |
libxml-perl, |
| 13 |
rename |
| 14 |
Standards-Version: 3.9.8 |
| 15 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdbix-dbstag-perl |
| 16 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdbix-dbstag-perl.git |
| 17 |
Homepage: https://metacpan.org/release/DBIx-DBStag |
| 18 |
|
| 19 |
Package: libdbix-dbstag-perl |
| 20 |
Architecture: all |
| 21 |
Depends: ${misc:Depends}, |
| 22 |
${perl:Depends}, |
| 23 |
libdata-stag-perl, |
| 24 |
libdbd-pg-perl, |
| 25 |
libdbi-perl, |
| 26 |
libdbix-dbschema-perl, |
| 27 |
libparse-recdescent-perl, |
| 28 |
libxml-perl |
| 29 |
Description: module providing relational database to hierarchical mapping |
| 30 |
The module DBIx::DBStag is for mapping from databases to Stag objects |
| 31 |
(Structured Tags - see the Data::Stag manpage), which can also be |
| 32 |
represented as XML. It has two main uses: |
| 33 |
. |
| 34 |
Querying |
| 35 |
This module can take the results of any SQL query and decompose the |
| 36 |
flattened results into a tree data structure which reflects the |
| 37 |
foreign keys in the underlying relational schema. It does this by |
| 38 |
looking at the SQL query and introspecting the database schema, |
| 39 |
rather than requiring metadata or an object model. |
| 40 |
. |
| 41 |
In this respect, the module works just like a regular the DBI |
| 42 |
manpage handle, with some extra methods provided. |
| 43 |
. |
| 44 |
Storing Data |
| 45 |
DBStag objects can store any tree-like datastructure (such as XML |
| 46 |
documents) into a database using normalized schema that reflects the |
| 47 |
structure of the tree being stored. This is done using little or no |
| 48 |
metadata. |
| 49 |
. |
| 50 |
XML can also be imported, and a relational schema automatically |
| 51 |
generated. |