MariaDB Information_schema Keywords Reserved Column

Published
Length
3 min read

Luis Felipe Dias

All posts

The mariadb information_schema keywords reserved column shows if a word needs quotes in queries. Teams check this system table to avoid syntax errors when naming tables or columns. Most database teams give developers broad read permissions to inspect system tables during builds. Yet wide permissions often let users read sensitive schema details across every database. How the mariadb information_schema keywords reserved column works Every database engine uses a specific list of words for buil

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

The mariadb information_schema keywords reserved column shows if a word needs quotes in queries. Teams check this system table to avoid syntax errors when naming tables or columns.

Most database teams give developers broad read permissions to inspect system tables during builds. Yet wide permissions often let users read sensitive schema details across every database.

How the mariadb information_schema keywords reserved column works

Every database engine uses a specific list of words for built-in commands and functions. Some of these words are strictly reserved for the database parser to read commands. Other words are non-reserved keywords that you can still use as plain table names.

The keywords view inside the system schema stores this full list for your server. It holds two main pieces of data for every single word in the list. The first column lists the word itself in plain text for easy searching. The second column is the reserved flag, which shows a simple number value.

When the reserved flag shows a one, the word is strictly reserved by MariaDB. You cannot use that word as a table name or column name without quotes. If you try to run a query without quotes, the parser stops and fails. When the reserved flag shows a zero, the word is not reserved at all. You can use a zero-flagged word for naming objects without adding special quote marks.

Developers read this view before they build new tables or migrate old database schemas. Build tools and migration scripts also read this view to check new table names. Any user who can log in can read this view with basic account roles.

What native schema checks solve and what they leave open

Checking the system keywords view solves syntax mistakes before code reaches your live server. It helps teams spot naming conflicts when they upgrade from one version to another. New database releases often add new words to the system list and change flags. Reading the reserved flag lets teams fix schema names early in the test cycle.

Security Information & Event Management (SIEM) + API Schema Validation: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Still, native database permissions only decide who can log in and read tables. To help developers check schemas, teams often grant wide read roles on live servers. Once a user logs in with that role, the database trusts every read query. The native setup does not check what individual statements do while they run.

A developer who logs in to check system views can also query user tables. If the role allows reading across schemas, sensitive customer rows are open to queries. Native roles cannot tell the difference between a schema check and a data dump. They also do not rewrite sensitive fields like emails or phone numbers in results.

Also, shared roles make it hard to see which person ran a statement. Database logs only show the shared role name instead of the real team member. Teams need a way to inspect every single query in flight and mask data.

Add wire guardrails and masking beside MySQL

Database grants and TLS setup decide who can reach MySQL. Even so, an open session can run broad updates or read raw personal data from allowed tables. In practice, hoop.dev runs beside the database as a sidecar for your MySQL. It keeps your login setup and drivers as they are while checking queries on the wire.

With hoop.dev MySQL support, guardrails refuse bad queries before they run and return a readable MySQL error. Data masking rewrites matched sensitive values in result rows in memory. Furthermore, hoop.dev holds SOC 2 Type II and generates evidence for GDPR, HIPAA, and PCI DSS programs. Read the docs and source on GitHub.

Frequently asked questions

What do the numbers in the reserved column mean?

A value of one means the word is reserved and needs quotes as an identifier. A value of zero means you can use the word without adding special quotes.

Who can read the keywords view in the system schema?

Any user who can log in to the database server can read this view. It does not need special admin roles because it only lists engine words.

Why do schema migration scripts check this system view?

Migration tools check this view to find out if new column names need quotes. This step stops syntax failures when scripts build tables on newer server versions.

The query runs. The emails stay hidden.