libs/Data/README.html

<HTML>
<HEAD>
<TITLE>Data::Storage</TITLE>
<LINK REV="made" HREF="mailto:">
</HEAD>

<BODY>

<A NAME="__index__"></A>
<!-- INDEX BEGIN -->

<UL>

        <LI><A HREF="#name">NAME</A></LI>
        <LI><A HREF="#synopsis">SYNOPSIS</A></LI>
        <UL>

                <LI><A HREF="#note">NOTE</A></LI>
        </UL>

        <LI><A HREF="#description">DESCRIPTION</A></LI>
        <LI><A HREF="#authors / copyright">AUTHORS / COPYRIGHT</A></LI>
        <LI><A HREF="#acknowledgements">ACKNOWLEDGEMENTS</A></LI>
        <LI><A HREF="#support / warranty">SUPPORT / WARRANTY</A></LI>
        <LI><A HREF="#todo">TODO</A></LI>
        <UL>

                <LI><A HREF="#handle the following errors/cases:">Handle the following errors/cases:</A></LI>
                <UL>

                        <LI><A HREF="#dbierror [tangram]: dbd::mysql::st execute failed: unknown column 't1.requestdump' in 'field list'">``DBI-Error [Tangram]: DBD::mysql::st execute failed: Unknown column 't1.requestdump' in 'field list'''</A></LI>
                        <LI><A HREF="#compare schema (structure diff) with database ...">Compare schema (structure diff) with database ...</A></LI>
                </UL>

                <LI><A HREF="#introduce some features:">Introduce some features:</A></LI>
                <UL>

                        <LI><A HREF="#links:">Links:</A></LI>
                </UL>

        </UL>

</UL>
<!-- INDEX END -->

<HR>
<P>
<H1><A NAME="name">NAME</A></H1>
<P>Data::Storage - Interface for accessing various Storage implementations for Perl in an independent way</P>
<P>
<HR>
<H1><A NAME="synopsis">SYNOPSIS</A></H1>
<PRE>
  ... the basic way:</PRE>
<PRE>
  ... via inheritance:
</PRE>
<PRE>

    use Data::Storage;
    my $proxyObj = new HttpProxy;
    $proxyObj-&gt;{url} = $url;
    $proxyObj-&gt;{payload} = $content;
    $self-&gt;{storage}-&gt;insert($proxyObj);</PRE>
<PRE>

    use Data::Storage;
    my $proxyObj = HttpProxy-&gt;new(
      url =&gt; $url,
      payload =&gt; $content,
    );
    $self-&gt;{storage}-&gt;insert($proxyObj);</PRE>
<P>
<H2><A NAME="note">NOTE</A></H2>
<P>This module heavily relies on DBI and Tangram, but adds a lot of additional bugs and quirks. 
Please look at their documentation and this code for additional information.</P>
<P>
<HR>
<H1><A NAME="description">DESCRIPTION</A></H1>
<P>Data::Storage is module for a accessing various ``data structures'' stored inside
various ``data containers''. It sits on top of DBI and/or Tangram.</P>
<P>
<HR>
<H1><A NAME="authors / copyright">AUTHORS / COPYRIGHT</A></H1>
<P>The Data::Storage module is Copyright (c) 2002 Andreas Motl.
All rights reserved.</P>
<P>You may distribute it under the terms of either the GNU General Public
License or the Artistic License, as specified in the Perl README file.</P>
<P>
<HR>
<H1><A NAME="acknowledgements">ACKNOWLEDGEMENTS</A></H1>
<P>Larry Wall and the <CODE>perl5-porters</CODE> for Perl, 
Tim Bunce for DBI, Jean-Louis Leroy for Tangram and Set::Object, 
Sam Vilain for Class::Tangram.</P>
<P>
<HR>
<H1><A NAME="support / warranty">SUPPORT / WARRANTY</A></H1>
<P>Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.</P>
<P>
<HR>
<H1><A NAME="todo">TODO</A></H1>
<P>
<H2><A NAME="handle the following errors/cases:">Handle the following errors/cases:</A></H2>
<P>
<H3><A NAME="dbierror [tangram]: dbd::mysql::st execute failed: unknown column 't1.requestdump' in 'field list'">``DBI-Error [Tangram]: DBD::mysql::st execute failed: Unknown column 't1.requestdump' in 'field list'''</A></H3>
<PRE>
    ... occours when operating on object-attributes not introduced yet:
    this should be detected and appended/replaced through:
    &quot;Schema-Error detected, maybe (just) an inconsistency. 
    Please check if your declaration in schema-module &quot;a&quot; matches structure in database &quot;b&quot; or try to run&quot;
    db_setup.pl --dbkey=import --action=deploy</PRE>
