Stop NHibernate N+1 selects with LINQ Fetch and FetchMany
Use NHibernate LINQ Fetch and FetchMany to load associations in one query instead of triggering a select for every row.
Loading…
ReadMeFeed / Community knowledge
#n-plus-one
Real questions. Useful conversations. Find the people who know your stack.
nhibernateChoosing Between joinedload and selectinload in SQLAlchemy 2.0
Avoid N+1 queries in SQLAlchemy by choosing selectinload for collections and joinedload for scalar relationships, then verify with echo=True.
sqlalchemyStop N+1 Queries in CakePHP ORM with Contain
Use CakePHP ORM contain to eager load associations and avoid separate queries inside loops, with verification steps for CakePHP 4.x and 5.x.
cakephpEliminate N+1 queries in AdonisJS with Lucid eager loading
Use AdonisJS Lucid preload to fetch related records in one extra query instead of one per row.
adonisjsRails 7.1 strict_loading: A Gradual Audit for Lazy Associations
Use Rails 7.1 strict_loading to surface lazy-loaded associations incrementally. Start with per-relation checks, move to per-model enforcement, and opt out intentionally lazy associations.
railsUsing SQLAlchemy joinedload to Stop N+1 Queries on Many-to-One Relations
Learn how SQLAlchemy's joinedload replaces N+1 queries with a single JOIN for many-to-one and one-to-one relations, when to use it, and what to watch out for.
Fixing N+1 Queries in AdonisJS with Lucid Preloading
Learn how to use Lucid ORM's preload method in AdonisJS to eliminate N+1 queries, with a worked example, pagination tips, and trade-offs to consider.
Diagnosing and Resolving N+1 Queries in SQLAlchemy ORM
Diagnose SQLAlchemy N+1 query problems with echo logging, then fix them by choosing joinedload or selectinload based on relationship type — and verify the query count stays flat.
Diagnosing N+1 Queries in Yii2 ActiveRecord and Fixing Them with Eager Loading
A Yii2 list page shows one query for the parent models plus one query per row for each accessed relation. Diagnose it with the debug toolbar, confirm lazy loading in loops, then fix with with() for batched IN queries or joinWith() for filtering, plus indexes and selective selects.