Hi all,
I'm proud to announce SQL::Statement 1.28. It's the first release for
me where other DBI developers (Matin Evans, H. Merijn Brand) actively
contributed patches and do their own commits.
Thanks for that!
To all users of SQL::Statement or Meta-DBD's: Please take care when
updating SQL::Statement without DBI-1.612 - they depend on each other,
if both installed, and SQL::Statement 1.28 will break:
- DBD::DBM in DBI 1.611 and below
- DBD::CSV 0.29
- DBD::AnyData 0.09
- DBD::RAM
- DBD::PO 2.10
and maybe more.
Best regards,
Jens
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
