I hate motherfucking SQL.

Feel this - trying to figure out rn why my .bacpac is not importing on sqlpackage docker container, but it’s importing no problemo on SSMS in my VM. And the error messages are like “something went wrong - operations not supported” and then it proceeds to spout error messages that aren’t even helpful??? I’m going to break something I swear.

Just use non-motherfucking SQL then.

Whats the problem with it?

Yes it can be hard but thats because databases with performance is a hard problem and SQL has proven to be one of the overall best ways to solve this unless you go with multiple different DB’s but that adds another can of worms of complexity believe me :)

@chonky-quiche ot is permissions, or user ownership issues.
If possible, always import the file explicitly, instead of putting it in the user home directory.

Why arent you using an object relational mapper then?
ORM libraries are the new hotness.
SQL is socks with crocs.

@Wisecrack ORMs still translate to SQL in the background. Some knowledge of SQL will save you from asking very dumb SO questions like "Why does my favorite ORM not work like I expect it to?"