From fce62cf424905c9cdfb47eeaf4317db24f17e1fa Mon Sep 17 00:00:00 2001 From: armando-migliaccio Date: Fri, 18 Dec 2015 16:34:21 -0800 Subject: [PATCH] Add notes on loading strategies for ORM relationships There have been a number of regressions caused by our inability to thoroughly review relatiohships' loading strategies. We should at least make an attempt to remind ourselves, and since I am guilty as charged, this patch is my attempt to redemption. Change-Id: I879cfceaa51386e9d6c683e7e02487df92b7e290 --- doc/source/devref/effective_neutron.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/source/devref/effective_neutron.rst b/doc/source/devref/effective_neutron.rst index bbe918189..13c9bd830 100644 --- a/doc/source/devref/effective_neutron.rst +++ b/doc/source/devref/effective_neutron.rst @@ -104,6 +104,10 @@ Document common pitfalls as well as good practices done during database developm transaction blocks, and the innermost block raises an error without proper rollback. Consider if `savepoints `_ can fit your use case. +* When designing data models that are related to each other, be careful to how + you model the relationships' loading `strategy `_. For instance a joined relationship can + be very efficient over others (some examples include `router gateways `_ + or `network availability zones `_). System development ~~~~~~~~~~~~~~~~~~ -- 2.45.2