couch.Doc interface

[jinroh]

See #36.

The doctype on the JSONDoc felt weird and we may fallback on this one... This change will affect the crud api since it adds a explicit doctype field to documents.. while the _id field also contains it. I'm not really sure about that.

Other than that, I don't see many issue.

[jinroh]

😕

[nono]

What can we do to avoid the doctype in the JSON?

One possibility is to add a ToJSON() method to our interface and modify JSONDoc to:

type JSONDoc struct {
  DocType string
  Data map[string]interface{}
}

[aenario]

How about

type JSONDoc map[string]interface{}
func (d *JSONDoc) Doctype {
id, ok = d["_id"].(string)
if !ok || id=="" { 
    return ""
}
return id[0:strings.Index(id, "/")]
}

?

[nono]

@aenario and how do you create a new document? You create the id in go, and not on relying on couchdb?

[aenario]

Yep, i did not think this in depth...

Alternatively, we can keep the doctype outside of the structure itself, then we can imagine having two APIs :

1. The full-of-string one for /data API (with Create(prefix, doctype, doc))
2. The go clean one :

type File 
//... 
files = couchdb.Doctype(File.Doctype())
//...
func upload()...{
    files.Create(myFile)
}

[tomsquest]

Why Type is exported since there is DocType() ?

[nono]

We want to specify the type when creating a document that we will save.

[jinroh]

I want to keep this PR simple for now. We can still discuss a change of API or adding the notion of serialization/deserialization later on.

Tell me if its good to merge for you (I'll remove the revert commits).