<P>
<H3><A NAME="compare schema (structure diff) with database ...">Compare schema (structure diff) with database ...</A></H3>
<PRE>
  ... when issuing &quot;db_setup.pl --dbkey=import --action=deploy&quot;
  on a database with an already deployed schema, use an additional &quot;--update&quot; then
  to lift the schema inside the database to the current declared schema.
  You will have to approve removals and changes on field-level while
  new objects and new fields are introduced silently without any interaction needed.
  In future versions there may be additional options to control silent processing of
  removals and changes.
  See this CRUD-table applying to the actions occouring on Classes and Class variables when deploying schemas,
  don't mix this up with CRUD-actions on Objects, these are already handled by (e.g.) Tangram itself.
  Classes:
    C create    -&gt;  yes, handled automatically
    R retrieve  -&gt;  no, not subject of this aspect since it is about deployment only
    U update    -&gt;  yes, automatically for Class meta-attributes, yes/no for Class variables (look at the rules down here)
    D delete    -&gt;  yes, just by user-interaction
  Class variables:
    C create    -&gt;  yes, handled automatically
    R retrieve  -&gt;  no, not subject of this aspect since it is about deployment only
    U update    -&gt;  yes, just by user-interaction; maybe automatically if it can be determined that data wouldn't be lost
    D delete    -&gt;  yes, just by user-interaction
  It's all about not to be able to loose data simply while this is in alpha stage.</PRE>
<P>
<H2><A NAME="introduce some features:">Introduce some features:</A></H2>
<PRE>
  Get this stuff together with UML (Unified Modeling Language) and/or standards from ODMG.
  Make it possible to load/save schemas in XMI (XML Metadata Interchange), 
  which seems to be most commonly used today, perhaps handle objects with OIFML.
  Integrate/bundle this with a web-/html-based UML modeling tool or 
  some other interesting stuff like the &quot;Co-operative UML Editor&quot; from Uni Darmstadt. (web-/java-based)
  Enable Round Trip Engineering. Keep code and diagrams in sync. Don't annoy/bother the programmer.</PRE>
<P>
<H3><A NAME="links:">Links:</A></H3>
<PRE>
    UML 1.3 Spec: <A HREF="http://cgi.omg.org/cgi-bin/doc?ad/99-06-08.pdf">http://cgi.omg.org/cgi-bin/doc?ad/99-06-08.pdf</A>
    XMI 1.1 Spec: <A HREF="http://cgi.omg.org/cgi-bin/doc?ad/99-10-02.pdf">http://cgi.omg.org/cgi-bin/doc?ad/99-10-02.pdf</A>
    XMI 2.0 Spec: <A HREF="http://cgi.omg.org/docs/ad/01-06-12.pdf">http://cgi.omg.org/docs/ad/01-06-12.pdf</A>
    ODMG: <A HREF="http://odmg.org/">http://odmg.org/</A>
    OIFML: <A HREF="http://odmg.org/library/readingroom/oifml.pdf">http://odmg.org/library/readingroom/oifml.pdf</A>
    Co-operative UML Editor: <A HREF="http://www.darmstadt.gmd.de/concert/activities/internal/umledit.html">http://www.darmstadt.gmd.de/concert/activities/internal/umledit.html</A></PRE>
