• State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 96 subscribers
  • Views 3533 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New Configuration Parameter in V8 now forces a compile needed?

aszeto

Hi,

We've noticed in version 8 (8.0.2) that adding a new configuration parameter initiates a DB compile required, whereas version 7 did not.  Is there a way to disable this?

Thanks!

Parents
  • 0

    Does your new configuration parameter contain a set pre-processor condition?

    When did you observe this behavior, during transport or while creating it with the Designer?

  • 0 in reply to Markus Weiss-Ehlers

    We've noticed it both in an scripted process that creates a new configuration parameter, and also directly creating a brand new one in Designer

  • 0 in reply to aszeto

    What about the question in regards to the pre-processor condition?

  • 0 in reply to Markus Weiss-Ehlers

    There weren't any pre-processor conditions added on the configuration parameter, if I only go and right-click add a new custom/TargetSystems/BLAH1 with value 1 and enable it, committing it to the database causes the compile...  I did not modify/add/remove any preprocessor conditions, although there appears to be many default ones checked... could it be inheriting it from the main "custom" level or "TargetSystems" level?

  • 0 in reply to aszeto

    The preprocessor conditions will not be inherited. And as you have written, that you created the configuration parameter underneath "Custom" the ootb ones shouldn't be an issue at all.

    I am going to take a look at it.

    But I already found that some holes and timing issues in regards to transporting data containing configuration parameters, new tables, and typed wrapper scripts as well as in regards to configuration parameters have been fixed on the way to 8.0.2 so maybe that's the reason for the seen behavior.

Reply
  • 0 in reply to aszeto

    The preprocessor conditions will not be inherited. And as you have written, that you created the configuration parameter underneath "Custom" the ootb ones shouldn't be an issue at all.

    I am going to take a look at it.

    But I already found that some holes and timing issues in regards to transporting data containing configuration parameters, new tables, and typed wrapper scripts as well as in regards to configuration parameters have been fixed on the way to 8.0.2 so maybe that's the reason for the seen behavior.

Children