[ 
https://issues.apache.org/jira/browse/COUCHDB-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Shorin closed COUCHDB-2277.
-------------------------------------

    Resolution: Not a Problem

{{key}}, {{startkey}} and {{endkey}] must have a valid JSON value. That's the 
requirement, because view index is built on JSON values - so you must provide 
the valid one to let CouchDB walk through index correctly.

> Bad unuseable Rest-API
> ----------------------
>
>                 Key: COUCHDB-2277
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2277
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Manfred Quasten
>
> 1. A key must be given with ?key="key" without " it will not work
> http://localhost:5984/petstore/_design/qualityByArtist/_view/qualityByArtist?key=%22nicole%22
> Using google maps will work, with and without "
> http://maps.googleapis.com/maps/api/geocode/jsonaddress=Magadan&sensor=false
> 2: a) AcomposedKey must be given as json ?! that is nearly not testable in a 
> browser and for me the only way is to use curl
> b) I think giving a content in rest will normaly be use post and give it in  
> body, this I've never seen before ....
> http://localhost:5984/petstore/_design/pricePerUnit/_list/quantityFilter/pricePerUnit?key={%22quality%22:%22platinium%22,%20%22unit%22:%22date%22}&quantity=3
> 2c) when I use 
> key={"unit":"date"}  , "quality" : "platinium"}   use unit at first and 
> quality as second" , nothing will be found.  I think,  why maps, it seams to 
> work like an array , are maps fake ? It seam not that they will work in a 
> correct way. Using java my workaround is using LinkedHashMaps and putting it 
> in the right order into it and after this I serialize it to json an give it 
> to springs resttemplate ...  I will be rembered  to petClinic, because pet 
> will get ill from bad  JavaEE, may be that this isn't good for pets too ... 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to