returned from storage
- Custom condition relationships are now invoked with a slightly
different signature (existing coderefs will continue to work)
- - Add extra custom condition coderef attribute 'foreign_resultobj'
+ - Add extra custom condition coderef attribute 'foreign_result_object'
to allow for proper reverse-relationship emulation
- (i.e. $result->set_from_related($custom_cond, $foreign_resultobj)
+ (i.e. $result->set_from_related($custom_rel, $foreign_result_object)
- When in a transaction, DBIC::Ordered now seamlesly handles result
objects that went out of sync with the storage (RT#96499)
resultsets with no rows
- Fix incorrect handling of custom relationship conditions returning
SQLA literal expressions
+ - Fix long standing bug with populate() getting confused by hashrefs
+ with different sets of keys: http://is.gd/2011_dbic_populate_gotcha
- Fix multi-value literal populate not working with simplified bind
specifications
- Massively improve the implied resultset condition parsing - now all
without bombing out (RT#93244)
- Fix set_inflated_column incorrectly handling \[] literals (GH#44)
- Ensure that setting a column to a literal invariably marks it dirty
+ - Work around exception objects with broken string overloading in one
+ additional codepath (missed in 0.08260)
- Fix inability to handle multiple consecutive transactions with
savepoints on DBD::SQLite < 1.39
* Misc
+ - Ensure source metadata calls always take place on the result source
+ instance registered with the caller
- IFF DBIC_TRACE output defaults to STDERR we now silence the possible
wide-char warnings if the trace happens to contain unicode
- Remove ::ResultSource::resolve_condition - the underlying machinery