×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Greg,
You can configure YAJLINTO to put any value you like into a null field
by specifying the "value_null" option to the parser. To make it blank,
just pass an empty string:
%PARSER('YAJLINTO': '{ "document_name": "doc", "value_null": "" }');
As for how this is "normally" handled, its normally handled by mapping a
string of *NULL to the field. The problem with blanks is that you can't
tell the difference between a field that was set to null, and a field
that was set to blank, and in many applications the difference does
matter. Since it's not possible for a DATA-INTO parser to set a
field's null indicator, it passes the special value of *NULL that your
code can look for.
But, if you want something else, such as blanks or zeroes, all you have
to do is specify the value_null option, as shown above, and specify the
appropriate string.
Good luck
-SK
On 6/19/2019 2:19 PM, Greg Wilburn wrote:
I apologize if this question is not appropriate for this mailing list...
I'm using YAJLINTO to load JSON into my data structure... In some of the elements I'm gathering, the element literally contains "null". Sometimes it contains "". YAJLINTO converts this to "*NULL" (that ends up in my DS fields).
Example:
"SellerOrderID": null,
In my DS field SellerOrderID (char(128)) contains *NULL
Since I'm using mostly all character definitions, I was wondering how to handle this.
Is there option with YAJLINTO to convert "null" to blank instead of "*NULL", or do I need to look for "*NULL" in each field before loading the data into my database files?
How is this normally handled?
Thx,
Greg
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.