The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

Changes for version 1.20 - 2011-11-30

  • No changes since 1.11-TRIAL. Releasing as stable.

Changes for version 1.11-TRIAL - 2011-05-03 (TRIAL RELEASE)

  • I'm looking for feedback on the new "strict mode" before including it a stable release. Contact: Mark Stosberg <mark@summersault.com>
  • THINGS THAT MIGHT BREAK YOUR CODE
    • This is no longer supported for enabling SQL tracing: SQL::Interp TRACE => 1; You can still set $ENV{TRACE_SQL} = 1 to enable SQL tracing.
  • FEATURES
    • Add sql_interp_strict() as a first stab at an API for adding a strict mode.
    • Switched to using Sub::Exporter and Exporter. This allows you to do this:
      • use SQL::Interp 'sql_interp_strict' => { -as => 'sql_interp' };
      • So that strict mode is enabled throughout your code. Before you do that, read the docs on sql_interp_strict-- some of your code may need to be refactored for it work, so you may want to start with the incremental approach.
      • While sql_interp() will work as before for backwards compatibility, you can do this to rename them on import now:
      • use SQL::Interp 'sql_interp' => { -as => 'sql_interp_insecure' }, 'sql_interp_strict' => { -as => 'sql_interp' };
      • If you would like a shortcut for this in the form of SQL::Interp::Strict, let me know.
  • DOCUMENTATION
    • The documentation has been updated to clarify that DBIx::Simple's SQL::Interp integration is recommended over DBIx::Interp.
    • Noted that SQL::Interp now has the primary repo hosted on Github: https://github.com/markstos/SQL-Interp

Modules

Interpolate Perl variables into SQL with DBI
Interpolate Perl variables into SQL statements

Provides

in lib/DBIx/Interp.pm
in lib/DBIx/Interp.pm
in lib/SQL/Interp.pm
in lib/SQL/Interp.pm