---
title: "Comment by Mostafa Mohamed on \"High Performance MySQL [Ch.5: Indexing for High Performance]\" | Hashnode"
description: "SELECT ... WHERE date_col &gt;= DATE_SUB(CURRENT_DATE, INTERVAL 10 days); There is a subtlety in the new query that using an always changing value like CURRENT_"
url: "https://hashnode.com/posts/high-performance-mysql-ch5-indexing-for-high-performance/607ad6f3c99e200d08f7ae37/comment/67d79f3ece7cf5258cb4224d"
---

[Discussion](https://hashnode.com/posts/high-performance-mysql-ch5-indexing-for-high-performance/607ad6f3c99e200d08f7ae37)

Comment [High Performance MySQL \[Ch.5: Indexing for High Performance\]](https://hashnode.com/posts/high-performance-mysql-ch5-indexing-for-high-performance/607ad6f3c99e200d08f7ae37)

[Mostafa Mohamed](https://hashnode.com/@mostafao4o)

[Mar 17, 2025](https://hashnode.com/posts/high-performance-mysql-ch5-indexing-for-high-performance/607ad6f3c99e200d08f7ae37/comment/67d79f3ece7cf5258cb4224d)

SELECT ... WHERE date\_col >= DATE\_SUB(CURRENT\_DATE, INTERVAL 10 days); There is a subtlety in the new query that using an always changing value like CURRENT\_DATE although we don't need the entire date, just the days, will cause this query to miss the cache all the time. Is this argument still valid? as there is no query cache any more (by default at least)
