couch_potato icon indicating copy to clipboard operation
couch_potato copied to clipboard

Ruby persistence layer for CouchDB.

Results 13 couch_potato issues
Sort by recently updated
recently updated
newest added

Hi! I want to create an "offline first" app and I will use [PouchDB](https://pouchdb.com/) in the frontend. I wonder if sync/replication will work with Couch Potato and Rails. Thanks!

* one process loads a document * another process loads the same document * the first process changes and saves the doc * the 2nd process makes a change that...

bug

Last release was in 2017. There has been some work completed in HEAD as of 2020. Any chance of a new release? https://rubygems.org/gems/couch_potato

In order to get the latest version of a document, document.reload should not use the cache when set. e.g. this is important in cases where you want to avoid conflicts...

if you define a property with type: [String] and you try to set e.g. `"string"` instead of `["string"]` the error is hard to understand.

instead of having to pass startkey/endkey, come up with something nicer. especially for cases like `startkey: ['something'], endkey: ['something', {}]`.

it would be nice to be able to cache queries, for example for the duration of a web request.

Right now when you query a db you get back eiher a single Ruby object, an array ob Objects, the raw CouchDB results hash or a number. IMHO this should...

Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 4. Release notes Sourced from actions/checkout's releases. v4.0.0 What's Changed Update default runtime to node20 by @​takost in actions/checkout#1436 Support fetching without the --progress option...

dependencies