There are solid reasons why we don't do this. Just to name one: a single database table rarely holds the information you need, and is even less likely in the way you want the user to see it.
It's orthogonal, in my view. You can integrate UI, business logic, and storage without forcing everything to be one table.
You can, of course, have multiple tables in your app. Moreover, you can decouple the UI schema from the table schema. But if you can put it all in one schema, why not?
3 comments
[ 3.6 ms ] story [ 259 ms ] threadI just put together a quick demo of a CRUD web app in just 65 lines of code.
Sure, this is a pretty simple app, but I feel that the integration between UI, storage, and business logic is starting to pay off.
There are solid reasons why we don't do this. Just to name one: a single database table rarely holds the information you need, and is even less likely in the way you want the user to see it.
You can, of course, have multiple tables in your app. Moreover, you can decouple the UI schema from the table schema. But if you can put it all in one schema, why not?