The JADE 2022 release meets tomorrow’s business demands.
John Munro
|
HistoricalComments
Julie Harliwich 10/10/2017 10:41:43 AM
If we could nominate a map file as being for Persistent classes only, or Transient classes only then it would reduce the mistakes. Kevin Saul 27/09/2017 3:21:07 PM Nor are map files needed for exclusive collections, (provided the persistent option isn't set for shared objects). We've got quite a lot of clutter in this regard. In the past, we've tried to remind each other to leave the map file blank when it isn't needed, but it tends to be left at the default. It'd be better if the map file field was disabled when it isn't actually needed, and cleared when changes are saved such that it isn't required anymore. To tidy up existing classes and delete redundant map files from our production systems, we'd ideally be able to handle resetting the map file for a class via schema load somehow. We've tried to find a way to do this before, with no luck (https://forums.jadeworld.com/viewtopic.php?f=9&t=2002). Blake De?Ath 27/09/2017 3:17:01 PM Also to consider, a map file cannot be removed for these classes via a JFC or an extract file, at least the last time I tried. |
