This is an automated email from the git hooks/post-receive script.

jame-guest pushed a commit to branch master
in repository libpgobject-simple-perl.

commit ecd416c167cbe833b568405967aa1c237f81a950
Author: Robert James Clay <>
Date:   Sun Apr 27 14:18:47 2014 -0400

    Long description in debian/control updated from new upstream README.
 debian/control | 34 +++++++++++++---------------------
 1 file changed, 13 insertions(+), 21 deletions(-)

diff --git a/debian/control b/debian/control
index fde284d..440d389 100644
--- a/debian/control
+++ b/debian/control
@@ -16,26 +16,18 @@ Architecture: all
 Depends: ${misc:Depends}, ${perl:Depends},
 Description: minimalist stored procedure mapper based on LedgerSMB's DBObject
- PGObject::Simple a top-half object system for PGObject which is simple and
- inspired by (and a subset functionally speaking of) the simple stored
- procedure object method system of LedgerSMB 1.3. The framework discovers
- stored procedure APIs and dispatches to them and can therefore be a base for
- application-specific object models and much more.
+ PBObject::Simple is a minimalist framework for mapping stored procedures in
+ PostgreSQL to object methods. The framework is truly minimalist and hence the
+ "Simple" designation (in fact the module contains less than 50 lines of code,
+ and the code is dwarfed by both POD and test cases). It is intended to be of
+ use for developers wishing for such a minimalist framework and those who may
+ want to have a reference for how to build such a mapping framework themselves.
- PGObject::Simple is designed to be light-weight and yet robust glue between
- your object model and the RDBMS's stored procedures. It works by looking up
- the stored procedure arguments, stripping them of the conventional prefix
- 'in_', and mapping what is left to object property names. Properties can be
- overridden by passing in a hashrefs in the args named argument. Named
- arguments there will be used in place of object properties.
+ The framework lends itself to a few specific antipatterns. Objects can become
+ ill-formed, overly nebulous, or the like. It is thus very important when using
+ this for actual development to ensure that acceptable data structures are well
+ documented and that these are adhered to.
- This system is quite flexible, perhaps too much so, and it relies on the
- database encapsulating its own logic behind self-documenting stored
- procedures using consistent conventions. No function which is expected to be
- discovered can be overloaded, and all arguments must be named for their
- object properties. For this reason the use of this module fundamentally
- changes the contract of the stored procedure from that of a fixed number of
- arguments in fixed types contract to one where the name must be unique and
- the stored procedures must be coded to the application's interface. This
- inverts the way stored procedures are typically thought about and makes them
- much more application friendly.
+ This module is based on a simple idea, namely that stored procedures can tell
+ application classes how to call them. See the POD for specific information and
+ guidelines.

Alioth's /usr/local/bin/git-commit-notice on 

Pkg-perl-cvs-commits mailing list

Reply via email to