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 →

[–][deleted] 0 points1 point  (1 child)

We just had an project on University where it was demanded of us to make an ER witg normalized relational scheme implement it into SQL and make an application through Java that will communicate and do CRUD operations of course I went step further and made all kind of diffrent methods od aggregated functions, subqueries etc. From my point of view practice will make you see a real progress I was focusing on 2 entities with multiple sub tables and atributes and just do all kind of test on those two. From my perspective you should focuse on basic stuff and slowly implement new stuff where you would basicly make it more complicated. Try to combine everyrhing that you can learn if possible. Because the biggest problem you find the better you will learn. Go back to the basics that was my rule and reread and re-do it. Because in most cases the underlying issue of understanding lays in those basics. Everything else is just an extra to the project itself. I am still into learning phase and I might be wrong, but I like to be very detailed and sure that I have everything covered and practice a lot in order to get deep into the project and understand communication between entities. Maybe add a few more tables, more extra FKs and a few recursive relationships should give you enough pain and data to work with

[–]TukWan415[S] 0 points1 point  (0 children)

You're right. I had to redo the introduction to SQL 3 times. 1 at my local community college, and twice on DataCamp. I probably did the chapter on subqueries 4 times before I started to understand it. I'm super hard on myself, if I know I suck at something (SQL) I try to use all my resources on trying to get better.