3 ms·
I'm going to make an argument here, and you might disagree but that's fine: If you don't understand the purpose of an ORM, you haven't worked on a sufficiently
by debacle 14y ago
I'm going to make an argument here, and you might disagree but that's fine:
If you don't understand the purpose of an ORM, you haven't worked on a sufficiently large enough software project or don't fully understand what the definition of an ORM is.
If you need to write a report of any fashion, do not use an ORM. You can help write the report with your ORM of choice, but at some point you need to get down to the language that the database speaks because you're doing the kind of set mathematics that ORMs aren't made for.
BUT, if you need to add a user permission, and you're doing anything other than:
$user->addPermission( Permissions->get( 'CAN_EAT_CAKE' ) )
you're doing something wrong.
- Philadelphia 14y agoBut that doesn't require or imply an ORM. That's just a matter of having an object model.
- debacle 14y agoIf you have a database, any object model is at some level an ORM.
- stevenwei 14y agoIf your object model at some point gets persisted into a database, then you're going to need to write code to (load from/save to) the database. At which point, if it walks like a duck, and quacks like a duck...