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 latest version of the Google Cloud Data Loss Prevention v2 API documented is 4.16.0, with multiple previous versions listed ranging down to version 2.15.0.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e is a class within the Google Cloud Data Loss Prevention v2 API, used for defining the frequency at which Cloud SQL table profiles are refreshed.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e class allows users to specify the \u003ccode\u003eRefreshFrequency\u003c/code\u003e for data changes and the \u003ccode\u003eSchemaModifiedCadence\u003c/code\u003e for schema changes in Cloud SQL tables.\u003c/p\u003e\n"],["\u003cp\u003eNew tables are scanned as soon as system capacity allows, while existing tables can have their profiles refreshed at a defined cadence set within this class.\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, as well as inherits from the \u003ccode\u003eobject\u003c/code\u003e base class, with specific methods and properties for its use.\u003c/p\u003e\n"]]],[],null,[]]
