NAME
    DBIx::SQLEngine::Docs::ToDo - Tasks, ideas, and bugs

TO DO
    There are a number of things that could be done to improve this module.

  Distribution

    Consider bumping the version number; the leading 0.0xx may deter some
    potential users by suggesting a less complete package.

  Tests

    The test scripts are fairly minimal and really ought to exercise much
    more of the public interface. Specific things to add to the test
    include:

    - Test for inserting, updating and selecting nulls, including "is null"
    test.

    - Test new transaction code.

  Schema Information

    The column-information retrieve in DBIx::SQLEngine::Default should be
    using DBI's type_info methods.

    Bless the column info hashes into new Column and ColumnSet classes.

    Add very simple Table and TableSet classes.

  Additional Criteria

    The Criteria subclasses are incomplete. Candidates include: SubString,
    CaseInsensitiveSubString, NumericEquality, NumericInequality,
    StringInequality.

    Consider enabling pure-Perl interpretation of criteria:

      package DBO::Criteria::Equality;
  
      sub inverse { 'DBO::Criteria::Inequality' }
  
      # $flag = $crit->matches( $record );
      sub matches {
        my ($crit, $record) = @_;
        return ($crit->value( $record ) eq $crit->{'value'}) ? 1 : 0;
      }

  Internals

    Centralize logging interface by making 'DBI', 'SQL' arguments to general
    function, or using log4perl.

    Consider becoming a subclass of DBI via RootClass and DbTypeSubclass,
    rather than using composition via DBIx::AnyDBD. This is somewhat
    attractive: it might run faster by eliminating a layer of delegation,
    and it would facilitate separation of the DBH and STH methods. The
    downside is loosing the flexibility of composition: if someone had their
    own DBI subclass, we could dynamically wrap around it if using
    composition, but it might be harder to dynamically inherit from it.
    There's also a certain degree of inertia in favor of not changing it.

  Database Subclasses

    Collect more subclasses.

    Review DBIx::Compat; it seems like this information should map fairly
    directly to candidate methods and subclasses.

SEE ALSO
    the DBIx::SQLEngine::ReadMe manpage

