Merge commit '2.11+2.111' into HEAD

[maypole.git] / lib / Maypole / Manual / Model.pod

diff --git a/lib/Maypole/Manual/Model.pod b/lib/Maypole/Manual/Model.pod
index 9add8934c6f6f6e9b42ee7e3ac83f6908bc80673..112effcb44d90e3823319adf4b994f5dfc63cb68 100644 (file)
--- a/lib/Maypole/Manual/Model.pod
+++ b/lib/Maypole/Manual/Model.pod
@@ -1,4 +1,8 @@
-=head1 Maypole Model Classes
+=head1 NAME
+
+Maypole::Manual::Model - Maypole Model Classes
+
+=head1 DESCRIPTION

 
 Maypole's model classes provide an interface to your data store.
 In principle Maypole can connect to pretty much any data source,
 
 Maypole's model classes provide an interface to your data store.
 In principle Maypole can connect to pretty much any data source,


@@ -37,8 +41,8 @@ make writing Maypole applications a lot easier:
 
     package Maypole::Model::CDBI;
     use base qw(Maypole::Model::Base Class::DBI);
 
     package Maypole::Model::CDBI;
     use base qw(Maypole::Model::Base Class::DBI);

-    use Class::DBI::AsForm;
-    use Class::DBI::FromCGI;
+    use Maypole::Model::CDBI::AsForm;
+    use Class::DBI::FromCGI;  # probabyly broken . 

     use Class::DBI::Loader;
     use Class::DBI::AbstractSearch;
     use Class::DBI::Plugin::RetrieveAll;
     use Class::DBI::Loader;
     use Class::DBI::AbstractSearch;
     use Class::DBI::Plugin::RetrieveAll;


@@ -109,10 +113,6 @@ We'll look more at how to put together actions in the
 L<Standard Templates and Actions|Maypole::Manual::StandardTemplates>
 chapter and our case studies.
 
 L<Standard Templates and Actions|Maypole::Manual::StandardTemplates>
 chapter and our case studies.
 

-=head2 What Maypole wants from a model
-
-=head2 Building your own model class
-

 =head2 Links
 
 L<Contents|Maypole::Manual>,
 =head2 Links
 
 L<Contents|Maypole::Manual>,