@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Remove doc references to LiskDAO::loadRelatives()
Summary:
`loadRelatives()` was removed in rP9aa5a52fbd1b4265633df88b337eb95acee9bd85.
Thus remove it from the docs.
Test Plan: None. Optionally, run `./bin/diviner generate`
Reviewers: O1 Blessed Committers, mainframe98, valerio.bozzolan
Reviewed By: O1 Blessed Committers, mainframe98, valerio.bozzolan
Subscribers: tobiaswiese, valerio.bozzolan, Matthew, Cigaryno
Differential Revision: https://we.phorge.it/D25982
-6
-3
src/docs/contributor/n_plus_one.diviner
-3
src/docs/contributor/n_plus_one.diviner
···
63
63
will perform much better (although, as with all performance changes, you should
64
64
verify this claim by measuring it).
65
65
66
-
See also @{method:LiskDAO::loadRelatives} method which provides an abstraction
67
-
to prevent this problem.
68
-
69
66
= Detecting the Problem =
70
67
71
68
Beyond reasoning about it while figuring out how to load the data you need, the
-3
src/infrastructure/storage/lisk/LiskDAO.php
-3
src/infrastructure/storage/lisk/LiskDAO.php
···
122
122
* @{method:loadAllWhere} returns a list of objects, while
123
123
* @{method:loadOneWhere} returns a single object (or `null`).
124
124
*
125
-
* There's also a @{method:loadRelatives} method which helps to prevent the 1+N
126
-
* queries problem.
127
-
*
128
125
* = Managing Transactions =
129
126
*
130
127
* Lisk uses a transaction stack, so code does not generally need to be aware