You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by Apache Wiki <wi...@apache.org> on 2009/03/21 12:38:17 UTC

[Couchdb Wiki] Update of "Breaking changes" by SvenHelmberger

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The following page has been changed by SvenHelmberger:
http://wiki.apache.org/couchdb/Breaking_changes

------------------------------------------------------------------------------
  This page documents backwards-incompatible changes made during the evolution of CouchDB. While not all such changes will necessarily affect all users, most of them probably will. This page should show you what changed and how you'll need to adapt your code.
  
  == Changes Between 0.8.x and 0.9.0pre ==
+ 
+ === Response to Bulk Creation/Updates ===
+ 
+ The response to a bulk creation / update now looks like this
+ 
+ {{{
+ [
+     {"id": "0", "rev": "3682408536"},
+     {"id": "1", "rev": "3206753266"},
+     {"id": "2", "error": "conflict", "reason": "Document update conflict."}
+ ]
+ }}}
  
  === Database File Format ===
  

Re: [Couchdb Wiki] Update of "Breaking changes" by SvenHelmberger

Posted by Chris Anderson <jc...@apache.org>.
On Sat, Mar 21, 2009 at 1:09 PM, Jan Lehnardt <ja...@apache.org> wrote:
>
> On 21 Mar 2009, at 11:38, Apache Wiki wrote:
>>
>>
>> == Changes Between 0.8.x and 0.9.0pre ==
>> +
>> + === Response to Bulk Creation/Updates ===
>> +
>> + The response to a bulk creation / update now looks like this
>> +
>> + {{{
>> + [
>> +     {"id": "0", "rev": "3682408536"},
>> +     {"id": "1", "rev": "3206753266"},
>> +     {"id": "2", "error": "conflict", "reason": "Document update
>> conflict."}
>> + ]
>> + }}}
>>
>> === Database File Format ===
>
> I'm not sure this change is intentional. Damien, Chris?
>
> I'd opt for a full JSON object. Not all client libs like parsing JSON
> partials.
>

The JSON spec allows objects or arrays as the outer member. http://www.json.org/

As long as it's documented I don't see a problem here.

-- 
Chris Anderson
http://jchris.mfdz.com

Re: [Couchdb Wiki] Update of "Breaking changes" by SvenHelmberger

Posted by Jan Lehnardt <ja...@apache.org>.
On 21 Mar 2009, at 11:38, Apache Wiki wrote:
>
>
> == Changes Between 0.8.x and 0.9.0pre ==
> +
> + === Response to Bulk Creation/Updates ===
> +
> + The response to a bulk creation / update now looks like this
> +
> + {{{
> + [
> +     {"id": "0", "rev": "3682408536"},
> +     {"id": "1", "rev": "3206753266"},
> +     {"id": "2", "error": "conflict", "reason": "Document update  
> conflict."}
> + ]
> + }}}
>
> === Database File Format ===

I'm not sure this change is intentional. Damien, Chris?

I'd opt for a full JSON object. Not all client libs like parsing JSON  
partials.

Cheers
Jan
--



Re: [Couchdb Wiki] Update of "Breaking changes" by SvenHelmberger

Posted by Brian Candler <B....@pobox.com>.
On Sat, Mar 21, 2009 at 05:04:14PM +0100, Sven Helmberger wrote:
>>> + === Response to Bulk Creation/Updates ===
>>> +
>>> + The response to a bulk creation / update now looks like this
>>> +
>>> + {{{
>>> + [
>>> +     {"id": "0", "rev": "3682408536"},
>>> +     {"id": "1", "rev": "3206753266"},
>>> +     {"id": "2", "error": "conflict", "reason": "Document update  
>>> conflict."}
>>> + ]
>>> + }}}
>>>
>>> === Database File Format ===
>>
>> I'm not sure this change is intentional. Damien, Chris?
>>
>> I'd opt for a full JSON object. Not all client libs like parsing JSON  
>> partials.
>>
>> Cheers
>> Jan
>> -- 
>>
>
> This behaviour is also documented as such on  
> http://wiki.apache.org/couchdb/HTTP_Document_API

I made that Wiki change, but only based on observed behaviour.

It's perfectly valid JSON (it's only CouchDB which insists on documents
being JSON *objects*).

Re: [Couchdb Wiki] Update of "Breaking changes" by SvenHelmberger

Posted by Sven Helmberger <sv...@gmx.de>.
Jan Lehnardt wrote:
> 
> On 21 Mar 2009, at 11:38, Apache Wiki wrote:
>>
>>
>> == Changes Between 0.8.x and 0.9.0pre ==
>> +
>> + === Response to Bulk Creation/Updates ===
>> +
>> + The response to a bulk creation / update now looks like this
>> +
>> + {{{
>> + [
>> +     {"id": "0", "rev": "3682408536"},
>> +     {"id": "1", "rev": "3206753266"},
>> +     {"id": "2", "error": "conflict", "reason": "Document update 
>> conflict."}
>> + ]
>> + }}}
>>
>> === Database File Format ===
> 
> I'm not sure this change is intentional. Damien, Chris?
> 
> I'd opt for a full JSON object. Not all client libs like parsing JSON 
> partials.
> 
> Cheers
> Jan
> -- 
> 

This behaviour is also documented as such on 
http://wiki.apache.org/couchdb/HTTP_Document_API

Regards,
Sven Helmberger

Re: [Couchdb Wiki] Update of "Breaking changes" by SvenHelmberger

Posted by Jan Lehnardt <ja...@apache.org>.
On 21 Mar 2009, at 11:38, Apache Wiki wrote:
>
>
> == Changes Between 0.8.x and 0.9.0pre ==
> +
> + === Response to Bulk Creation/Updates ===
> +
> + The response to a bulk creation / update now looks like this
> +
> + {{{
> + [
> +     {"id": "0", "rev": "3682408536"},
> +     {"id": "1", "rev": "3206753266"},
> +     {"id": "2", "error": "conflict", "reason": "Document update  
> conflict."}
> + ]
> + }}}
>
> === Database File Format ===

I'm not sure this change is intentional. Damien, Chris?

I'd opt for a full JSON object. Not all client libs like parsing JSON  
partials.

Cheers
Jan
--