Tag: sequelize

Day 56: Breaking it down…

After my little adventure last night where I almost permanently hosed my server, I decided to leave well enough alone for now and just go with the pages I’ve rendered so far. If we’re going to have to rewrite pages in Angular, I’d just as soon not have too much to convert. I do want to work on eventually converting them all, so that I can practice different types of server routing…Oh my God…I really AM turning into a nerd…

Today’s deeper dive into Angular was a bit better than yesterday, although I’m still not sure HOW we’re going to pull off rewriting our pages. I’ve been reading ahead and it STILL looks confusing. I’m hoping that as we go along it will become clearer. I get the concept of breaking things (the partials and views we have now) into components, but we’re launching into another round of divding things up further into routes, components, and providers (services). We did a few of these today and I STILL have no idea how to determine what goes into which type of file.

In other more exciting news, I believe I’ve figured out how to vary my nav bar using Handlebar conditions, depending on whether a user is logged in or not. My next step is to figure out how to pull this off for users who are admins, so that other users (a.k.a. the unwashed public) aren’t privy to the admin link.

Actually, after last night’s adventure, my next step is to go to bed!

Day 52: MySQL…the Sequel…ize

Today we continued our MySQL adventure with something called “Sequelize” which honestly sounds like a Star Trek term—as in, “Mr. Sulu, sequelize the photon torpedoes!” It also sounds like something done with movie franchises that are well past their prime (“Rocky XIX,” anyone?). The entertaining thing is that autocorrect is coming up with all sorts of naughty words for Sequelize—especially if you initially spell it wrong.

Sequelize is an ORM (object-relational mapping) which we used for MySQL. This is also used for something called PostgreSQL, and yes, I think our instructor is just making stuff up now. All kidding aside, PostgreSQL seems to be very similar to Oracle tables, so I’m sure this will be beneficial to understand when I eventually return to our department.

The thing that’s giving me a coronary is that we need to learn all this stuff, at the rate of one major concept per day, and then APPLY IT TO THE CAPSTONE. I just barely have my routes operational from our last lab, and even so, my pages are not what one might call “functional,” except for the ones that applied to the requirements of the lab. To top it off, we now have to divide everything into routes, controllers, services, models…and I know I’m forgetting something. This is supposed to make the code easier to maintain, but honestly, if you can’t FIND anything, how much simpler is it??? I already get confused about which code is server code vs. client code. This is going to send me running screaming into the night…oh, right. We live in the boonies and THIS is what’s out there:

I’ll have to take my chances with the scary code…