Online Math Tutoring for SMP Students: How to Choose and What to Check in the Trial Class

Glossary

Fajar Hidayat
Coding Curriculum Team, Algonova

A database is a collection of data organised in one place so that a program can search, add, change, and delete it easily.
Table of Contents
The easiest way to picture one is a class register. There is a row for each pupil and columns for name, student number, and grades. A database works on the same principle, except a computer can find one row among millions in a fraction of a second.
Data is stored in tables. Each table has columns that define what kind of information it holds, and rows that each contain one complete record. In a pupils table the columns might be name, class, and date of birth; one row is one child.
Each row usually has a unique marker called a key, such as a student number. The key is what lets the computer be certain it is fetching the right record even when two children share a name.
Programs talk to a database using special commands. The most common ones read almost like plain English: get every pupil in year 5 whose grade is above 80. That command language is called SQL, and it does only four fundamental things - add, read, change, and delete data.
Every column has its own data type: a whole number for the student ID, text for the name, and a date for the birthday. Clear types prevent mistakes such as typing letters into a grade column.
| Type | How it stores data | Best suited to |
|---|---|---|
| Relational (SQL) | Linked tables of rows and columns | Tidy, consistent data: pupils, transactions, stock |
| Non-relational (NoSQL) | Free-form documents with no rigid table shape | Data whose shape keeps changing: social posts, activity logs |
For a child starting out, the relational kind is far easier to grasp because it looks exactly like a table in an exercise book.
The moment a child builds a project that has to remember something after the program closes - a high score that survives until tomorrow, say - they already need a database. That is where the concept stops being theory.
Understanding databases also trains a way of thinking that pays off outside coding: breaking information into clear parts, naming them well, and making sure every record can be found again. It is the same skill as organising lesson notes so they are easy to find before an exam.
In the Algonova coding course, children who have the basics of programming start storing their own project data. Want to see where your child is now? Join a free coding class.
A database is a collection of data organised in one place so a program can search, add, change, and delete it quickly. The most common shape is a table of rows and columns, much like a class register.
A game's high-score table, an online shop catalogue, a social media friends list, and a digital school report. All of them hold many similar records that need to be found again quickly.
Both look like tables, but a database is designed for far larger amounts of data accessed by many programs at once. It also enforces that each column holds the right kind of value and that every record has a unique marker, so data is harder to mix up or corrupt.
SQL is the command language used to talk to a database. Its commands read almost like plain English, such as asking for every year 5 pupil scoring above 80. Fundamentally SQL does only four things: add, read, change, and delete data.
Usually from around age 12, once a child is comfortable with variables and data types. The most natural trigger is building a project that has to remember something after the program closes, such as a high score that survives until the next day.
Blog


