You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed at the Orchard meeting of 07.09.2021, for performance reasons linq2db queries shouldn't always open a transaction since for reads this is not necessary. Ideally, we'd have something like ITransactionManager.GetOrCreate() in Orchard or YesSql since YesSql opens transactions only the first time a write query happens, lazily.
See this discussion on what can be used from the linq2db API.
I don't have any specific suggestion; the implementation details are up to be figured out.
sarahelsaig
changed the title
Linq2db should queries should only use transactions for write queries
Linq2db queries should only use transactions for write queries
Feb 24, 2022
github-actionsbot
changed the title
Linq2db queries should only use transactions for write queries
Linq2db queries should only use transactions for write queries (OSOE-343)
Sep 18, 2022
As discussed at the Orchard meeting of 07.09.2021, for performance reasons linq2db queries shouldn't always open a transaction since for reads this is not necessary. Ideally, we'd have something like
ITransactionManager.GetOrCreate()
in Orchard or YesSql since YesSql opens transactions only the first time a write query happens, lazily.See this discussion on what can be used from the linq2db API.
Jira issue
The text was updated successfully, but these errors were encountered: