Temporal versioning for sequel, fully tested.

Translate model attributes for sequel, fully tested.

Read through caching library inspired by Cache Money, support Sequel 4 Read-Through: Queries by ID or any specified unique key, like `User[params[:id]]` or `User[username: 'bachue@gmail.com']`, will first look in memcache store and then look in the database for the results of that query. If there is a cache miss, it will populate the cache. As objects are created, updated, and deleted, all of the caches are automatically expired.

Sequel::Units provides a simple way to work with numeric values with units in Sequel models.

Sequel plugins to handle encrypted attributes

A light-weight simple to use gem to manage sequencing of records in the database. Check the homepage for more information.

Formatted sequence for rails models with unique scope

Sequent-Rails is providing Rails specific features and helpers around the CQRS and Event-Sourcing framework Sequent.

Add dynamic JSON data to active records. Access it like documents. Query it.

Adds named scopes for ActiveRecord/ActiveResource serialization methods (to_xml, to_json)

Serialize model attributes to a single database column instead

Ability to have several activerecord-like attributes in a single serialized column

Manage text field attribute serialized as an array, hash, etc. Add per-item validation

virtual attributes accessor via a serialized Hash column

An add-on for ActiveRecord and Mongoid which allows serialization options to be stored on a model.

serialize_with_coder is an ActiveRecord 2.x extended serialize function which acts like Rails 3.1 one - you can use custom coder as storing engine. Including 2 sample coders - CSV and JSON.

Simple XML and JSON APIs for your Rails app

ActiveRecord::Coder to transition serialized attributes from YAML to JSON.

Have you ever had a class whose instances required a series of background tasks to run serially, strictly one after another? Than Serially is for you. Declare the tasks using a simple DSL in the order you want them to to run. The tasks for each instance will run inside a separate Resque job, in a queue you specify. The next task will run only if the previous one has finished successfully. All task runs are written to DB and can be inspected.

Serialized Preferences for your models