⚙️How to use MySQL database answer environment

Introduction

Students interact with CodeChum's coding environment whenever they answer programming items in activities created by their teacher.

As a student, it would do you good if you get familiar with how CodeChum's MySQL database environment works and how to use it well so you can be ultra ready for your next CodeChum activity!

MySQL Database Coding Environment Anatomy

CodeChum's MySQL database environment looks like this and has the following parts in it:

1. Item Description - located on the leftmost side of the screen, which contains the item name and the description of the item.

2. Query Editor - Located at the center of the screen, this is where students write their queries to solve the given test cases. Each test case is presented as a card, and students must provide the appropriate MySQL queries to meet its requirements.

3. Check Code- A button located at the bottom of the query editor. When clicked, it submits the students’ queries to the system and returns a score based on the correctness of their output.

4. Item Navigation - one of the cards located at the top right corner of the screen, which shows a list of all the items in the activity, providing your students with seamless navigation from one item to another.

5. Test Cases - one of the tabs located at the rightmost side of the screen, which shows a list of all test cases containing sample outputs that determine your students' score for the item. If their output matches the test cases, you will receive a point.

6. Bottom Navigation - located at the bottom of the screen, which allows your students to seamlessly navigate from one item to another.

7. Messenger Support - located at the bottom left corner of the screen, this allows your students to communicate with our Customer Support Team for assistance with any concerns they may have regarding our app.

Tips

To maximize the potential of our MySQL database environment, here are some tips to up your coding experience:

1. Read the item description carefully, and look out for sample outputs in the description. Those will be helpful to get a visual grasp of what the item is looking for.

2. Always check the description in the test cases so you can determine whether your code follows the required syntax. Before submitting, click the Check Code button multiple times. Also, compare the expected output and your actual output to ensure they are the same.