2 edited body
source | link

Well I suppose that you could use an ORM.

But really, database design should NOT follow OOP priciples, it should follow database design priciples such as normalization. And it should be designed at the database not in the application. And the data integrity rules shoudlshould be enforced at the database level not by the application.

I would suggest you read some database design books and, then, read about performance tuning the database of your choice.

Well I suppose that you could use an ORM.

But really, database design should NOT follow OOP priciples, it should follow database design priciples such as normalization. And it should be designed at the database not in the application. And the data integrity rules shoudl be enforced at the database level not by the application.

I would suggest you read some database design books and, then, read about performance tuning the database of your choice.

Well I suppose that you could use an ORM.

But really, database design should NOT follow OOP priciples, it should follow database design priciples such as normalization. And it should be designed at the database not in the application. And the data integrity rules should be enforced at the database level not by the application.

I would suggest you read some database design books and, then, read about performance tuning the database of your choice.

1
source | link

Well I suppose that you could use an ORM.

But really, database design should NOT follow OOP priciples, it should follow database design priciples such as normalization. And it should be designed at the database not in the application. And the data integrity rules shoudl be enforced at the database level not by the application.

I would suggest you read some database design books and, then, read about performance tuning the database of your choice.