Posts

Computer Science BS Journal (CST363) : Week 4

     This week marks the halfway point for our class. There is so much I've learned in this class so far and I'm excited to keep moving forward.  Briefly summarize 5 things what you have learned in the course so far.   SQL - I've learned that SQL (Structured Query Language) is used to manage and interact with relational databases. It lets you define data structures(tables), insert data, and query information using commands like SELECT, INSERT, UPDATE, and DELETE. Java Tuples - In Java, I learned that tuples are fixed-size collections of elements, used to group related values without creating a class. Java Predicates - A Java Predicate is a functional interface that represents a condition or boolean-valued function. I learned that it's commonly used in filtering operations with streams or collections, and takes one argument to return true or false. Bitmaps - I learned that a bitmap is a data structure that represents a set of bits (0s and 1s), often used to ...

Computer Science BS Journal (CST363) : Week 3

  1.What is an SQL view.  How is it similar to a table? In what ways is it different (think about primary keys,  insert, update, delete operations) ?      An SQL view is a virtual table that is created by saving the result of a SELECT query. It does not store data itself but presents data from one or more underlying base tables. A view is similar to a table in that you can query it using SELECT statements, apply filtering, sorting, and even joins, just like with a regular table. However, views differ from tables in several key ways. Unlike tables, views do not physically store data, and they cannot have primary keys defined on them. Additionally, while tables fully support INSERT , UPDATE , and DELETE operations, views only support these operations under certain conditions. For example, a view must be updatable—typically meaning it is based on a single table without joins, aggregations, or GROUP BY clauses—to allow data modifications. Even when a view i...

Computer Science BS Journal (CST363) : Week 2

 Class: CST363-30_2253 ( Intro to Database Systems) SQL has the flexibility to join tables on any column(s) using any predicate (=, >, < ).    Most of the time the join will use equality between a primary and foreign key.   Think of example where joining on something other than keys would be needed.  Write the query both as an English sentence and in SQL.  If you can't think of your own example, search the textbook or internet for an example. English Sentence: Imagine you are working with a database that stores information about employees and their salary performance. You may want to find the employees who are earning more than the average salary in their department. In this case, you would join the employee table with the salary data table using the salary amount, not the keys, in order to compare each employee's salary with the department's average. Query:   SELECT e.employee_name, e.department_id, s.salary FROM employees e JOIN salaries ...

Computer Science BS Journal (CST363) : Week 1

  Class: CST363-30_2253 ( Intro to Database Systems) From the orientation, your reading from week 1 and your own experience answer the following questions. Relational database tables and spreadsheets look similar with both having rows and columns.  What are some important differences between the two? A few important differences I can point out between relational database tables and spreadsheets are Data Integrity/Constraints, Data Relationships, and Data Volume/Performance.  Data Integrity/Constraints :  Relational Database  -  Provides tools for ensuring data integrity through constraints like primary keys, foreign keys, and unique constraints. This ensures data is valid, consistent, and adheres to business rules.  Spreadsheets  -  Lack inherent features for enforcing data integrity. It’s easy to accidentally input inconsistent or erroneous data.  Data Relationships :  Relational Database -  Supports complex re...

Computer Science BS Journal: Week 13

 This week we are reviewing the Markov assignment with classmates. For the Markov review I worked with Neng Lao. He helped me get out of a tough spot with my failing tests and in the end I had all tests passing and got full marks. (I had a typo 😭) Who did you work with? I worked with Neng Lao What was your strategy for solving the Markov assignment? Did you start writing code right away? Did you plan it out on paper?  I didn't plan anything out, but I initially read the coding prompt and took a look at the UML diagram to get an idea of what was to be included. After reading and becoming familiar with the prompt I had it opened on my other screen while I created my stubs. Then I simply went down the list of methods on the prompt and coded them in order. What was THEIR strategy for solving the Markov assignment. Neng said his strategy was "For the assignment my strategy was to write out all the stubs and worked through each function/method one by one making sure they pass the t...

Computer Science BS Journal: Week 12

  Wk04: Learning Journal Project 1 review You can work with up to three people (you MUST work with at least one other person) With whom did you work?  I ended up working with Neng Lao What was your strategy for solving the assignments? Did you start writing code right away? Did you plan it out on paper?  For the lab I like to follow the prompt thoroughly. First I'll add all the stubs from the UML diagram and then start implementing my methods via the order on the prompt. I usually wait to test until I feel like I'm done with the main java file, not a good habit I know, but going about it that way I can do individual tests to see which ones are passing and which aren't. Usually if I run into failed tests there is only one root cause that I end up having to debug to complete my assignment. What was THEIR strategy for solving the assignments Neng Lao: " For the first lab my strategy was to write out all the stubs and worked through each function/method one by one making s...

Computer Science BS Journal: Week 11

  Wk03 Learning Journal: Project 1 Code Review      This week we are trading our code with our peers and reviewing them to help each other notice mistakes in our code and perhaps improve each others skillset and knowledge. I worked with Neng Lao in the code review, more like he assisted me with some troubleshooting on the assignment. Turns out I make some very sneaky typos every so often that breaks everything. Lol. I'll go over the assignment prompt and answer each question below. Summarize the feedback you received about your code from your peers Some of the feedback I got was to stick to the prompt. I have a bit of previous java experience so I tend to try and use some of that knowledge. For instance I was trying to use append and StringBuilder in some of my code when we hadn't been "taught" that yet in the class. Sticking to what has been taught thus far to hone THOSE skills is something I should focus on. And I agree with that assessment. I'm going to try and...