> Even if OOP really were a great way to model your data, to express relationships and property types and such, it's all just going to end up in a database anyway.
Of course. But when you operate on it. When you end user is typing into a screen. When you're validating the contents. You're doing in the application, not in the database. RAM is where the data lives when it's being acted on.
It's like saying your Word processor should have no internal data structures different from how the file stored on disk.
OOP is a great way to model data sotred in RAM and operated on. And an ORM is a great tool for persisting that structure to disk as needed.
Of course. But when you operate on it. When you end user is typing into a screen. When you're validating the contents. You're doing in the application, not in the database. RAM is where the data lives when it's being acted on.
It's like saying your Word processor should have no internal data structures different from how the file stored on disk.
OOP is a great way to model data sotred in RAM and operated on. And an ORM is a great tool for persisting that structure to disk as needed.