#274 new
Bob Aman

dm-couchdb-adapter relies on abnormal naming scheme

Reported by Bob Aman | May 11th, 2008 @ 03:05 PM | in 1.x

Right now, the dm-couchdb-adapter expects a User resource to have a corresponding users database in CouchDB. This is very strange. This is what a typical CouchDB database looks like (taken from the Ajatus CRM):

4c480f9453cc31c017241ab61d0e334c
66a500d4ab151613fbb9a808ace9e21a
92a28dd10796ddbfc4de273f11e815a4
E16902809F2021F5397D64D0B0322310
_design/contact
_design/event
_design/expense
_design/hour_report
_design/note
_design/tag

In this example, there is 1 contact (E169028...) in the DB with 3 tags (4c480f9..., 66a500d4..., 92a28dd...).

Essentially, document type is determined by the internal structure of the document (typically by checking the _type property), not by which database it's in. CouchDB's not exactly a table/row based database. :-) The dm-couchdb-adapter really needs to be completely rewritten to be more flexible. I'll happily volunteer to take responsibility for this, assuming there's agreement that the change needs to happen.

Comments and changes to this ticket

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket

Tags