We try to avoid using Entity/record directly, as it is rare that we actually need all the fields of a row, so it hurts performance significantly to send them over every time.
There are a few places that this has been difficult to do, for example upsert. This function would be very useful, but we currently avoid it due to the overhead.
For this reason I would greatly appreciate non-Entity/record equivalents of various functions that return Key or even ().
For read operations I can understand Entity/record being the default, in which case perhaps a Key suffix or similar could work for getting just the Key.
For write operations I personally think having Key be the default makes sense, with an _ suffix for (), and an Entity suffix for Entity. For backwards compatibility reasons I can understand taking the Key suffix approach even if it will be a little inconsistent with existing write operations like insert.
We try to avoid using
Entity/recorddirectly, as it is rare that we actually need all the fields of a row, so it hurts performance significantly to send them over every time.There are a few places that this has been difficult to do, for example
upsert. This function would be very useful, but we currently avoid it due to the overhead.For this reason I would greatly appreciate non-
Entity/recordequivalents of various functions that returnKeyor even().For read operations I can understand
Entity/recordbeing the default, in which case perhaps aKeysuffix or similar could work for getting just theKey.For write operations I personally think having
Keybe the default makes sense, with an_suffix for(), and anEntitysuffix forEntity. For backwards compatibility reasons I can understand taking theKeysuffix approach even if it will be a little inconsistent with existing write operations likeinsert.