ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nhibernate
When NHibernate’s second‑level cache isn’t working, performance suffers. This guide walks you through the most common symptoms, root causes, ordered checks, fixes, and when to seek help.
NHibernate's Take/Skip normally generates dialect-specific SQL for pagination, but when a collection is eagerly fetched (e.g., Fetch(p => p.Children) ), the query may fall back to in-memory pagination after loading the full result set. This makes the number of distinct entities returned less than the requested page size and leaves the total row count ambi
Learn how to safely use NHibernate’s built‑in Hashtable second‑level cache for read‑heavy workloads, what to monitor, where it can fail, and when to move to a distributed cache.
The goal is to allow a rolling upgrade of a .NET application that uses NHibernate while keeping the SQL Server database available, so that both the old and new versions can operate against the same schema without downtime. The main uncertainty is whether to rely on NHibernate’s automatic hbm2ddl.auto=update mode (or the SchemaUpdate tool) to propagate additi
NHibernate's async query API in the 5.x line accepts a CancellationToken, but the ORM delegates actual cancellation to the underlying ADO.NET provider's DbCommand.Cancel. This integration boundary means graceful cancellation depends on provider support rather than an ORM-level guarantee. When IQuery.SetTimeout is also configured, both the token and the timeo
Goal The objective is to retrieve a specific page—say the 10th page of 1,000 records—from a very large table that participates in a many‑to‑many relationship. The query must avoid loading the entire dataset into memory, prevent duplicate root entities, and maintain acceptable performance on SQL Server 2019 using NHibernate 6. Constraints & Uncertainty Pa
NHibernate's LINQ provider translates Skip() and Take() into SQL OFFSET/FETCH or LIMIT/OFFSET depending on the configured dialect. A documented behavioral ambiguity arises when these methods are applied without an explicit OrderBy clause, as the database may return rows in an unspecified order, producing inconsistent page results across separate executions.
The goal is to lower CPU and memory consumption for a low‑traffic NHibernate‑based web or service application while preventing LazyInitializationException when lazy‑loaded collections are accessed after the session is closed. Constraints include choosing appropriate second‑level cache regions and expiration policies, setting an AdoBatchSize that balances bat
NHibernate's automatic flush behavior under FlushMode.Auto is documented as a heuristic that flushes pending changes before a query only when the session determines the query might touch the same entity or table spaces. In workflows that mix HQL, Criteria, QueryOver, and LINQ against the same transaction, developers face an unresolved consistency decision: w