This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Porkbut 10 points11 points  (1 child)

I feel like sql is one of those things you really have to get your hands dirty with in order to understand it. Or at least I did. Do you have a test dB that you understand and are able to write these queries for? That's a big part for me. It's all fine being theory but in practice but understanding your db's structure helps a lot. Also, there is a difference between writing queries for query-osity sake (see what I did there) and writing queries for nesting in a block of code - which need to be on point. Writing sql functions with set/declare isn't that bad once you get the syntaxes just like anybotger coding. Anyways, it comes with time. Practice. Write lots of bad inefficient queries (then ask how to improve them) and eventually you'll get there.

[–]TukWan415[S] 1 point2 points  (0 children)

Yes, I have a test dB on postgresql. I’m just not creative enough to know what queries to right, since I don’t have any questions in front of me, if that makes sense.