Updating databases/p5-SQL-Statement from 1.27 to 1.28

pkgsrc changes:
- require DBI-1.612 for testing
- add conflict for DBI<=1.612

Upstream changes:
Version 1.28, release July 15th, 2010
----------------------------------------------

[Improvements]
* Introduce new "capability" method for SQL::Statement and SQL::Eval::Table
  + Add capability for "insert_new_row" to allow DBD::DBM to fix PK
    constrain on INSERT statements.
* Performance of IMPORT feature improved (thanks to Sven Probst, RT#57322)

[Bug fixes]
* expect every table object being derived from SQL::Eval::Table
* rewrite DELETE and UPDATE command based on table capabilities
* add abstract methods for all methods derived classes must override
  (this means, open_table for SQL::Statement deriveds must be overridden
   and all data access methods of tables - see SQL::Eval::Table for details)
* Tests are fixed to use TEMP TABLES explicitely when required
* check for invalid column names fixed
* Don't let depreciated parser structures stay alive in SQL::Statement when
  reusing the Parser

[Documentation]
* Method documentation of SQL::Statement and SQL::Eval::Table are improved
* Add a Roadmap describing future plans for SQL::Statement (in addition to
  DBD::File::Roadmap).
* POD spelling fixes provided by H.Merijn Brand and Pod::Spell::CommonMistakes
  (thanks Tux)
* POD grammar fixes and reasonable sentences created by Martin Evans

[Things that may break your code]
* SQL::Statement 1.28 is expected not to work proper in combination with
  DBI 1.611 and below
* SQL::Statement::ColumnValue expects now every table being derived from
  SQL::Eval::Table

0 files changed, 0 insertions, 0 deletions