first commit

Author: araga-dev

.gitattributes

@@ -0,0 +1,10 @@
+* text=auto eol=lf
+
+*.php text eol=lf
+*.md text eol=lf
+*.json text eol=lf
+
+# Exclude from archives
+.gitattributes export-ignore
+.gitignore export-ignore
+examples/ export-ignore

.gitignore

@@ -0,0 +1,29 @@
+# Dependencies
+/vendor/
+composer.lock
+
+# IDE
+/.idea/
+/.vscode/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Testing
+/.phpunit.cache/
+.phpunit.result.cache
+
+# Runtime
+*.log
+*.db
+*.db-shm
+*.db-wal
+/storage/
+
+# Build artifacts
+/build/
+/dist/

CHANGELOG.md

@@ -0,0 +1,66 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - Unreleased
+
+### Added
+- **PSR-16 SimpleCache compliance** - Full implementation of `Psr\SimpleCache\CacheInterface`
+- `DateInterval` support for TTL values (PSR-16 standard)
+- `setMultiple()` method for batch setting (PSR-16)
+- `getMultiple()` method for batch retrieval (PSR-16)
+- `deleteMultiple()` method for batch deletion (PSR-16)
+- Simple key/value storage with SQLite
+- TTL support for automatic expiration
+- Atomic increment/decrement operations
+- Transaction support
+- WAL mode for better concurrency
+- Chunk processing for large datasets
+- Database statistics via `stats()`
+- Garbage collection for expired keys via `cleanExpired()`
+- `pull()` method for get-and-delete operation
+- Multiple examples demonstrating usage
+- Comprehensive documentation
+
+### Changed
+- **BREAKING**: `forget()` renamed to `delete()` (PSR-16 standard)
+- **BREAKING**: `flush()` renamed to `clear()` (PSR-16 standard)
+- **BREAKING**: `setMany()` renamed to `setMultiple()` (PSR-16 standard)
+- **BREAKING**: `many()` renamed to `getMultiple()` (PSR-16 standard)
+- `set()` now returns `bool` instead of `void` (PSR-16 compliance)
+- `delete()` now returns `bool` instead of `void` (PSR-16 compliance)
+- `clear()` now returns `bool` instead of `void` (PSR-16 compliance)
+- TTL parameter now accepts `int|DateInterval|null` instead of just `int|null`
+
+### Fixed
+- TTL handling with value 0 (now correctly treated as "already expired")
+- Optimized `has()` method to avoid unnecessary JSON decoding
+- Batch deletion of expired keys in `all()` method
+
+### Security
+- Table name sanitization to prevent SQL injection
+- Value size validation (max 10MB recommended)
+- Proper key validation in batch operations
+
+## Migration Guide from Pre-1.0
+
+If you're upgrading from a pre-PSR-16 version, update your code as follows:
+
+```php
+// Before
+$cache->forget('key');
+$cache->flush();
+$cache->setMany(['key' => 'value']);
+$values = $cache->many(['key1', 'key2']);
+
+// After (PSR-16 compliant)
+$cache->delete('key');
+$cache->clear();
+$cache->setMultiple(['key' => 'value']);
+$values = $cache->getMultiple(['key1', 'key2']);
+```
+
+All other methods (`get`, `has`, `increment`, `decrement`, `pull`, `all`, `keys`, `transaction`, `chunk`, `cleanExpired`, `stats`) remain unchanged.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Mário Aragão
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.