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
From the docs around property handlers, you have this example:
What would be incredible is for RepoDB in the background to hold the backing string on the POCO on retrieval. Only when the property is first accessed, is the property handler run (i.e deserialized). In this way you defer the cost of the property handler for when it is first used, and thereafter the object is set.
The text was updated successfully, but these errors were encountered:
Hmmm, interesting proposal. Definitely, it will improve the perf specially if property handler is doing an extensive operation. We will look how this is possible with the existing implementation we had, most likely not due to PH dependency to the connection.
Describe the enhancement
From the docs around property handlers, you have this example:
What would be incredible is for RepoDB in the background to hold the backing string on the POCO on retrieval. Only when the property is first accessed, is the property handler run (i.e deserialized). In this way you defer the cost of the property handler for when it is first used, and thereafter the object is set.
The text was updated successfully, but these errors were encountered: