Re: Which NoxDB branch today?

I know it sounds confusing, so let me try to explain it:

The *master* branch, was carved out from the IceBreak core where everything
was EBCDIC. This code has been battle-tested for at least two decades and
we know that the "classic" noxDb is very stable.

Today - we have UTF-8 in RPG and the world has changed. We had attempts to
put UTF-8 into the "classic" noxDb, but it was not clean - this brach still
exists as utf-8 but only for reference.

So we created the *main *branch, where the graph itself is in UTF-8 and
everything in that branch works, however it is not battle-tested for more
that two decades.

Also notice that the *main *branch (the UTF-8 stuff) has all the new
features for easy construction of objects and array - ex:

pCustomer1 = nox_Object(
'id' : nox_Int (12345):
'name' : nox_Str ('System & Metod A/S'):
'street' : nox_Str ('Håndværkersvinget 8'):
'city' : nox_Str ('Hørsholm'):
'greeting' : nox_Str (u'4f605978'): // "Ni hau" in unicode
'creditLimit': nox_Dec (76543.21):
'createdDate': nox_Date (%date()):
'createdTime': nox_Time (%time()):
'dateTime' : nox_TS (%timestamp()):
'isNice' : nox_Bool (10 > 1):
'isUS' : nox_Bool ('DK' = 'USA')
);

Let me point to, where the "work in progress" coms in:

- Examples - are not all re-written, the original branch was bloated
with examples. There is a kitch-sink where old-stuff can stay as
inspiration.
- JSON-IN/JSON-OUT dynamic calls of programs with inline PCM. This is a
super advanced feature that is not ported yet. It fails during compilation
and was therefore left out of the service program.

My advice: if you are starting a new project, please go for the *main.* It
is production ready, and we use it for our own projects at clients.

.. i'll put the above in the readme.md

Thank you for your interest - and please keep me posted.





On Mon, Jul 20, 2026 at 9:52 PM Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Says right in the readme...
"However, for any new projects, rather use the "main" branch where
everything is stored in UTF-8 and the prototypes have been cleaned up and
have great new features."

Charles

On Mon, Jul 20, 2026 at 12:45 PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx

wrote:

Hi Daniel,

That’s a great question.

I was thinking of using NOXDB for a project and now I’m confused.

The UTF version is marked as “Work in Progress”.

Not sure that means ready for production.

I posted an issue here to see if Neils will provide some thoughts:

https://github.com/sitemule/noxDB/issues/122

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx

----------------------------------------------------------------------

message: 1
date: Mon, 20 Jul 2026 07:06:16 +0200
from: Daniel Gross <daniel@xxxxxxxx>
subject: Which NoxDB branch today?

Hi,

we're thinking of using NoxDB in our production environment, and as we

are

at the very start, the question is, whether to check out the "master" or
the "main" branch.

If I understand that correctly:

- master uses the json_* and xml_* prototypes and is quite stable

- main uses only nox_* prototypes (by default) and is the future

That means that using master is safe today - but needs migration in the
(near?) future. Whereas main is still in development.

Which one would you recommend today?

TIA and kind regards,
Daniel

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.