search

sitemule / noxDB

Not only XML. SQL,JSON and XML made easy for IBM i
MIT License
41 stars 20 forks source link

Numeric 30:15 not quite large enough #79

Closed wimjongman closed 1 year ago

wimjongman commented 1 year ago

We are trying to operate on packed(20:2) numbers that do not fit setNum. Setnum operates on 30:15. Is there a solution other than converting the large number to a string?

Would it be as simple as changing setNum to 40:15?

NielsLiisberg commented 1 year ago

It was for historic reasons;

The max size was the 30

But you can simply do like in examples/JSONPARS2G.JSON-Append-using-NodeAdd.rpgle

pmy20_2 = json_NodeAdd(pNode:json_AFTER_SIBLING:'mybrother': %char(my20_2) : json_LITERAL);

Perhaps not elegant. and you need to have the edit code set to '.' or use %EDIT.

Internal noxDb stores everything in plain char sequence to not have any limitations of sizes nor decimals . ..

.. There will come a version using the new *CONVERT making this go away ...

On Fri, Apr 7, 2023 at 1:03 PM Wim Jongman @.***> wrote:

We are trying to operate on packed(20:2) numbers that do not fit setNum. Setnum operates on 30:15. Is there a solution other than converting the large number to a string?

Would it be as simple as changing setNum to 40:15?

— Reply to this email directly, view it on GitHub https://github.com/sitemule/noxDB/issues/79, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVIPHSZEVJZVOY74JYVJRTW77YA5ANCNFSM6AAAAAAWWOTMTE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

wimjongman commented 1 year ago

Ok, thanks for the hint. I can work with that.