As suggested by srjfoo. I agree with her that it's better to fail loudly rather than silent ignore unrecognized fields. If nothing else, it helps when a dev makes typos in client code.
I needed to do some code reorg to avoid repeating a subset of SQL column names and API field names for a third time.
As suggested by srjfoo. I agree with her that it's better to fail loudly rather than silent ignore unrecognized fields. If nothing else, it helps when a dev makes typos in client code.
I needed to do some code reorg to avoid repeating a subset of SQL column names and API field names for a third time.
Sandbox at https://www.pgdp.org/~bfoley/c.branch/invalid-field but it doesn't touch any non-API code.
Example call: