About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Thanks for the update Peter. We will wait for the patch.
It looks like we can accomodate this, not in the next fixpack (YE 2023) but in the subsequent fixpack, Q2 2024.
Hi Peter,
What if the data type in postgres has been definied as TEXT, But the data inside it is of small character length and sensitive??
In such situation Optim is identifying this TEXT as a LOB data and we can't able to apply the masking policies for LOB data
Hi, what kind of behavior would you expect for Text to Varchar if the data is too long to fit in Varchar?