🗃️Databases
Storing and querying structured data · 46 terms
Database Basics
15What a database is made of: tables, rows, keys, schemas and queries.
A store of data that programs save to. They can search it fast.
A code to ask a database for data. You use it to change data too.
One kind of data in a database. It is set out in rows and columns.
A column with a different value in each row. That is how one row is found.
A column that points to a row in another table. The link is checked for you.
The plan of a database. It lists the tables, columns, types and links.
A request sent to a database. It reads some data or changes it.
The four jobs you do on data: add it, read it, change it, and delete it.
A link between two tables. One row on one side goes with many rows on the other.
SQL Query Syntax
4The parts of a SQL query that pick, filter, group and count the rows you get back.
The SQL command that reads data out of a table.
The part of a SQL command that keeps only the rows that pass a test.
The SQL part that puts rows with the same value into groups.
A SQL tool that turns lots of rows into one number, like a sum.
Relational Databases
17Databases built from linked tables, spoken to in SQL.
A database that keeps data in linked tables. You talk to it in SQL.
Features
11The parts of SQL that join, speed up and protect the data.
The part of a query that pairs rows from two tables. You get one result.
A join that keeps only the rows with a match in both tables.
A join that keeps each row from the first table, with a match or not.
A sorted list that lets the database find rows fast. It skips the rest.
The steps a database picks to answer a query. EXPLAIN shows them.
A group of changes that all happen, or none of them do.
Four promises a database keeps, so each change is safe.
A log the database writes each change to first. Then a crash loses nothing.
Setting up a database so each fact is kept in one place.
A saved query you can read from as if it were a table.
A small program saved in the database. The app calls it by its name.
Popular Databases
5The relational databases you are most likely to meet.
A free, open-source SQL database with lots of tools. Many teams pick it first.
A hosted back end built on a Postgres database. It adds login and file storage.
A popular, free SQL database. A huge share of websites run on it.
A tiny SQL database in one file. There is no server to run.
The database Microsoft makes. Apps talk to it in a kind of SQL called T-SQL.
NoSQL Databases
6Databases that store documents, keys or graphs instead of linked tables.
A database that does not use linked tables. It keeps data in other shapes.
A NoSQL database that keeps each record as one document. It looks a lot like JSON.
The top store for documents. Each record is a document, a lot like JSON.
The simplest NoSQL database. You save a value under a key and read it back.
A store that keeps data in memory, under keys. That makes it very fast.
A database that stores things as points and the links between them.
Databases in Code
5How an app talks to its database, changes it and fills it.
Code that lets you use rows as objects in your own language. You write no SQL.
A small file that makes one change to a database's shape. It lives with the code.
Open links to a database that an app keeps ready. It uses them again.
One query for a list, then one more for each item. Pages get slow.
Data put into an empty database at the start. The app or tests use it.
Scaling
3Copying and splitting a database so it stays safe and fast as it grows.
Live copies of a database kept on other servers. If one fails, the rest go on.
A copy of a database that only answers reads. It takes load off the main one.
The rows of a big database, split across many servers. Each holds a part.