Small refactoring in entity config

[Jonathan Leibiusky]

Hi!

So I'm fixing some small issues with the inheritance support that I added. The problem that I usually run into is related to how the code is implemented.

The OutletEntityConfig is being used to know which columns to select from DB. I think we should separate that from the actual properties. So we should have a class that holds information of properties of the class and another class that holds which columns to select when loading that class. That will make out lives easier to extend outlet for multiple inheritance strategies, etc.

It could be something like OutletEntityMapper.

So when building SQL queries we would use the OutletEntityMapper for the class that we want to load, and to hydrate we will use the OutletEntityConfig of the class that we want to load.

What do you think? I could do the refactoring with my inheritance changes.

Jonathan