You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was added in #395 but then the test it was added for was later remove d in #560, so it's not currently being used. And it's not documented anywhere for customers to be able to use themselves.
Do we need this caching at all? Can we refactor the bindings to get all the column info for a table and be fine with that never changing for the lifetime of the function? (we already say that changes to the table while a function is running may have unexpected behavior)
If we do keep it, we should consider moving the parsing logic out of the UpsertRowsAsync method. We only need to calculate the value once at startup - so calculating it each time an insert is done is just wasted effort.
The text was updated successfully, but these errors were encountered:
This was added in #395 but then the test it was added for was later remove d in #560, so it's not currently being used. And it's not documented anywhere for customers to be able to use themselves.
Questions we should ask:
If we do keep it, we should consider moving the parsing logic out of the UpsertRowsAsync method. We only need to calculate the value once at startup - so calculating it each time an insert is done is just wasted effort.
The text was updated successfully, but these errors were encountered: