And also async was a huge help with that too.
ah. nano.atomic ... found it. sorry
Hello. I'm in trouble with testing nano (with mocha/chai/sinon). I would like to simply verify nano.db.create is called in my code, but I can't get how to do it :
But all I get is TypeError: Attempted to wrap undefined property db.create as function
Does anybody know how can I get it right, please ?
var nano = require('nano')('http://localhost:5984');
var mock = sinon.mock(nano.db); mock.expects('db.create').atLeast(1).withExactArgs('bus_stop_dev').returns(true);But all I get is TypeError: Attempted to wrap undefined property db.create as function
Does anybody know how can I get it right, please ?
Hello. I'm in trouble with testing nano (with mocha/chai/sinon). I would like to simply verify nano.db.create is called in my code, but I can't get how to do it :
var nano = require('nano')('http://localhost:5984'); var mock = sinon.mock(nano.db); mock.expects('db.create').atLeast(1).withExactArgs('bus_stop_dev').returns(true);
But all I get is TypeError: Attempted to wrap undefined property db.create as function
Does anybody know how can I get it right, please ?
Changed my code : mock.expects('create') instead of 'db.create'. Now I get ExpectationError: Expected create(bus_stop_dev) at least once (never called)
Callback should be called with response to client, if upload success
with some JSON data
where can I call this callback?
// Should I call result callback from `cb`
var ws = db.attachment.insert(documentName, attName, null, mimetype, {rev : response.rev}, function(...) {})
// Or should I call in on ('end') event
ws.on('end', ...)
// Should I catch write stream errors?
ws.on('error', function (err) {...})
// Should I catch input stream errors?
file.on('error', function(err) {...})
file.pipe(ws)
hi @hellboy81, this is how I do it (read file from disk, pipe to db attachment ):
// add attachment
var dbWriteStream = db.attachment.insert(doc._id, filename, null, type, {rev: doc._rev}, uploaded);
var fileReadStream = fs.createReadStream(file.path);
fileReadStream.on('error', error);
dbWriteStream.on('error', error);
fileReadStream.pipe(dbWriteStream);
uploaded is the callback that gets called when piping is complete
then, uploaded():
function uploaded(err, body) {
if (err) {
console.log("[Attachment] Error in upload.");
if (err.status_code === 409) {
console.log('Attachment upload conflict, retry.');
addAttachment(req, res);
return;
}
else {
console.log("Unrecoverable error in upload", err);
clearTmp();
return error(err);
}
}
clearTmp();
....
}
so i would suggest you to use the variant above, where nano handles it the way it wants
It's celar
@hellboy81 i have no idea, i just remember that dealing with
on('end', ...) was not successful that time i wrote that code
?
But a good programmer handles it in one way or the other ;)
(my strategy here is to refetch the document to get the latest revision and try again to upload, as long until it works, may not be the best for all applications)
for "making it work", you don't need to handle 409. Handle it when the problem gets frequent
ok then just go for it and not handle 409 that's perfectly fine
you can read more about conflicts here: http://guide.couchdb.org/draft/conflicts.html or here: http://writing.jan.io/2013/12/19/understanding-couchdb-conflicts.html
Isn't it?
wir können auch Deutsch sprechen ;-)
No, let's go with english, as this is a public channel and other people may want to profit from our discussion
aber danke :)
Habe noch eine Frage: wenn db.insert ein nicht-leeres
err - Objekt zurückgibt, dies bedeutet automatisch, dass ok == false und umgekehrt kein Error - ok ist immer true