First step to add some sanity to _resolve_condition

[dbsrgits/DBIx-Class.git] / Changes

diff --git a/Changes b/Changes
index 2932f71..88ed825 100644 (file)
--- a/Changes
+++ b/Changes
@@ -7,9 +7,13 @@ Revision history for DBIx::Class
           returned from storage
 
     * Fixes
+        - Fix Resultset delete/update affecting *THE ENTIRE TABLE* in cases
+          of empty (due to conditions) resultsets with multi-column keys
         - Fix on_connect_* not always firing in some cases - a race condition
           existed between storage accessor setters and the determine_driver
           routines, triggering a connection before the set-cycle is finished
+        - Fix incorrect handling of custom relationship conditions returning
+          SQLA literal expressions
         - Fix multi-value literal populate not working with simplified bind
           specifications
         - Massively improve the implied resultset condition parsing - now all
@@ -25,6 +29,8 @@ Revision history for DBIx::Class
     * Misc
         - Stop explicitly stringifying objects before passing them to DBI,
           instead assume that the DBI/DBD combo will take care of things
+        - Remove ::ResultSource::resolve_condition - the underlying machinery
+          is in flux, and the method has had a deprecation warning for 5 years
 
 0.08270 2014-01-30 21:54 (PST)
     * Fixes