MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Show DB version at nightly build  (Mono Support )

Viewed 12298 time(s), 4 post(s) 2/13/2013 7:42:49 AMby Zoomicon
Zoomicon

Zoomicon

2/13/2013 7:42:49 AM
Currently at nightly builds, one can't compare between versions quickly (without downloading them first) to see if the database schema version shipping with them has changed (that is if they need to do extra work running the monox/installer/sql/updatescripts from one version up their current one to the latest version).

I'd expect the webpage to list the db version too.

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)
This content has not been rated yet. 
2793 Reputation 345 Total posts
Zoomicon

Zoomicon

2/14/2013 12:12:34 PM
Also, some versions seem to be reporting at the admin bar a wrong Database version.

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

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)
This content has not been rated yet. 
2793 Reputation 345 Total posts
Zoomicon

Zoomicon

2/15/2013 8:39:42 AM
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
This content has not been rated yet. 
2793 Reputation 345 Total posts
khorvat

khorvat

2/15/2013 1:43:39 PM
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.
This content has not been rated yet. 
15993 Reputation 2214 Total posts