lanto03 / couchdb-python

Automatically exported from code.google.com/p/couchdb-python
Other
0 stars 0 forks source link

Server does not support _uuids method #122

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
CouchDB server offers a possibility to get uuid(s) for the app's use.

The current implementation of couchdb-python does not offer an interface to it.

The following patch provides a possible implementation of two methods:
  * uuids -- direct implementation of a call to a CouchDB server
  * get_uuid -- a possibility to get an uuid for the app's use (this method
obtains a batch of uuids and serves them when necessary)

Original issue reported on code.google.com by mikhail....@gmail.com on 6 Apr 2010 at 8:54

Attachments:

GoogleCodeExporter commented 8 years ago
(This is not a defect but an enhancement)

Original comment by mikhail....@gmail.com on 6 Apr 2010 at 8:55

GoogleCodeExporter commented 8 years ago

Original comment by djc.ochtman on 7 Apr 2010 at 7:49

GoogleCodeExporter commented 8 years ago
I've add Server.uuids() in r25e802498028. I'm not entirely sure about the other 
part
of your patch... maybe that's something the application should take care of? I 
also
added a test case. What do others think about the uuid buffering?

Original comment by djc.ochtman on 6 Jun 2010 at 6:48

GoogleCodeExporter commented 8 years ago
Using server-generated UUIDs probably makes sense so we can take advantage of 
CouchDB's alternative UUID algorithms, e.g. sequential supposedly results in 
more compact databases. It should probably be configurable though.

Original comment by matt.goo...@gmail.com on 16 Jul 2010 at 11:56

GoogleCodeExporter commented 8 years ago
Of course, if you don't supply an id then you get a server-generate one anyway. 
Duh!

Original comment by matt.goo...@gmail.com on 16 Jul 2010 at 12:17

GoogleCodeExporter commented 8 years ago
I'm closing this on the premise that people can buffer on the application side. 
If anyone wants the client buffering, please file a new issue.

Original comment by djc.ochtman on 19 Sep 2010 at 1:19