× 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.



Hi,

the bug is already fixed, but I do not know if it is already a official PTF.
I recently talked with Scott Forstie. The easiest way to get the PTF is to
open a PMR and point to Scott Forstie.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Craig
Richards
Sent: Samstag, 30. Dezember 2017 00:34
To: rpg400-l@xxxxxxxxxxxx
Subject: New JSON Publishing functions - bug with JSON numeric types?

Hi All,

I was hoping to use the new JSON Publishing functions in a current project.
I've installed the relevant TR and have access to the new functions, which
mostly seem very good.

However, it seems to me that there is a bug in the json_object() function.

To illustrate - here is some sql which tries to build a json object in two
ways - in t1 it is using the new json_object() function and in t2 I've just
built it manually.

What I expect is: {"amount":0.5}
but what json_object is giving me is: {"amount":.5} i.e it is not inserting
the 0 before the decimal point.

I also use the IS JSON predicate to indicate that the json object built by
json_object() is not valid JSON:

with t1 as (
select 'auto' as coltype, json_object( 'amount' value 0.5 ) as data from
sysibm/sysdummy1) ,
t2 as (
select 'manual' as coltype, '{"amount":0.5}' as data from sysibm/sysdummy1)
select coltype, data, case when data is json object then 'Y'
else 'N'
end as validjson
from t1
union all
select coltype, data,
case when data is json object then 'Y'
else 'N'
end as validjson
from t2;

This yields:
-- COLTYPE DATA VALIDJSON
-- auto {"amount":.5} N
-- manual {"amount":0.5} Y

Am I missing something or is this a bug?
Any advice on how to report this?
I would much prefer to use these functions to build my json objects but my
project has some pretty tight deadlines.

Thanks and best regards,
Craig
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.