Question
Cost performance of unoptimized property vs optimized with DataType modification
Hello dear Community,
I'm using Pega 7.3/7.4 and I have a question considering property stored in DataBase.
the context : I need to get a property through a report. This property references the base 64 code to display an pdf and is natively unoptimized. The thing is that this property can contain a very long string (like a length of 270,000 characters). But if I optimize this property, the DataType in DataBase will be in VARCHAR(32).
So here are my few questions :
- Is it possible to optimize a property and then change its Datatype to something able to contain all the information ?
- If it is possible, does changing the datatype deoptimize my property ?
- Finally, what what will be more expensive in term of perfomance : an unoptimized property in the BLOB or an optimized property but with a modifier DataType ?
Best regards,
Kevin.
***Edited by Moderator Marissa to update platform capability tags****
To avoid significant impact on performance, I would suggest not to retrieve that much information through report. As you haven't explained your use case and you want to use report def to retrieve data, so I assume you would be showing all such records on a tabular format (grid, repeating section). I would suggest to use Report def to retrieve only the pzInsKey of the instance that holds that property, and render it as URL on UI. On click event on that URL, open the instance using Obj-Open and retrieve that property and render its content as per your requirement.
This on-demand retrieval of that attribute (actually the instance that holds it) would reduce network traffic and performance of report def.