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
?
*them
OK, at the moment I have following problem:
I am trying to implement attachment upload in the right way.
As I mentioned I should do it in following steps
- db.get - Get document (existing or not existing)
- db.insert - If document not exists
- db.attachment.insert - Insert attachment
- If attachment upload success:
- db.get to get the updated versions (with `_attachments`) - Add additional custom attachment meta data to the document - db.insert - Save updated document
- If attachment upload success:
Can you verify it?
Is there
db.attachment.head implementation?
Since v6.x passing in a url requires it to be https? Therefor require('nano')('http://localhost:5984/foo'); fails. Is this the expected behavior and we should all use https now?
?
@dscape
As I mentioned in nano there is no db.head
And the best way to ensure that
- CouchDB is online
- Database is available (exists)
it to create it?
I’m trying to understand search
can I search a field for instances of a string and return the doc?
is that how that works?
logs: (thing, callback) => {
nano.db.use(‘mydb').search('log', 'logs', { message: ’searchstring’}, (err, data) => {
callback(err, data);
});
},
where I have a field in my logs view called message
Error: missing handler: _search
so I guess I am doing something wrong
hmm