<PRE>
  further readings:
    <A HREF="http://www.google.com/search?q=web+based+uml+editor&amp">http://www.google.com/search?q=web+based+uml+editor&amp</A>;hl=en&amp;lr=&amp;ie=UTF-8&amp;oe=UTF-8&amp;start=10&amp;sa=N
    <A HREF="http://www.fernuni-hagen.de/DVT/Aktuelles/01FHHeidelberg.pdf">http://www.fernuni-hagen.de/DVT/Aktuelles/01FHHeidelberg.pdf</A>
    <A HREF="http://www.enhyper.com/src/documentation/">http://www.enhyper.com/src/documentation/</A>
    <A HREF="http://cis.cs.tu-berlin.de/Dokumente/Diplomarbeiten/2001/skinner.pdf">http://cis.cs.tu-berlin.de/Dokumente/Diplomarbeiten/2001/skinner.pdf</A>
    <A HREF="http://citeseer.nj.nec.com/vilain00diagrammatic.html">http://citeseer.nj.nec.com/vilain00diagrammatic.html</A>
    <A HREF="http://archive.devx.com/uml/articles/Smith01/Smith01-3.asp">http://archive.devx.com/uml/articles/Smith01/Smith01-3.asp</A></PRE>
<PRE>
  maybe useful for / to be integrated with:
    ArapXML: <A HREF="http://xml.coverpages.org/ni2001-09-24-b.html">http://xml.coverpages.org/ni2001-09-24-b.html</A></PRE>

</BODY>

