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
The POCO date types have their ObjectValue set to string, and will parse the string into a DateTimeOffset every time a something is "done" with the type (e.g. comparing, getting Utc dates, etc). This causes performance issues in the CQL engine, so we should try to cache the conversion from string to DateTimeOffset (invalidating it when the ObjectValue/Value is changed).
The text was updated successfully, but these errors were encountered:
The POCO date types have their
ObjectValue
set to string, and will parse the string into aDateTimeOffset
every time a something is "done" with the type (e.g. comparing, getting Utc dates, etc). This causes performance issues in the CQL engine, so we should try to cache the conversion from string toDateTimeOffset
(invalidating it when the ObjectValue/Value is changed).The text was updated successfully, but these errors were encountered: