v0.5.5

Description -

Minor release - removed redundant png file

Full Changelog: v0.5.4...v0.5.5

elara v0.5.4

Description :

• Elara can now support keys of any type, not just strings!

• New ttl and ttls functions to retrieve time to live for all cache objects

• A new persist function to persist a key that previously had an expiry.

• Added linsert for lists and randomkey to fetch any random key from the database.

v0.5.4 out now on pypi! No breaking changes.

---

elara v0.5.3

Description :

• fixed json dump bug for export functions
• db writes are now done in a separate thread
• getmatch(key) to retrieve all key-value pairs that contain the substr in their key
• syntax sugar for get, set , rem and exists.

No breaking changes.

elara v0.5.2

Description :

• Fully atomic database writes using safer.
• updated tests

No breaking changes.

elara v0.5.1

Description :

• InvalidCacheParams exception class added for better error messages.
• Fixed internal bug in rem(key) (raises exception if lru.rem_key(key) returns Status.NOTFOUND)
• Improved testing for exceptions

No breaking changes were made from v0.5.0.

elara v0.5.0

Description :

• Re-designed the core cache and LRU backend to allow for default max_age, max_size and cull_freq parameters
• Updated set functions to take max_age param to allow for more granular control
• Official support for python 3.6. (Elara now supports 3.6 to 3.9)
• Updated tests and docs

No breaking changes were made from v0.4.x.

elara v0.4.0

Description :

This is a breaking change

• v0.4.x moves away from utf-8 encoded json based storage and stores data as bytes (uses msgpack dependency)
• Support for checksums to verify database file integrity
• updated tests

Every version after v0.4.0 will use the same storage method thus breaking changes w.r.t this may be unlikely.
To safeguard data, its better to export all existing data from any existing database file before upgrading Elara. (use exportdb(export_path)).

elara v0.3.0

Description :

• v0.2.1 and earlier used a mix of ascii and base64 encoding. v0.3.0 uses utf-8 encoding instead.
• To safeguard data, its better to export all existing data from any encrypted file before upgrading.
  You can then use the securedb() method to re-encrypt it.

This release is a breaking change from v0.2.x.

elara v0.2.1

Description :

• incr(key, val=1) and decr(key, val=1) added with tests

No breaking change.

elara v0.2.0

Description -

• Improved support for in-memory caching :
  • Includes a cull() function that deletes stale keys. Key access is tracked using the LRU principle
  • getkeys() returns all the keys in the database ordered by most recently accessed.
• Updated tests for LRU
• Updated documentation for cache

No breaking changes were made in this update.