SQL or No SQL?

Your data should dictate that, not a random internet persona.

Depends on the data. Depends on the app. Depends on the availability requirements. Depends on the scalability requirements. Depends on the database engine. Depends on the persistence model. Depends on a bunch of things that you need to research to accurately gauge this question.

Computer science is hard. You can't reduce it to inane questions like "SQL or noSQL?"

SomeSQLPerhaps

Screwdriver or hammer?

Go with OQL

@C0D4 What if it's one of us, though? It's good in that case, no?

"That is the question"

@react-guy geez you beat me to It 😁😁😁

Most projects I encountered work fine with MySQL and you can shoe-hammer a NoSQL database into it as well. I've seen it with a project which wanted NoSQL just to have it (because it's shiny new shit). And then implemented foreign keys and other constraints with the Model class as beforeInsert() hooks.

True

U mad or u nomad?

Of all the things it could be called, NOSQL is the worst. The name contradicts itself.

neither, storing all relevant information in your head, like a true madman, for everything, even your users

Big fan of redis as a backend for desktop helper stuff.

@AleCx04 post-it notes 🤔 this gives me an idea 💡 PINQL

It depends on the situation