Sha256: b37b9d936e731c07437214c251b83cef8fb7dde3bfd4b8c5b6d6ab19d4af29eb
Contents?: true
Size: 1.42 KB
Versions: 4
Compression:
Stored size: 1.42 KB
Contents
= Toystore An object mapper for anything that can read, write and delete data. See examples/ for potential direction. The idea is that any key-value store (via adapters) that supports read, write, delete will work (memcache, membase, mongo, redis, couch, toyko. Potentially even RESTFUL services or sqlite with a single key-value table?) == Mailing List https://groups.google.com/forum/#!forum/toystoreadapter == Identity Map By default, Toystore has identity map turned on. It assumes that any Toystore model has a unique id across all models. This means you either need to use the default uuid id's, object_id's (included), some other unique id, or create your own key factory that namespaces to model (see examples). You also need to clear the map before each request. For this, there is a provided piece of middleware that you can use. use(Toy::Middleware::IdentityMap) It is autoloaded, so just add it to your config.ru or sinatra/rails app as you would any other middleware and you are good to go. == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so we don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine, but bump version in a commit by itself so we can ignore when we pull) * Send us a pull request. Bonus points for topic branches.
Version data entries
4 entries across 4 versions & 1 rubygems
Version | Path |
---|---|
toystore-0.7.0 | README.rdoc |
toystore-0.6.6 | README.rdoc |
toystore-0.6.5 | README.rdoc |
toystore-0.6.4 | README.rdoc |