I have a table that stores an encrypted password in one of its columns. I'm using an Adapter scenario, with a server that handles data fetches and sends the data to the client using fast binary serialization.
The password needs to be accessible in the server application (so I need to include the column in my entity), but I don't want to send the field to the client, since the client does not need it.
I'm trying to figure out the best way to accomplish this with the llblgen entities. I thought about using a field filter to exclude this field whenever I do fetches on behalf of the client, but it seems like it would be difficult to enforce the use of the filter everywhere a fetch might load the object.
Is there a way to prevent llblgen from serializing this one field? Would I need to override SerializeOwnedData and DeserializeOwnedData to write/read all values except the password, without calling the base's methods?
Or does someone have a better idea on how to accomplish this goal?