Cohort 23 CS Online Journal

CST363 Learning Journal - Week 4 In this course, I remembered a few things from the last time I took an intro to database systems course. I wish I still had the textbook from that class, I feel like it would have helped me with my studies.  I've learned how query data from a database, and how to present it to the user with conditions. The different types of joins I had trouble with previously, but now I know how to use each one best. I've used ER diagrams to visualize the relationships in a database. I am more confident about reading ER diagrams, and understanding what they convey for a database. I remember the normal form rules from a previous class, and the zybooks textbook supplements this. There are a few questions I still have about databases: I still need guidance on how to implement SQL into Java. Many of my implementations are researched from the Internet. I need to research more about MySQL Workbench 8.0, there are some issues that occur with large databases that I nee...

Went back on previous CS courses and updated their titles to their corresponding weeks, rather than the total week count of the program. The breaks in-between jumbled my numbers too much! CST363 Week 3 - Learning Journal 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) ? SQL views are a bit like subclasses in Java, where they are mainly used to present only specific data to the user. Views can be created to restrict what information a user queries from a database, but without modifying any existing tables in the database. Views can also be used as a shorthand for complex queries, so they are not written over and over when they are needed.   Operating on views can be tricky, because restricting what data is available can have undesirable side effects. For example, inserting a primary key that exists in the base table but not the view itself will be prevented because the view wi...

 CST363 Week 2 Learning Journal 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. Compare the prices between a digital product and a physical product. create table digi_product (key varchar(20), price varchar(15), name varchar(20), provider varchar(20), size numeric(10,2) primary key (key) ); create table phys_product  (key varchar(20), price varchar(15), name varchar(20), store_location varchar(20) shipping numeric(10,2) primary key (key) ); What is your opinion of SQL as a language?  Do you think it is easy to learn and use?  When translating from an English question to SQL, what k...

Since this is the new fall semester, I'm not too sure whether to include the last two weeks as part of the 100-week count for this program. I'm going to assume no, that is not included. CST363 - Week 1 This week I had trouble finding information to help with the java labs. I felt like I had to research a lot more information than what was provided in the course for these specifically. On the other hand, the ZyBooks textbook is very well made and helped me relearn MySQL statements from years ago. I plan on writing a whole notebook using this textbook just so I have access to it later. There are some questions that this week wants answered:  Relational database tables and spreadsheets look similar with both having rows and columns.  What are some important differences between the two? Data that is inserted into relational database tables must adhere to the table's constraints. For spreadsheets, any data that is inserted is not validated (some spreadsheets can enable this). ...