"Database" gets used loosely to describe everything from a carefully structured catalogue to a single unsorted text file of game titles. The difference matters enormously once you actually try to find something specific.
Structured Fields, Not Just Free Text
A genuine database attaches consistent fields to every entry — release year, platform, genre, developer, publisher, legal status — rather than burying that information inside a paragraph of prose that a search function cannot reliably parse. Consistent fields are what make filtering and sorting possible at all.
Cross-Referenced Taxonomy
Platforms, genres, publishers and developers work best as their own structured entities that games link to, rather than repeated free-text labels typed slightly differently on every entry. This is exactly why the genre, platform, publisher and developer listings function as their own browsable pages rather than just search filters.
Verified, Not Just Collected, Information
A database that collects information without verifying it eventually accumulates errors that compound over time, particularly around legal status, as discussed in Inside a Retro Gaming Archive. Volume without verification produces something that looks comprehensive but cannot be trusted on the details.
Built for Browsing, Not Only Searching
A well-structured database supports discovery even when a visitor does not know exactly what they are looking for — browsing by year, platform or genre rather than only typing a title into a search box. See Searching an Old PC Games Database for how that browsing experience should actually work in practice.
