Because the ResourceTreeServicePostgreSQL can receive a custom model (as long as it implements same fields structure as Resource), it is possible to reuse this tree and all its useful methods for other similar tables.
I employ this in my repo to sync Resource (local) against RemoteResource that derives from Resource.
This fix retrieves the field by name of the model class instead of hardcoded auto0generated attribute named like default Resource model.
Because the
ResourceTreeServicePostgreSQL
can receive a custom model (as long as it implements same fields structure asResource
), it is possible to reuse this tree and all its useful methods for other similar tables.I employ this in my repo to sync
Resource
(local) againstRemoteResource
that derives fromResource
.This fix retrieves the field by name of the model class instead of hardcoded auto0generated attribute named like default
Resource
model.