Couchbase

Couchbase http://www.couchbase.com/issues This file is an XML representation of an issue en-us

5.2.4

845

26-12-2012

[CBMA-19] Need API for external path to CouchbaseMobile http://www.couchbase.com/issues/browse/CBMA-19 Couchbase Mobile Android A request for a small improvement for your Android API: You offer a method CouchbaseMobile.externalPath() to get the external path for Couchbase Mobile. We have implemented some kind of quota control that limits the used diskspace, so we need to find out the path where CouchDB stores its database files. Unfortunately this is a sub-folder of the one returned by externalPath(). We implemented a method on our own that returns new File(externalPath(), "/db/"); but that should be included in your CouchbaseMobile class (name of db folder could be changed) and used by CouchbaseMobile.installDatabase(String) as well. CBMA-19

Need API for external path to CouchbaseMobile

Improvement Minor Resolved Won't Fix Unassigned Perry Krug Mon, 31 Oct 2011 18:31:42 -0500 Mon, 15 Oct 2012 09:49:49 -0500 Mon, 15 Oct 2012 09:49:49 -0500 2.0-beta SDK 0 0 Will it work to execute this request against the running server? GET /_config/couchdb/database_dir This is the single point of truth for the answer you seek, so our API would just be querying this anyway: This works but implementing an asynchronous HTTP-GET with parsing afterwards and additional error handling would not be appropriate for only getting this directory. So far we have a working solution but we want the one-liner I suggested on your side rather than on our side because you might want to change the name of the “db”-subfolder for some reason. This is what is desired: Class CouchbaseMobile:          public static File databaseDir() {              return new File(externalPath(), "db");        }   And its usage in CouchbaseMobile.installDatabase():          public void installDatabase(String fileName) throws IOException {              File destination = new File(databaseDir(), fileName);              copyIffNotExists(fileName, destination);        } A better option would be to create a generic config API access layer in Java. I think this is properly done in Ektorp, so that we don't end up shipping an HTTP client as part of the default Couchbase Mobile package. Having that HTTP client in there would invite disaster as folks would start to use it for their primary access and then we'd start to have to support it. Chris Rank 11324 Time In Status