Releases: Laragear/CacheQuery
v4.1.0
What's Changed
- Apply fixes from StyleCI by @DarkGhostHunter in #33
- [4.x] Adds support for custom query hasher function. by @DarkGhostHunter in #34
Full Changelog: v4.0.0...v4.1.0
v4.0.0
What's Changed
- Apply fixes from StyleCI by @DarkGhostHunter in #28
- Apply fixes from StyleCI by @DarkGhostHunter in #31
Full Changelog: v3.1.2...v4.0.0
v3.1.2
What's Changed
- Fixes stub autocompletion by @DarkGhostHunter in #23
- Apply fixes from StyleCI by @DarkGhostHunter in #24
Full Changelog: v3.1.1...v3.1.2
v3.1.1
What's Changed
- Fixes
groupBy
clauses by extending the proxy with aConnection
class in dc286c8 - Apply fixes from StyleCI by @DarkGhostHunter in #22
Full Changelog: v3.1.0...v3.1.1
v3.1.0
What's Changed
- Apply fixes from StyleCI by @DarkGhostHunter in #16
- Better GitHub config and actions. by @DarkGhostHunter in #17
- [3.x] Adds PHP 8.2, Laravel 10 support by @DarkGhostHunter in #21
Full Changelog: v3.0.1...v3.1.0
Minor fix for deleting keys
New cache system
This 3.x is a more cleaner implementation of caching queries, as it wraps the Database Connection into a proxy and hears select
statements.
It also supports programmatically caching results forever with null
, or regenerating them with false
.
Minor cosmetic fix
- Adds SonarCloud badge.
New release, new mechanic
This new release doesn't break anything, but it changes how it caches results. It simply proxies the underlaying connection for a SELECT
statement. Proxying the Database Connection is by far a better implementation of cache interception.
This version will run in parallel with version 2.0, so you can choose for the foreseeable future which feels better for you, unless 1.x becomes hard to maintain.
Command for removing keys
What's Added
- This new release adds a command to forget named keys from the CLI:
cache-query:forget my-named-key
.