Liking any of these indicates a belief system I don't agree with
Liking any of these indicates a belief system I don't agree with
You're viewing a single thread.
- ORM's
- Place ALL of the business logic in stored procedures.
- Eliminate the backend.
- Make the front end connect directly to the database.
Profit- Introduce tons of bugs and terrible performance.
- Database is compromised within five minutes of going live.
I'm confused. Are you saying all of that is a consequence of not using ORMs? Because if so, that's absolutely not true. ORMs truly are complete trash.
Sounds like you were hurt by an ORM.
One huge benefit of an ORM is that it does type checking. it makes sure your tables exist, relationships are valid, etc, and it makes easy things easy. If you add a column, it'll make sure it gets populated, give you decent error messages, etc.
As long as you use a proper repository pattern setup and isolate DB interactions from the rest of the code, how you construct the queries is completely up to you. I try to use DTOs to communicate w/ the repo layer, so whether an ORM is used or direct SQL queries is largely an implementation detail.
https://github.com/launchbadge/sqlx
Not an ORM, but uses Rust's compile time macros so you can write raw SQL and it will type check everything against either a real database connection or a JSON cache of the database's schema.
Absolute best of both worlds.
That sounds really nice, I'll have to check it out.
I have for years been pumped to create a sql only side project or sql + frontend
Please don't. I self-host actual budget, and they compile SQLite to WASM to use it in the FE. That just feels... wrong.
There are some other options as well: https://youtu.be/3JW732GrMdg