Hi,
we are working on enhancing this so nightly build will expose db version.
Also, once you get a nightly build downloaded, I guess the quickest way to check if there's a new DB version is to check the monox/installer/sql/updatescripts to see if there are newer folders, correct? (sorting alphabetically btw is bound to break when you go from one digit to two digit fields in some sections of the version number btw - and sorting by date will mean that if some older update script is fixed in the future it will show at wrong order in the list)
I wan't able to reproduce this, could you give us more details ?
e.g. MonoX_4_7_40_3598 (Beta) that we had been given reports database 4.5.3103 that fails to upgrade twith the next version script, since if you look at the .zip file with that version the upgradeScripts folder has subfolders up to version 4.7.40.3540, so the database should be that version, not 4.5.3103 as it erroneously reports
We will expose the full log in next nightly build.
Also at the top of the nightly build page it would be nice to have a "Complete Change Log" (from as far in the past you can) download. That way one can search in there
Yes that's true.
BTW, I hope we're supposed to choose with upgrade scripts to run based on the db version and not the MonoX platform version (this is not very clear)
Thanks for the feedback.