Closed hfaulds closed 8 years ago
Unless I'm missing something this just gives up on resolving the value and returns the encoded value instead, right? That might be better than nothing in some cases, but I wouldn't imagine this fixes all cases where we use compact-decoded.
This seems abandoned and I think was at least partially fixed by https://github.com/estately/rets/pull/163, so I'm closing for now. Let me know if you disagree.
We've had some problem mlses where we had to use the
COMPACT-DECODED
format (which is significantly slower to fetch) because when usingCOMPACT
and 'resolving' the values using the metadata we had fields with missing values.I've tried multiple times to see if I could get thngs working using
COMPACT
.This fix appears to work though.
For a single property I fetched 3 times, once with compact_decoded, once with compact and once with this new change: