Rewriting own SqlDataMapper classes about opulence HOT 4 CLOSED

@connerbw Fair point. I've created an issue over in the doc repo to do this.

from opulence.

It would be nice to extend the "Basic Usage" documentation though.

I had similar issues starting out. I figured it out but for a first time developer it would be beneficial to show a Post::class code with a corresponding DB table INSERT example to start them off in the right direction.

Then you could add your reasoning why you chose this way (schema is limiting, extending is hard, etc), flesh out the docs a bit more?

from opulence.

The Post class is just a plain-old PHP class. You do not have to implement or extend any interface/base class. The issue with trying to have the ORM auto-write queries for you is that it assumes a certain DB schema, which I find to be very limiting to the developer. If your tables/entities are very simple and you'd like that auto-wiring support, I'd recommend an active record ORM.

from opulence.

@evolic I'm going to mark this closed because I've created an issue in the documentation repo to better explain the design choices behind the data mapper.

from opulence.