Hi Gnanaprakash,
We're puzzled a little as it seems that this should not have happened
with the way the REST API is designed.
How did you ingest the documents? We're collectively of the opinion
that if you insert
{"id":1}
That it should come back out of the database the same way, not as a
string. If that's not the case then it might be a bug.
Charles
On 12/20/2012 11:40 PM, [email protected] wrote:
> Hi Charles Greer,
>
> I inserted a new schema into my Schema database and updated all my content in
> my Content database to map schema.
>
> For handling data types, having a schema is the best approach as there won't
> be any need to think about new elements being added to the content (we can
> just update the schema to reflect the changes).
>
> Having said that, I still believe we should have an option to customize the
> data types for elements (similar to what we have for array-element-names
> which is used to force elements to be as an array in JSON).
> The main reason for me in asking this is, most of the cases we will be
> writing our custom code to have response in our required format where we
> can't enforce schema. In these cases we need to have the above options.
>
> Regards
> Gnanaprakash Bodireddy.
>
> Message: 2
> Date: Thu, 20 Dec 2012 09:56:28 -0800
> From: Charles Greer <[email protected]>
> Subject: Re: [MarkLogic Dev General] MarkLogic 6 XML to JSON DataTypes
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Gnanaprakash, Dave,
>
> On 12/20/2012 01:51 AM, [email protected] wrote:
>> Meanwhile, I tried using schema for handling data types and it's working
>> perfectly.
>>
>>
> I'm really glad to hear that -- I've been really puzzling over the best
> response to your issue. Did this involve inserting a schema that defined,
> the json:id XML element as numeric? I'm curious how much you felt as though
> you were peeling the JSON black-box open.
>
> It seems as though using datatypes, rather than some transform, is a better
> approach to your issue. How important is JSON customization in light of that?
>
> Thanks for your input,
>
> Charles
>
> --
> Charles Greer
> Senior Engineer
> MarkLogic Corporation
> [email protected]
> Phone: +1 707 408 3277
> www.marklogic.com
>
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. If you are not the intended recipient(s), please reply to the
> sender and destroy all copies of the original message. Any unauthorized
> review, use, disclosure, dissemination, forwarding, printing or copying of
> this email, and/or any action taken in reliance on the contents of this
> e-mail is strictly prohibited and may be unlawful.
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
--
Charles Greer
Senior Engineer
MarkLogic Corporation
[email protected]
Phone: +1 707 408 3277
www.marklogic.com
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
