X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=Changes;h=236b7349c961b72aa6995675422a283114cf9213;hb=12e7015aa9372aeaf1aaa7e125b8ac8da216deb5;hp=c73756951d9c0e6513192993a6e460c454eb39d2;hpb=304409e12f0c26662204e662f69a67f04283840b;p=dbsrgits%2FDBIx-Class.git diff --git a/Changes b/Changes index c737569..236b734 100644 --- a/Changes +++ b/Changes @@ -10,6 +10,10 @@ Revision history for DBIx::Class the maintainer believe this is safe, but this is a very complex area and reality may turn out to be different. If **ANYHTING** at all seems out of place, please file a report at once + - The unique constraint info (including the primary key columns) is no + longer shared between related (class and schema-level) ResultSource + instances. If your app stops working with no obvious pointers, set + DBIC_ASSERT_NO_ERRONEOUS_METAINSTANCE_USE=1 to obtain extra info - Neither exception_action() nor $SIG{__DIE__} handlers are invoked on recoverable errors. This ensures that the retry logic is fully insulated from changes in control flow, as the handlers are only @@ -29,6 +33,10 @@ Revision history for DBIx::Class instead of silently discarding the argument * New Features + - DBIC now performs a range of sanity checks on the entire hierarchy + of Schema/Result/ResultSet classes loudly alerting the end user to + potential extremely hard-to-diagnose pitfalls ( RT#93976, also fully + addresses https://blog.afoolishmanifesto.com/posts/mros-and-you/ ) - InflateColumn::DateTime now accepts the ecosystem-standard option 'time_zone', in addition to the DBIC-only 'timezone' (GH#28) - Massively optimised literal SQL snippet scanner - fixes all known @@ -39,6 +47,8 @@ Revision history for DBIx::Class specific DateTime::Format dependencies * Fixes + - Fix regresion (0.082800) of certain calls being presented stale + result source metadata (RT#107462) - Fix incorrect SQL generated with invalid {rows} on complex resultset operations, generally more robust handling of rows/offset attrs - Fix incorrect $storage state on unexpected RDBMS disconnects and