Skipping pre-populated query fields like Shot.OpenNotes

[patrickwolf]

Some query fields like Shot.OpenNotes are returned by the regular shotgun API and because of it do not actually need to be queried again as query fields ie reducing overhead. All that might be needed is a check if the field is != None and then skip get the field value again.

Thanks
Patrick

[ksallee]

I'm not sure how this could be fixed other than either something in the schema that allows to know that it's actually returned, or a hardcoded list of fields. We could check that at least one of the entities returned have data in this field, but the opposite (all to None) wouldn't mean we need to skip it.

It could still work most of the time, in which case the test for this could be done here:

fpt-api/python/fpt_api.py

Line 572 in b49d30a

requested_fields = set(fields)

and here for dotted query fields:

fpt-api/python/fpt_api.py

Line 848 in b49d30a

Since I don't have access to any SG instance to test this I can't really implement it blindly unfortunately.