Closed TomHAnderson closed 12 years ago
My thought is that you should still implement the user interface at minimum in a custom user entity to ensure that that the mapper will behave as desired.
I'm starting to think along the same lines and perhaps this module is best served using it out of the box instead of with custom entities. This means I need to wrap my database diagram around your user_id conventions vs key and ref which are easier to read and query IMHO. At any rate I'm now down to trying to implement this out of the box.
The more I use this module the more I think it has to be a cornerstone of your project so you can make your project work with it. I had tried to drop it into an existing diagram.
Well, keep in mind that we definitely do want to support custom entities and have that be a fully supported workflow. By no means to I want to lock everyone into using the entity we provide out of the box. I just think it's best for everyone if we keep the custom entities at least compatible with the interface so that they'll behave in a somewhat predictable manner.
Closing now -- I don't think there is an issue here.
By type casting the entity class you cannot use a custom doctrine entity.