A streaming storage engine based on LevelDB.
Store your in-flight mqtt packets in Level
level store for mojule
Seneca leveldb store
Primitives for creating small reactive objects that doesn't change their shape over time - don't need a proxy wrapper.
Save binary blobs in level and stream then back
Encode data with built-in or custom encodings
Allow parsing of top-level await in modules
The parameters package for the Powertools for AWS Lambda (TypeScript) library
Low-level HTTP/HTTPS/XHR/fetch request interception library.
Backwards compatible shim for React's useSyncExternalStore. Works with any React that supports hooks.
datastore interface
LevelDb database adapter for Yjs
Definitions of levels for logging purposes & shareable Symbol constants.
👻🔁
Datastore implementation with level(up|down) backend
Invoke scoped data storage for AWS Lambda Node.js Runtime Environment
Generates and consumes source maps
An interface for storing and retrieving blocks
Detect whether a terminal supports color
Create a manifest describing the abilities of an abstract-level database
Fastest HTML entities encode/decode library.
Namespaced logger
A well-tested CSS minifier
Provides higher-level access to Configuration stored in the Environment
A simple Gem to enable any `ActiveRecord::Base` object to store a set of attributes in a set like structure represented through a bitfield on the database level. You only have to specify the name of the set to hold the attributes in question an the rest is done for you through some fine selected Ruby magic. Here is a simple example of how you could use the gem: class Person < ActiveRecord::Base has_set :interests end To get this to work you need some additional work done first: 1. You need an unsigned 8-Byte integer column in your database to store the bitfield. It is expected that the column is named after the name of the set with the suffix `_bitfield` appended (e.g. `interests_bitfield`). You can change that default behavior by providing the option `:column_name` (e.g. `has_set :interests, :column_name => :my_custom_column`). 2. You need a class that provides the valid values to be stored within the set and map the single bits back to something meaningful. The class should be named after the name of the set (you can change this through the `:enum_class` option). This class could be seen as an enumeration and must implement the following simple interface: * There must be a class method `values` to return all valid enumerators in the defined enumeration. * Each enumerator must implement a `name` method to return a literal representation for identification. The literal must be of the type `String`. * Each enumerator must implement a `bitfield_index` method to return the exponent of the number 2 for calculation the position of this enumerator in the bitfield. **Attention** Changing this index afterwards will destroy your data integrity. Here is a simple example of how to implement such a enumeration type while using the the `renum` gem for simplicity. You are free to use anything else that matches the described interface. enum :Interests do attr_reader :bitfield_index Art(0) Golf(1) Sleeping(2) Drinking(3) Dating(4) Shopping(5) def init(bitfield_index) @bitfield_index = bitfield_index end end
Rails session store using low-level redis-client for Redis 6+ For great glory!
Opt-in read through Active Record caching.
On the middleware level catch an exception from Rails app and store in the separated Redis database.
Use the policy pattern to define access control mechanisms in Rails. Store user-level, group-level, or org-level permission on any given record or concept in the database with ultra-fast lookups.
Provides a class level local data store with namespaces support
Store page and action descriptions in yaml files, use this library to perform all low-level Watir-webdriver calls
It just makes sense to store mutable, site-wide, admin-level settings in the database. Right? A key-value table may be more flexible, but maybe we don't want to be flexible! If you truly want that flexibility: http://github.com/stephencelis/kvc
RiakRest provides structured, RESTful interaction with the HTTP/JSON interface of a Riak[http://riak.basho.com] document data store. RiakRest provides two levels of interaction: Core Client and Resource. Core Client works at the Jiak level and exposes Jiak internals. JiakResource is an abstraction built on top of the Core Client that gives a true RESTful feel.
A gem that provides logging functionality for ActiveRecord models, storing logs in a separate table with support for log chains, metadata, and different visibility levels.
It just makes sense to store mutable, site-wide, admin-level settings in the database. Right? A key-value table may be more flexible, but maybe we don't want to be flexible! If you truly want that flexibility: http://github.com/stephencelis/kvc
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.