Documentation → Working with the site → Database

Database

The database stores all website content: products, services, articles, requests, and users. It's typically accessed through the admin panel , but the data can be accessed directly if needed—it can be viewed, edited, and exported.

Where to find it: Settings → Database

When a section is empty: While the site is being created and hasn't been launched yet, the database doesn't yet exist—the section displays the message "The site database has not yet been created." It will appear automatically.

On this page

How the section is structured

  • Tables — a list of all the site's tables. The names are self-explanatory: products , orders , users , and so on (the list depends on your site).
  • Records - the contents of the selected table row by row, with page-by-page navigation.
  • SQL query is a field for a custom query, if you know how to use them.

What can be done?

  • View data - for example, check whether the application has actually been saved.
  • Edit a record - open a row and change the field values.
  • Add entries manually.
  • Delete entries.
  • Execute SQL queries - for bulk operations and selections.
Actions are irreversible. A deleted entry can't be restored with the "undo" button, and an erroneous request can corrupt a large amount of data. Before making mass changes, make a backup , or better yet, delegate the task to an assistant: describe what needs to be changed in the "Development" chat, and they will perform it more carefully.

Useful techniques

  • Test your form. Submit a sample application on the website and see if it appears in the corresponding table.
  • Bulk change via the assistant. "Raise prices on all items in the 'Desserts' category by 10%" is easier to set in chat than to type out manually.
  • Import your data. Attach a list of products or clients as a file in the chat and ask to upload it to the database.

Peculiarities

  • If a table does not have a primary key, an individual row cannot be changed through the interface; such tables can only be edited by query.
  • Changes to the database are applied immediately to the live site—there is no separate test mode.
  • The database is included in the site's backup copies , so regular backups are the best data insurance.
Start now