search

sitemule / noxDB

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

noxDB vesrsion seems to be missing #89

Open krka01 opened 3 weeks ago

krka01 commented 3 weeks ago

Hi,

I can not find any form of versions in noxDB. I think there is a need for some kind of version description.

Thanks

NielsLiisberg commented 3 weeks ago

noxDb ( and ILEastic and ILEvator) has a promise to always be backward compatible. Therefore the version is more or less the git commit. So always pull the main branch.

On Mon, Sep 2, 2024 at 12:55 PM Krister Karlsson @.***> wrote:

Hi,

I can not find any form of versions in noxDB. I think there is a need for some kind of version description.

Thanks

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

krka01 commented 3 weeks ago

@NielsLiisberg Thanks for the reply. I do understand what you are saying.

We have starting to explore the possibilities with noxDB at my company, but a concern have been raised how we can identify which version we have installed on every single IBM i partition.

Besides the built date, the only way I have found to identify this, is be looking at the COPYRIGHT_STRING with the SQL service QSYS2.PROGRAM_INFO as it have the git checkout commit listed there.

Is there any other, better way to identify the installed version?

The only concern I have with using the git commit as a version, is that you can not tell by just looking at the commit string to differentiate which is newest without heading to the sitemule/noxDB commits and search for them.

NielsLiisberg commented 3 weeks ago

You are all correct Krister,

We actually use the commit id as you describe and trawl the repo with "git graph" in cases where we need to check out a specific version and reproduce a customer issue. It has been the most effective and precise way to handle versions.

We might consider adding a version tag, however, that will be something like the 1.1.date-time, which gives you not much more info. Versions run fast from time to time, so for now we have found the commit id is much more efficient. But still, you have the object date if you run:

DSPSRVPGM SRVPGM(NOXDB/JSONXML) DETAIL(*MODULE)

However, I will discuss it with the team.

https://github.com/mhutchie/vscode-git-graph

On Tue, Sep 3, 2024 at 1:26 PM Krister Karlsson @.***> wrote:

@NielsLiisberg https://github.com/NielsLiisberg Thanks for the reply. I do understand what you are saying.

We have starting to explore the possibilities with noxDB at my company, but a concern have been raised how we can identify which version we have installed on every single IBM i partition.

Besides the built date, the only way I have found to identify this, is be looking at the COPYRIGHT_STRING with the SQL service QSYS2.PROGRAM_INFO as it have the git checkout commit listed there.

Is there any other, better way to identify the installed version?

The only concern I have with using the git commit as a version, is that you can not tell by just looking at the commit string to differentiate which is newest without heading to the sitemule/noxDB commits and search for them.

— Reply to this email directly, view it on GitHub https://github.com/sitemule/noxDB/issues/89#issuecomment-2326279142, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVIPHRSFMHUZ7IUWC2SYY3ZUWMG7AVCNFSM6AAAAABNQCRM6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRWGI3TSMJUGI . You are receiving this because you were mentioned.Message ID: @.***>

krka01 commented 2 weeks ago

@NielsLiisberg I think it should be sufficient if you could also append the date and time for the git commit in the copyright string.

NielsLiisberg commented 2 weeks ago

This sounds like a great idea. Will do!!

man. 9. sep. 2024 kl. 09.00 skrev Krister Karlsson @.***

:

@NielsLiisberg https://github.com/NielsLiisberg I think it should be sufficient if you could also append the date and time for the git commit in the copyright string.

— Reply to this email directly, view it on GitHub https://github.com/sitemule/noxDB/issues/89#issuecomment-2337192877, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVIPHQBEACVZ4V26542C5LZVU2OPAVCNFSM6AAAAABNQCRM6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZXGE4TEOBXG4 . You are receiving this because you were mentioned.Message ID: @.***>