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 problem is, we don't really have a useful abstraction that we could use in such a callback.
At that stage we are dealing with ResultSet which is way to complex and fiddly for this purpose.
It has multiple ways of accessing a column (by index, by name, with specified type or just as getObject) and it includes traversal controls.
Of course we could wrap it in a simpler interface, but this wouldn't allow actually changing the data since all the other infrastructure works on ResultSet.
What we can do is have an additional AfterLoadWithResultSetCallback(*) interface that will take an entity and a wrapped ResultSet.
If will be called after construction of the entity but allows to extract additional data from the ResultSet
This allows to have custom queries with additional columns that by default don't get used for construction of the entity but maybe used in post processing.
Also #1006 might be of interest to you since it will allow to completely control the construction of entities.
(*) that name is just proposal and will not be the final name. See #1053.
May I Have
BeforeLoad
Entity Callback to use encrypt string to queryNow I have
AfterLoadCallback
to process something about decryption.The text was updated successfully, but these errors were encountered: