#QueryCache
LightNews LightNews
beefedai.bsky.social
Designing a Smart Cache for Analytical Query Acceleration

https://beefed.ai/en/smart-cache-analytical-query-acceleration

#SmartCache #QueryCache #CacheInvalidation #AcceleratorHitRate #Autowarming
Designing a Smart Cache for Analytical Query Acceleration
beefed.ai
July 4, 2026 at 3:25 AM
throwable.bsky.social
📦 grafite/query-cache v1.5.0

A database query caching system with invalidation automation.

🔗 https://github.com/GrafiteInc/QueryCache
June 29, 2026 at 7:28 PM
dailyzenntrends.bsky.social
今日のZennトレンド

TanStack Query を完全にゼロから実装して理解する
TanStack Queryの内部設計を理解するため、ゼロから実装して解説する記事です。
設計思想の把握を目的とし、useStateを用いた単純な実装の限界から、QueryやQueryCacheなどの役割分担、データ状態と通信状態を分ける仕組みへと段階的に解説します。
本家のソースコードを読み解くための地図となる簡略版の実装を通じて、動作原理を明らかにします。
TanStack Query を完全にゼロから実装して理解する
この記事についてTanStack Query（旧 React Query）は「サーバーの状態」を扱うためのライブラリとして広く使われています。useQuery を呼ぶだけでローディング・エラー・キャッシュ・再取得がよしなに処理され、とても便利です。ただ、便利さの裏で「中で何が起きているのか」がブラックボックスになりがちです。isPending がなぜ自動で切り替わるのか、別々のコンポーネントで同
zenn.dev
June 5, 2026 at 10:16 PM
beefedai.bsky.social
Indexing and Caching Strategies for Low-Latency Analytics

https://beefed.ai/en/indexing-caching-low-latency-analytics

#BloomFilterIndex #MaterializedViews #QueryCache #CacheInvalidation #SecondaryIndexes
Indexing and Caching Strategies for Low-Latency Analytics
beefed.ai
May 4, 2026 at 6:06 AM
throwable.bsky.social
📦 grafite/query-cache v1.4.0

A database query caching system with invalidation automation.

🔗 https://github.com/GrafiteInc/QueryCache
April 9, 2026 at 6:12 PM
parlaconguido.bsky.social
disable #activerecord query caching => in application.rb insert this: config.middleware.delete ActiveRecord::QueryCache #rails #cache
October 13, 2025 at 8:47 AM
pub.dev.web.brid.gy
v3.0.0 of fquery
Simple yet powerful async state management solution with in-built caching Changelog excerpt: - `QueryClientProvider`changed to `CacheProvider` - The methods in the `QueryClient`has been housed inside `QueryCache`and `QueryClient`has been removed. - New instance readers - `QueryInstance`, `InfiniteQueryInstance`, `QueriesInstance` - There are other breaking changes in builder as the core code now recides in `fquery_core`package.
pub.dev
October 5, 2025 at 9:30 AM
christoph.luppri.ch
Here's the PR that fixed this: github.com/rails/rails/...
Cause ActiveRecord::Base::reload to also ignore the QueryCache. by henders · Pull Request #19886 · rails/rails
This pull request gives a suggested implementation for causing the ActiveRecord::Base::reload method to not only ignore association and aggregation caches, but also to ignore the query cache. The m...
github.com
August 27, 2025 at 2:37 PM
throwable.bsky.social
📦 grafite/query-cache v1.1.0

A database query caching system with invalidation automation.

🔗 https://github.com/GrafiteInc/QueryCache
June 13, 2025 at 7:00 AM
throwable.bsky.social
📦 grafite/query-cache v1.0.3

A database query caching system with invalidation automation.

🔗 https://github.com/GrafiteInc/QueryCache
June 12, 2025 at 2:59 PM
throwable.bsky.social
📦 grafite/query-cache v1.0.2

A database query caching system with invalidation automation.

🔗 https://github.com/GrafiteInc/QueryCache
May 31, 2025 at 5:11 AM
throwable.bsky.social
📦 grafite/query-cache v1.0.1

A database query caching system with invalidation automation.

🔗 https://github.com/GrafiteInc/QueryCache
May 31, 2025 at 4:59 AM
throwable.bsky.social
📦 grafite/query-cache v1.0.0

A database query caching system with invalidation automation.

🔗 https://github.com/GrafiteInc/QueryCache
May 30, 2025 at 7:59 PM
fxn.bsky.social
These posts are triggered by this patch (though this topic has been in my mind for years).

AR::QueryCache::ClassMethods has to document it extends AR::Base. Otherwise, users cannot make the connection.

I think the module should not be listed in the first place.

github.com/rails/rails/...
Make the executor hooks in AR::QueryCache private by fxn · Pull Request #55007 · rails/rails
API docs show the executor hooks in ActiveRecord::QueryCache and their installer. These should be private, they are not supposed to be callable or overridden by external code. The patch also groups...
github.com
May 4, 2025 at 8:50 AM
ralexanderson.com
Here's how I did it: When a query is invalidated by any of the clients, a hook that's subscribed to the QueryCache gets notified and tells the SharedWorker. The SharedWorker then invalidates that query itself and sends the data to all of the open windows using that query.

Works for the POC.
February 28, 2025 at 4:35 PM
dogpawhat.tech
I think the global querycache callback is what you want there I think. tkdodo.eu/blog/react-q...
React Query Error Handling
After covering the sunshine cases of data fetching, it's time to look at situations where things don't go as planned and "Something went wrong..."
tkdodo.eu
January 21, 2025 at 10:13 PM
oljimenez.bsky.social
What I meant was that it would be great if fetch itself could access queryCache (if it's in the cache).

I know for this to work in RQ we would have to assign a key to the fetch call for it to work, like the url.

Access cache values ​​via fetch instead of queryClient.
December 9, 2024 at 12:47 PM
tkdodo.eu
I’m not sure what you mean with “access the queryCache directly”. Can you try to describe what you are trying to achieve? You say you “wish some day we could have this” but I’m struggling to understand what “this” refers to (mandatory this bindings are hard joke 😂)
December 9, 2024 at 10:07 AM
msnook.xyz
... client starts fetching data later.
2. I'm going to load this evergreen data into the querycache anyway for use in client components, now the NextJS cache has one copy and the query-cache has another.
3. There seems to just actually not be a way to resolve URLs not available at build time...
August 11, 2024 at 12:04 PM