libs/Data/README.text

NAME
    Data::Storage - Interface for accessing various Storage implementations
    for Perl in an independent way

SYNOPSIS
      ... the basic way:

      ... via inheritance:
  
        use Data::Storage;
        my $proxyObj = new HttpProxy;
        $proxyObj->{url} = $url;
        $proxyObj->{payload} = $content;
        $self->{storage}->insert($proxyObj);
    
        use Data::Storage;
        my $proxyObj = HttpProxy->new(
          url => $url,
          payload => $content,
        );
        $self->{storage}->insert($proxyObj);

  NOTE

    This module heavily relies on DBI and Tangram, but adds a lot of
    additional bugs and quirks. Please look at their documentation and/or
    this code for additional information.

REQUIREMENTS
    For full functionality: DBI from CPAN Tangram from CPAN Class::Tangram
    from CPAN MySQL::Diff from http://adamspiers.org/computing/mysqldiff/
    ... and all their dependencies

DESCRIPTION
    Data::Storage is module for a accessing various "data structures" stored
    inside various "data containers". It sits on top of DBI and/or Tangram.

AUTHORS / COPYRIGHT
    The Data::Storage module is Copyright (c) 2002 Andreas Motl. All rights
    reserved.

    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.

ACKNOWLEDGEMENTS
    Larry Wall for Perl, Tim Bunce for DBI, Jean-Louis Leroy for Tangram and
    Set::Object, Sam Vilain for Class::Tangram, Adam Spiers for MySQL::Diff
    and all contributors.

SUPPORT / WARRANTY
    Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.

TODO
  Handle the following errors/cases:

   "DBI-Error [Tangram]: DBD::mysql::st execute failed: Unknown column 't1.requestdump' in 'field list'"

        ... occours when operating on object-attributes not introduced yet:
        this should be detected and appended/replaced through:
        "Schema-Error detected, maybe (just) an inconsistency. 
        Please check if your declaration in schema-module "a" matches structure in database "b" or try to run"
        db_setup.pl --dbkey=import --action=deploy

   Compare schema (structure diff) with database ...

      ... when issuing "db_setup.pl --dbkey=import --action=deploy"
      on a database with an already deployed schema, use an additional "--update" 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    ->  yes, handled automatically
        R retrieve  ->  no, not subject of this aspect since it is about deployment only
        U update    ->  yes, automatically for Class meta-attributes, yes/no for Class variables (look at the rules down here)
        D delete    ->  yes, just by user-interaction
      Class variables:
        C create    ->  yes, handled automatically
        R retrieve  ->  no, not subject of this aspect since it is about deployment only
        U update    ->  yes, just by user-interaction; maybe automatically if it can be determined that data wouldn't be lost
        D delete    ->  yes, just by user-interaction
  
      It's all about not to be able to loose data simply while this is in pre-alpha stage.
      And loosing data by being able to modify and redeploy schemas easily is definitely quite easy.
  
      As we can see, creations of Classes and new Class variables is handled 
      automatically and this is believed to be the most common case under normal circumstances.

  Introduce some features:

      - 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 "Co-operative UML Editor" from Uni Darmstadt. (web-/java-based)
      - Enable Round Trip Engineering. Keep code and diagrams in sync. Don't annoy/bother the programmers.
      - Add some more handlers:
        - look at DBD::CSV, Text::CSV, XML::CSV, XML::Excel
      - Add some more locations/locators:
        - PerlDAV: http://www.webdav.org/perldav/
      - Move to t3, use InCASE

   Links:

      Specs:
        UML 1.3 Spec: http://cgi.omg.org/cgi-bin/doc?ad/99-06-08.pdf
        XMI 1.1 Spec: http://cgi.omg.org/cgi-bin/doc?ad/99-10-02.pdf
        XMI 2.0 Spec: http://cgi.omg.org/docs/ad/01-06-12.pdf
        ODMG: http://odmg.org/
        OIFML: http://odmg.org/library/readingroom/oifml.pdf

      CASE Tools:
        Rational Rose (commercial): http://www.rational.com/products/rose/
        Together (commercial): http://www.oi.com/products/controlcenter/index.jsp
        InCASE - Tangram-based Universal Object Editor 
        Sybase PowerDesigner: http://www.sybase.com/powerdesigner
  
      UML Editors:
        Fujaba (free, university): http://www.fujaba.de/
        ArgoUML (free): http://argouml.tigris.org/
        Poseidon (commercial): http://www.gentleware.com/products/poseidonDE.php3
        Co-operative UML Editor (research): http://www.darmstadt.gmd.de/concert/activities/internal/umledit.html
        Metamill (commercial): http://www.metamill.com/
        Violet (university, research, education): http://www.horstmann.com/violet/
        PyUt (free): http://pyut.sourceforge.net/
        (Dia (free): http://www.lysator.liu.se/~alla/dia/)
        UMLet (free, university): http://www.swt.tuwien.ac.at/umlet/index.html
        Voodoo (free): http://voodoo.sourceforge.net/
        Umbrello UML Modeller: http://uml.sourceforge.net/

      UML Tools:
        http://www.objectsbydesign.com/tools/umltools_byPrice.html

      Further readings:
        http://www.google.com/search?q=web+based+uml+editor&hl=en&lr=&ie=UTF-8&oe=UTF-8&start=10&sa=N
        http://www.fernuni-hagen.de/DVT/Aktuelles/01FHHeidelberg.pdf
        http://www.enhyper.com/src/documentation/
        http://cis.cs.tu-berlin.de/Dokumente/Diplomarbeiten/2001/skinner.pdf
        http://citeseer.nj.nec.com/vilain00diagrammatic.html
        http://archive.devx.com/uml/articles/Smith01/Smith01-3.asp

1	joko	1.1	NAME
2			Data::Storage - Interface for accessing various Storage implementations
3			for Perl in an independent way
4
5			SYNOPSIS
6			... the basic way:
7
8			... via inheritance:
9
10			use Data::Storage;
11			my $proxyObj = new HttpProxy;
12			$proxyObj->{url} = $url;
13			$proxyObj->{payload} = $content;
14			$self->{storage}->insert($proxyObj);
15
16			use Data::Storage;
17			my $proxyObj = HttpProxy->new(
18			url => $url,
19			payload => $content,
20			);
21			$self->{storage}->insert($proxyObj);
22
23			NOTE
24
25			This module heavily relies on DBI and Tangram, but adds a lot of
26	joko	1.3	additional bugs and quirks. Please look at their documentation and/or
27			this code for additional information.
28
29			REQUIREMENTS
30			For full functionality: DBI from CPAN Tangram from CPAN Class::Tangram
31			from CPAN MySQL::Diff from http://adamspiers.org/computing/mysqldiff/
32			... and all their dependencies
33	joko	1.1
34			DESCRIPTION
35			Data::Storage is module for a accessing various "data structures" stored
36			inside various "data containers". It sits on top of DBI and/or Tangram.
37
38			AUTHORS / COPYRIGHT
39			The Data::Storage module is Copyright (c) 2002 Andreas Motl. All rights
40			reserved.
41
42			You may distribute it under the terms of either the GNU General Public
43			License or the Artistic License, as specified in the Perl README file.
44
45			ACKNOWLEDGEMENTS
46	joko	1.3	Larry Wall for Perl, Tim Bunce for DBI, Jean-Louis Leroy for Tangram and
47			Set::Object, Sam Vilain for Class::Tangram, Adam Spiers for MySQL::Diff
48			and all contributors.
49	joko	1.1
50			SUPPORT / WARRANTY
51			Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.
52
53			TODO
54			Handle the following errors/cases:
55
56			"DBI-Error [Tangram]: DBD::mysql::st execute failed: Unknown column 't1.requestdump' in 'field list'"
57
58			... occours when operating on object-attributes not introduced yet:
59			this should be detected and appended/replaced through:
60			"Schema-Error detected, maybe (just) an inconsistency.
61			Please check if your declaration in schema-module "a" matches structure in database "b" or try to run"
62			db_setup.pl --dbkey=import --action=deploy
63
64			Compare schema (structure diff) with database ...
65
66			... when issuing "db_setup.pl --dbkey=import --action=deploy"
67			on a database with an already deployed schema, use an additional "--update" then
68			to lift the schema inside the database to the current declared schema.
69			You will have to approve removals and changes on field-level while
70			new objects and new fields are introduced silently without any interaction needed.
71			In future versions there may be additional options to control silent processing of
72			removals and changes.
73			See this CRUD-table applying to the actions occouring on Classes and Class variables when deploying schemas,
74			don't mix this up with CRUD-actions on Objects, these are already handled by (e.g.) Tangram itself.
75			Classes:
76			C create -> yes, handled automatically
77			R retrieve -> no, not subject of this aspect since it is about deployment only
78			U update -> yes, automatically for Class meta-attributes, yes/no for Class variables (look at the rules down here)
79			D delete -> yes, just by user-interaction
80			Class variables:
81			C create -> yes, handled automatically
82			R retrieve -> no, not subject of this aspect since it is about deployment only
83			U update -> yes, just by user-interaction; maybe automatically if it can be determined that data wouldn't be lost
84			D delete -> yes, just by user-interaction
85	joko	1.2
86			It's all about not to be able to loose data simply while this is in pre-alpha stage.
87			And loosing data by being able to modify and redeploy schemas easily is definitely quite easy.
88
89			As we can see, creations of Classes and new Class variables is handled
90			automatically and this is believed to be the most common case under normal circumstances.
91	joko	1.1
92			Introduce some features:
93
94	joko	1.2	- Get this stuff together with UML (Unified Modeling Language) and/or standards from ODMG.
95			- Make it possible to load/save schemas in XMI (XML Metadata Interchange),
96			which seems to be most commonly used today, perhaps handle objects with OIFML.
97			Integrate/bundle this with a web-/html-based UML modeling tool or
98			some other interesting stuff like the "Co-operative UML Editor" from Uni Darmstadt. (web-/java-based)
99			- Enable Round Trip Engineering. Keep code and diagrams in sync. Don't annoy/bother the programmers.
100			- Add some more handlers:
101			- look at DBD::CSV, Text::CSV, XML::CSV, XML::Excel
102			- Add some more locations/locators:
103			- PerlDAV: http://www.webdav.org/perldav/
104			- Move to t3, use InCASE
105	joko	1.1
106			Links:
107
108	joko	1.2	Specs:
109	joko	1.1	UML 1.3 Spec: http://cgi.omg.org/cgi-bin/doc?ad/99-06-08.pdf
110			XMI 1.1 Spec: http://cgi.omg.org/cgi-bin/doc?ad/99-10-02.pdf
111			XMI 2.0 Spec: http://cgi.omg.org/docs/ad/01-06-12.pdf
112			ODMG: http://odmg.org/
113			OIFML: http://odmg.org/library/readingroom/oifml.pdf
114
115	joko	1.2	CASE Tools:
116			Rational Rose (commercial): http://www.rational.com/products/rose/
117			Together (commercial): http://www.oi.com/products/controlcenter/index.jsp
118			InCASE - Tangram-based Universal Object Editor
119			Sybase PowerDesigner: http://www.sybase.com/powerdesigner
120
121			UML Editors:
122			Fujaba (free, university): http://www.fujaba.de/
123			ArgoUML (free): http://argouml.tigris.org/
124			Poseidon (commercial): http://www.gentleware.com/products/poseidonDE.php3
125			Co-operative UML Editor (research): http://www.darmstadt.gmd.de/concert/activities/internal/umledit.html
126			Metamill (commercial): http://www.metamill.com/
127			Violet (university, research, education): http://www.horstmann.com/violet/
128			PyUt (free): http://pyut.sourceforge.net/
129			(Dia (free): http://www.lysator.liu.se/~alla/dia/)
130			UMLet (free, university): http://www.swt.tuwien.ac.at/umlet/index.html
131			Voodoo (free): http://voodoo.sourceforge.net/
132	joko	1.3	Umbrello UML Modeller: http://uml.sourceforge.net/
133	joko	1.2
134			UML Tools:
135			http://www.objectsbydesign.com/tools/umltools_byPrice.html
136
137			Further readings:
138	joko	1.1	http://www.google.com/search?q=web+based+uml+editor&hl=en&lr=&ie=UTF-8&oe=UTF-8&start=10&sa=N
139			http://www.fernuni-hagen.de/DVT/Aktuelles/01FHHeidelberg.pdf
140			http://www.enhyper.com/src/documentation/
141			http://cis.cs.tu-berlin.de/Dokumente/Diplomarbeiten/2001/skinner.pdf
142			http://citeseer.nj.nec.com/vilain00diagrammatic.html
143			http://archive.devx.com/uml/articles/Smith01/Smith01-3.asp
144
MailToCvsAdmin">MailToCvsAdmin	ViewVC Help
Powered by ViewVC 1.1.26