</HTML>
1	joko	1.1	<HTML>
2			<HEAD>
3			<TITLE>Data::Storage</TITLE>
4			<LINK REV="made" HREF="mailto:">
5			</HEAD>
6
7			<BODY>
8
9			<A NAME="__index__"></A>
10			<!-- INDEX BEGIN -->
11
12			<UL>
13
14			<LI><A HREF="#name">NAME</A></LI>
15			<LI><A HREF="#synopsis">SYNOPSIS</A></LI>
16			<UL>
17
18			<LI><A HREF="#note">NOTE</A></LI>
19			</UL>
20
21			<LI><A HREF="#description">DESCRIPTION</A></LI>
22			<LI><A HREF="#authors / copyright">AUTHORS / COPYRIGHT</A></LI>
23			<LI><A HREF="#acknowledgements">ACKNOWLEDGEMENTS</A></LI>
24			<LI><A HREF="#support / warranty">SUPPORT / WARRANTY</A></LI>
25			<LI><A HREF="#todo">TODO</A></LI>
26			<UL>
27
28			<LI><A HREF="#handle the following errors/cases:">Handle the following errors/cases:</A></LI>
29			<UL>
30
31			<LI><A HREF="#dbierror [tangram]: dbd::mysql::st execute failed: unknown column 't1.requestdump' in 'field list'">``DBI-Error [Tangram]: DBD::mysql::st execute failed: Unknown column 't1.requestdump' in 'field list'''</A></LI>
32			<LI><A HREF="#compare schema (structure diff) with database ...">Compare schema (structure diff) with database ...</A></LI>
33			</UL>
34
35			<LI><A HREF="#introduce some features:">Introduce some features:</A></LI>
36			<UL>
37
38			<LI><A HREF="#links:">Links:</A></LI>
39			</UL>
40
41			</UL>
42
43			</UL>
44			<!-- INDEX END -->
45
46			<HR>
47			<P>
48			<H1><A NAME="name">NAME</A></H1>
49			<P>Data::Storage - Interface for accessing various Storage implementations for Perl in an independent way</P>
50			<P>
51			<HR>
52			<H1><A NAME="synopsis">SYNOPSIS</A></H1>
53			<PRE>
54			... the basic way:</PRE>
55			<PRE>
56			... via inheritance:
57			</PRE>
58			<PRE>
59
60			use Data::Storage;
61			my $proxyObj = new HttpProxy;
62			$proxyObj->{url} = $url;
63			$proxyObj->{payload} = $content;
64			$self->{storage}->insert($proxyObj);</PRE>
65			<PRE>
66
67			use Data::Storage;
68			my $proxyObj = HttpProxy->new(
69			url => $url,
70			payload => $content,
71			);
72			$self->{storage}->insert($proxyObj);</PRE>
73			<P>
74			<H2><A NAME="note">NOTE</A></H2>
75			<P>This module heavily relies on DBI and Tangram, but adds a lot of additional bugs and quirks.
76			Please look at their documentation and this code for additional information.</P>
77			<P>
78			<HR>
79			<H1><A NAME="description">DESCRIPTION</A></H1>
80			<P>Data::Storage is module for a accessing various ``data structures'' stored inside
81			various ``data containers''. It sits on top of DBI and/or Tangram.</P>
82			<P>
83			<HR>
84			<H1><A NAME="authors / copyright">AUTHORS / COPYRIGHT</A></H1>
85			<P>The Data::Storage module is Copyright (c) 2002 Andreas Motl.
86			All rights reserved.</P>
87			<P>You may distribute it under the terms of either the GNU General Public
88			License or the Artistic License, as specified in the Perl README file.</P>
89			<P>
90			<HR>
91			<H1><A NAME="acknowledgements">ACKNOWLEDGEMENTS</A></H1>
92			<P>Larry Wall and the <CODE>perl5-porters</CODE> for Perl,
93			Tim Bunce for DBI, Jean-Louis Leroy for Tangram and Set::Object,
94			Sam Vilain for Class::Tangram.</P>
95			<P>
96			<HR>
97			<H1><A NAME="support / warranty">SUPPORT / WARRANTY</A></H1>
98			<P>Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.</P>
99			<P>
100			<HR>
101			<H1><A NAME="todo">TODO</A></H1>
102			<P>
103			<H2><A NAME="handle the following errors/cases:">Handle the following errors/cases:</A></H2>
104			<P>
105			<H3><A NAME="dbierror [tangram]: dbd::mysql::st execute failed: unknown column 't1.requestdump' in 'field list'">``DBI-Error [Tangram]: DBD::mysql::st execute failed: Unknown column 't1.requestdump' in 'field list'''</A></H3>
106			<PRE>
107			... occours when operating on object-attributes not introduced yet:
108			this should be detected and appended/replaced through:
109			"Schema-Error detected, maybe (just) an inconsistency.
110			Please check if your declaration in schema-module "a" matches structure in database "b" or try to run"
111			db_setup.pl --dbkey=import --action=deploy</PRE>
112			<P>
113			<H3><A NAME="compare schema (structure diff) with database ...">Compare schema (structure diff) with database ...</A></H3>
114			<PRE>
115			... when issuing "db_setup.pl --dbkey=import --action=deploy"
116			on a database with an already deployed schema, use an additional "--update" then
117			to lift the schema inside the database to the current declared schema.
118			You will have to approve removals and changes on field-level while
119			new objects and new fields are introduced silently without any interaction needed.
120			In future versions there may be additional options to control silent processing of
121			removals and changes.
122			See this CRUD-table applying to the actions occouring on Classes and Class variables when deploying schemas,
123			don't mix this up with CRUD-actions on Objects, these are already handled by (e.g.) Tangram itself.
124			Classes:
125			C create -> yes, handled automatically
126			R retrieve -> no, not subject of this aspect since it is about deployment only
127			U update -> yes, automatically for Class meta-attributes, yes/no for Class variables (look at the rules down here)
128			D delete -> yes, just by user-interaction
129			Class variables:
130			C create -> yes, handled automatically
131			R retrieve -> no, not subject of this aspect since it is about deployment only
132			U update -> yes, just by user-interaction; maybe automatically if it can be determined that data wouldn't be lost
133			D delete -> yes, just by user-interaction
134			It's all about not to be able to loose data simply while this is in alpha stage.</PRE>
135			<P>
136			<H2><A NAME="introduce some features:">Introduce some features:</A></H2>
137			<PRE>
138			Get this stuff together with UML (Unified Modeling Language) and/or standards from ODMG.
139			Make it possible to load/save schemas in XMI (XML Metadata Interchange),
140			which seems to be most commonly used today, perhaps handle objects with OIFML.
141			Integrate/bundle this with a web-/html-based UML modeling tool or
142			some other interesting stuff like the "Co-operative UML Editor" from Uni Darmstadt. (web-/java-based)
143			Enable Round Trip Engineering. Keep code and diagrams in sync. Don't annoy/bother the programmer.</PRE>
144			<P>
145			<H3><A NAME="links:">Links:</A></H3>
146			<PRE>
147			UML 1.3 Spec: <A HREF="http://cgi.omg.org/cgi-bin/doc?ad/99-06-08.pdf">http://cgi.omg.org/cgi-bin/doc?ad/99-06-08.pdf</A>
148			XMI 1.1 Spec: <A HREF="http://cgi.omg.org/cgi-bin/doc?ad/99-10-02.pdf">http://cgi.omg.org/cgi-bin/doc?ad/99-10-02.pdf</A>
149			XMI 2.0 Spec: <A HREF="http://cgi.omg.org/docs/ad/01-06-12.pdf">http://cgi.omg.org/docs/ad/01-06-12.pdf</A>
150			ODMG: <A HREF="http://odmg.org/">http://odmg.org/</A>
151			OIFML: <A HREF="http://odmg.org/library/readingroom/oifml.pdf">http://odmg.org/library/readingroom/oifml.pdf</A>
152			Co-operative UML Editor: <A HREF="http://www.darmstadt.gmd.de/concert/activities/internal/umledit.html">http://www.darmstadt.gmd.de/concert/activities/internal/umledit.html</A></PRE>
153			<PRE>
154			further readings:
155			<A HREF="http://www.google.com/search?q=web+based+uml+editor&amp">http://www.google.com/search?q=web+based+uml+editor&amp</A>;hl=en&lr=&ie=UTF-8&oe=UTF-8&start=10&sa=N
156			<A HREF="http://www.fernuni-hagen.de/DVT/Aktuelles/01FHHeidelberg.pdf">http://www.fernuni-hagen.de/DVT/Aktuelles/01FHHeidelberg.pdf</A>
157			<A HREF="http://www.enhyper.com/src/documentation/">http://www.enhyper.com/src/documentation/</A>
158			<A HREF="http://cis.cs.tu-berlin.de/Dokumente/Diplomarbeiten/2001/skinner.pdf">http://cis.cs.tu-berlin.de/Dokumente/Diplomarbeiten/2001/skinner.pdf</A>
159			<A HREF="http://citeseer.nj.nec.com/vilain00diagrammatic.html">http://citeseer.nj.nec.com/vilain00diagrammatic.html</A>
160			<A HREF="http://archive.devx.com/uml/articles/Smith01/Smith01-3.asp">http://archive.devx.com/uml/articles/Smith01/Smith01-3.asp</A></PRE>
161			<PRE>
162			maybe useful for / to be integrated with:
163			ArapXML: <A HREF="http://xml.coverpages.org/ni2001-09-24-b.html">http://xml.coverpages.org/ni2001-09-24-b.html</A></PRE>
164
165			</BODY>
166
167			</HTML>
MailToCvsAdmin">MailToCvsAdmin	ViewVC Help
Powered by ViewVC 1.1.26