When creating either a Pre or Post Image for use in a plugin, is there a noticeable difference between bringing in all fields to the image vs. selecting only the fields you need?
With the question asked, just a few points/clarifications:
- I would image that moreso than the number of fields, it would be the amount of data in the fields that would have an impact (e.g. a 4,000 char text field would consume more resources than 5 boolean fields).
- I totally understand that 'all fields' is the lazy way to bring fields in (equivalent to 'Select *' in SQL when you only need 2 fields), but unless there is some noticeable impact on performance/resources then the convenience offered is very tempting (as when deploying to customers, there is less configuration work [fields which could be missed] which lowers the chance of mistakes).
I guess what I am asking is what are the practices other CRM developers use when defining the fields for images which are used in plugins? From developing in SQL, I have always avoided 'Select *' in order to remove the added overhead to query execution, so I am curious is the same overhead holds true to plugins. I would imagine, so but I can't really find any concrete information on this.
Thanks in advance.
