Data changes (non-schema changes) in Cloud SQL tables can't trigger
reprofiling. If you set this field, profiles are refreshed at this
frequency regardless of whether the underlying tables have changed.
Defaults to never.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe webpage provides documentation for the \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e class within the Google Cloud Data Loss Prevention v2 API, specifically version 4.11.0.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e is designed to manage how often existing Cloud SQL table profiles are updated, with new tables being scanned promptly.\u003c/p\u003e\n"],["\u003cp\u003eThe class implements several interfaces, including \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, and inherits from the \u003ccode\u003eobject\u003c/code\u003e class.\u003c/p\u003e\n"],["\u003cp\u003eIt offers two main properties, \u003ccode\u003eRefreshFrequency\u003c/code\u003e to define how often to refresh profiles regardless of changes and \u003ccode\u003eSchemaModifiedCadence\u003c/code\u003e to define the behavior when schema changes are detected.\u003c/p\u003e\n"],["\u003cp\u003eThe webpage contains a list of available versions of the \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e class documentation, ranging from version 2.15.0 up to the latest version 4.16.0.\u003c/p\u003e\n"]]],[],null,[]]
