New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to use the in-memory database #38
Comments
nolanlawson
added a commit
that referenced
this issue
May 28, 2014
nolanlawson
added a commit
that referenced
this issue
May 28, 2014
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
May 28, 2014
nolanlawson
added a commit
that referenced
this issue
May 28, 2014
nolanlawson
added a commit
that referenced
this issue
May 30, 2014
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
May 30, 2014
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
May 31, 2014
nolanlawson
added a commit
that referenced
this issue
May 31, 2014
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
Jun 1, 2014
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
Jun 1, 2014
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
Jun 1, 2014
Also related to pouchdb/pouchdb-server#36. Also fixes #51 because we now use the pouchdb-all-dbs plugin.
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
Jun 1, 2014
Also related to pouchdb/pouchdb-server#36. Also fixes #51 because we now use the pouchdb-all-dbs plugin.
nolanlawson
added a commit
to pouchdb/express-pouchdb
that referenced
this issue
Jun 4, 2014
Also related to pouchdb/pouchdb-server#36. Also fixes #51 because we now use the pouchdb-all-dbs plugin.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Eventually we want to support multiple leveldown adapters, but I think MemDOWN is the one people will want the most, so I'd like to have an option like
--in-memory
.The text was updated successfully, but these errors were encountered: