The JADE 2022 release meets tomorrow’s business demands.
Guest
|
HistoricalComments
Ty Baen-Price 13/11/2018 12:12:35 PM
Loading into current version should not be a default behaviour because it's dangerous. You might want to use it (under advisement) in your development environment (or to hotfix a production environment), but if anyone is relying on the behaviour of running applications, you will, at best, confuse them, and at worst, waste their time or ruin their data. You know you can unversion a versioned schema? Brian Johnstone 17/10/2018 3:03:09 PM Further to @Blake's comment, assuming the schema(s) were not versioned prior to the load, you could potentially avoid the 'unnecessary' reorg by unversioning the schema(s) and then redo the schema load with the loadstyle set to currentSchemaVersion. Blake De?Ath 17/10/2018 10:53:00 AM The load style options can already be manipulated, including completely removing options, with INI settings. Have a read of the following: https://www.jadeworld.com/docs/jade-70/Default.htm#resources/jadeini/jade_start-up_section_[jade]/loadstyledefault.htm https://www.jadeworld.com/docs/jade-70/Default.htm#resources/jadeini/jade_start-up_section_[jade]/loadstylesecond.htm https://www.jadeworld.com/docs/jade-70/Default.htm#resources/jadeini/jade_start-up_section_[jade]/loadstylethird.htm |
Hi Sam, I am just reviewing some old JEDIs, and given the dialog on this one can I close it? Thanks John R.