[Jifty-commit] r1554 - in Jifty-DBI/trunk/lib/Jifty: . DBI

jifty-commit at lists.jifty.org jifty-commit at lists.jifty.org
Thu Jul 13 13:43:40 EDT 2006


Author: srl
Date: Thu Jul 13 13:43:36 2006
New Revision: 1554

Modified:
   Jifty-DBI/trunk/lib/Jifty/DBI.pm
   Jifty-DBI/trunk/lib/Jifty/DBI/Filter/Date.pm
   Jifty-DBI/trunk/lib/Jifty/DBI/Record.pm

Log:
POD fixes.

Modified: Jifty-DBI/trunk/lib/Jifty/DBI.pm
==============================================================================
--- Jifty-DBI/trunk/lib/Jifty/DBI.pm	(original)
+++ Jifty-DBI/trunk/lib/Jifty/DBI.pm	Thu Jul 13 13:43:36 2006
@@ -13,7 +13,7 @@
 Jifty::DBI deals with databases, so that you don't have to.
 
 This module provides an object-oriented mechanism for retrieving and
-updating data in a DBI-accesible database. 
+updating data in a DBI-accessible database. 
 
 This module is the direct descendent of L<DBIx::SearchBuilder>. If you're familiar
 with SearchBuilder, Jifty::DBI should be quite familiar to you.
@@ -21,7 +21,7 @@
 =head2 What is it trying to do. 
 
 Jifty::DBI::Record abstracts the agony of writing the common and generally 
-simple SQL statements needed to serialize and De-serialize an object to the
+simple SQL statements needed to serialize and de-serialize an object to the
 database.  In a traditional system, you would define various methods on 
 your object 'create', 'read', 'update', and 'delete' being the most common. 
 In each method you would have a SQL statement like: 
@@ -39,9 +39,9 @@
 Enter, Jifty::DBI::Record. 
 
 With ::Record, you can in the simple case, remove all of that code and 
-replace it by defining two methods and inheriting some code.  Its pretty 
-simple, and incredibly powerful.  For more complex cases, you can, gasp, 
-do more complicated things by overriding certain methods.  Lets stick with
+replace it by defining two methods and inheriting some code.  It's pretty 
+simple and incredibly powerful.  For more complex cases, you can 
+do more complicated things by overriding certain methods.  Let's stick with
 the simple case for now. 
 
 

Modified: Jifty-DBI/trunk/lib/Jifty/DBI/Filter/Date.pm
==============================================================================
--- Jifty-DBI/trunk/lib/Jifty/DBI/Filter/Date.pm	(original)
+++ Jifty-DBI/trunk/lib/Jifty/DBI/Filter/Date.pm	Thu Jul 13 13:43:36 2006
@@ -17,8 +17,7 @@
 
 This filter allow you to work with DateTime objects that represent "Dates",
 store everything in the database in GMT and not hurt yourself badly
-when you pull them out and put them in repeatedly
-text dates.
+when you pull them out and put them in repeatedly.
 
 =head2 encode
 

Modified: Jifty-DBI/trunk/lib/Jifty/DBI/Record.pm
==============================================================================
--- Jifty-DBI/trunk/lib/Jifty/DBI/Record.pm	(original)
+++ Jifty-DBI/trunk/lib/Jifty/DBI/Record.pm	Thu Jul 13 13:43:36 2006
@@ -76,6 +76,7 @@
     if ( $args{'handle'} ) {
         $self->_handle( $args{'handle'} );
     }
+
 }
 
 =head2 id
@@ -441,7 +442,7 @@
 contains C<column> and C<value> keys. If C<value> was a SQL function,
 it will now contain the actual value that was set.
 
-This hooks return value is ignored.
+This hook's return value is ignored.
 
 =item validate_I<column_name> VALUE
 
@@ -671,7 +672,7 @@
     # really going on. (ex SET Cost = Cost+5)
     if ( $args{'is_sql_function'} ) {
 
-        # XXX TODO primary_keys
+        .# XXX TODO primary_keys
         $self->load_by_cols( id => $self->id );
     } else {
         $self->{'values'}{ $column->name } = $unmunged_value;
@@ -683,8 +684,8 @@
 
 =head2 load
 
-Takes a single argument, $id. Calls load_by_cols to retrieve the row whose primary key
-is $id
+Takes a single argument, $id. Calls load_by_cols to retrieve the row 
+whose primary key is $id.
 
 =cut
 
@@ -750,6 +751,7 @@
 
 =head2 load_by_primary_keys 
 
+Loads records with a given set of primary keys. 
 
 =cut
 


More information about the Jifty-commit mailing list