develop into main #29
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated README with comprehensive documentation for the new minimum prefix length feature introduced in previous release. Changes: - Added min_prefix_length to configuration example - Created Configuration Options table with all settings - Added dedicated "Minimum Prefix Length" section with: - Clear explanation of the feature - Code examples showing behavior - Recommended values for different use cases - Environment variable configuration - Updated config example to include all current options This addresses documentation gap for the minimum prefix length feature that prevents overly broad searches from short terms.
This feature enables efficient searching across multiple fields in a single database query, significantly improving performance for complex search scenarios. New Scopes Added: 1. encryptedSearchAny() - OR logic across multiple fields - Searches same term in multiple fields - Returns models where ANY field matches - Example: Client::encryptedSearchAny(['first_names', 'last_names'], 'John', 'exact') 2. encryptedSearchAll() - AND logic with field-specific terms - Searches different terms in different fields - Returns models where ALL fields match their respective terms - Example: Client::encryptedSearchAll(['first_names' => 'John', 'last_names' => 'Doe'], 'exact') Benefits: - Single database query instead of multiple individual queries - Reduced database round-trips - Lower memory footprint - Better performance at scale - Supports both exact and prefix search types - Works with both database and Elasticsearch backends Test Coverage: - Added 13 comprehensive tests (BatchQueryTest.php) - Tests cover OR/AND logic, edge cases, empty inputs - Performance comparison test validates optimization - Tests confirm minimum prefix length compliance - All 89 tests passing (161 assertions) This addresses performance optimization requirement #1: batch queries for multiple fields in complex search scenarios.
…y-optimization add batch query optimization for multiple fields
…-min-prefix-length docs: add min_prefix_length configuration documentation
Implements a caching layer for encrypted search queries to improve performance by reducing redundant database/Elasticsearch queries. Features: - Configurable TTL and enable/disable via config - Smart cache invalidation based on model updates - Support for cache tagging (Redis, Memcached, DynamoDB, Octane) - Automatic cache invalidation when configuration changes - Fallback for non-tagging cache drivers Cache keys are generated based on model class, search type, search parameters, and configuration hash to ensure proper cache isolation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…ult-caching add SearchCacheService for caching encrypted search results
ginkelsoft-development
added a commit
that referenced
this pull request
Oct 14, 2025
develop into main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.