database
Let an agent help design, query, secure and maintain databases, choose database types, and handle personal data lawfully.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify
Researched by: Claude
Purpose and description
Let an agent help design, query, secure and maintain databases, choose database types, and handle personal data lawfully.
An organised collection of data stored and accessed electronically, managed by a database management system, in models such as relational, document, key-value, graph and time-series databases; related systems include institutional and code repositories, which store files and history rather than structured records.
What it is for: Storing, retrieving and managing data.
It can be choose a database model; design schemas and write queries; secure and back up databases; comply with data protection rules.
Distinguishing features
Structured storage
Managed by a DBMS
Queryable
Needs security and backups
What it looks like
Not physical; tables, collections and graphs managed by software on servers.
How it is recognised
Tables, documents or graphs
Query languages such as SQL
Spreadsheets and code repositories are different tools
Related models
is a kind of - category
is managed by - software
stores - content
is used in - practice
In practice
Families and kinds
relational databases
document and key-value stores
graph databases
time-series and analytical databases
repositories (related sense)
Standards and regulation
ISO/IEC 9075 SQL
GDPR and data protection law
Database rights in the EU
Failure modes and hazards
SQL injection and breaches
Data loss without backups
Unlawful processing of personal data
Also called
+197
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.
Design Choosing and designing.
Requirements drive design.
Model
Database type.
Model
Database type.
- Which database model suits this data and workload? action
- What are the trade-offs? boundary
Schema
Schema design.
Schema
Schema design.
- How should the schema be designed and normalised? action
- Which indexes are needed? measurement
Query Using data.
Queries retrieve data.
SQL
Writing queries.
SQL
Queries.
- How can this query be written and optimised? action
- Is it safe against injection? boundary
Performance
Tuning.
Performance
Performance.
- Why is this query slow, and how can it be improved? measurement
- What does the query plan show? definition
Security Protection.
Data must be protected.
Access
Access control.
Access
Access control.
- Are access controls, encryption and auditing in place? boundary
- Which guidance applies? provenance
Backup
Backups.
Backup
Backups.
- Are backups taken and tested for restore? boundary
- What recovery objectives are needed? measurement
Law Personal data.
Law governs data.
GDPR
Data protection.
GDPR
Data protection.
- Does the database hold personal data, and what legal basis and retention apply? provenance
- Is a data protection impact assessment needed? provenance
Senses
Repositories.
Senses
Repositories.
- Is a code or institutional repository meant rather than a database? boundary
- Which entry fits? action
What the second pass must settle
- Should database models be separate entries?
- How should products be linked?
- How should repositories be split off?