On Wed, Oct 29, 2003 at 01:06:27PM +0100, Perl Authors Upload Server wrote: > > The following module was proposed for inclusion in the Module List: > > modid: DBIx::Composer > DSLIP: adpOp > description: Composing and executing of SQL statements > userid: PLISCO (Igor Plisco) > chapterid: 7 (Database_Interfaces) > communities: > > similar: > > rationale: > > Module DBIx::Composer composes SQL statements from parts (table > name, field list, 'where' clause etc.). Then it can execute these > statements. It makes SQL command composing more clear and convenient > for common cases. > > Name DBIx::Composer is appropriate because 1) it deals with > database and SQL, so should be under DBIx namespace, 2) its main > task is _composing_ SQL statements from parts. > > Usage of module is like following: > > $cmd = new DBIx::Composer; $cmd->table = 'table1'; $cmd->fields = > 'field1, field2'; $cmd->where = 'where field3 > 0'; @out = > $cmd->selectrow_array;
Actually, the SQL::* namespace seems more appropriate. But your example is confusing because it implies that $cmd->selectrow_array performs the select, and yet there's no $dbh in the example quoted. In fact the example makes the module seem almost trivial. How does it compare to modules like SQL::Abstract and SQL::Generator? Tim.
