Skip to content
Anthony ERIBON

Projects / Data and developer tools

Database Atlas

Follow a relationship into its records

Read the ER diagram, select a table and inspect its rows without changing workspaces.

  • See key columns and linked tables in the diagram.
  • Read the selected table’s comment and contents together.
  • Diagram browsing does not eagerly load every table’s rows.

Inspect the schema behind a value

Expand the selected table’s metadata when a relationship or constraint needs explaining.

  • Inspect column types and nullability, with primary/foreign-key indicators.
  • Read primary, foreign, unique and check constraints, including FK targets and reference actions.
  • Inspect index columns, uniqueness and engine-reported type.

Filter and page the relevant rows

Column substring filters narrow a bounded, read-only preview.

  • Combine non-empty column filters; the host filters before applying offset and limit.
  • Choose 50, 100 or 200 rows per page and navigate previous/next pages.
  • Changing a filter or page size resets the row offset.

Keep asynchronous results aligned with the selection

A new table or filter selection replaces the previous request.

  • Debounce filter changes, abort superseded requests and ignore their late responses.
  • Validate schema and preview payloads before rendering.
  • Expose loading, empty and error states with retry rather than displaying an invalid response.

Reuse the host’s access context

The host injects schema and optional row-preview loaders into the component.

  • Keep authentication, database access and query scope in the host.
  • Inherit host theme variables and receive selection through a React callback.
  • Liam ERD supplies the diagramming foundation; Atlas supplies the embedding and record-inspection contract.

Who does what

User selection and filtering trigger bounded read requests. The host remains responsible for database access and authorization.