Browse and fix your database on BrewInTH without phpMyAdmin

Browse tables, search and fix rows in PostgreSQL, MySQL or MariaDB from the BrewInTH console, with SQL to copy, the limits, and a phpMyAdmin-ready download.
Your shop's site has been taking orders for a while. Then a customer writes in: they typed their phone number wrong, could you fix it? Or you simply want to know how many orders are still waiting to ship. On old-style hosting you'd open phpMyAdmin. On BrewInTH the database lives on the project's private network, so desktop tools such as DBeaver or MySQL Workbench can't reach it.
This guide walks you through the Database browser on the console's Databases tab: browsing tables, reading their columns, running your own SQL with examples to copy, changing data without slipping up, and downloading the whole database for phpMyAdmin somewhere else.
In short
🗂️ Open the project › Databases tab › Database browser; it works with PostgreSQL, MySQL and MariaDB
👀 Pick a table on the left to page through its rows 50 at a time, or to see its columns
⌨️ Press SQL to run your own statements, one at a time: at most 200 rows back, finished within 10 seconds
🛟 Before you change or delete data, press Back up now and run a SELECT with the same WHERE first
📦 A MySQL database has a For phpMyAdmin/MySQL download that imports more easily on other hosts
What the Database browser is, and where to find it
The Database browser is a phpMyAdmin-style page built into the BrewInTH console, with nothing to install. You can reach it two ways:
- Open the project and choose the Databases tab.
- Or choose Databases in the menu on the left, then pick the project.
The tab starts with the project's list of databases. Below it sits the Database browser, which appears once a database is Ready. It works with PostgreSQL, MySQL and MariaDB; MongoDB and Redis are used from your app or the Commands tab.
Why go through the console at all? The address behind the Connection button only works from inside the project: your published app and the commands that run on BrewInTH. From your own computer, this page is the way in, or you can let an AI look for you, as described below.

Page through 50 rows at a time, and see a table's columns
- Pick a table on the left. The list loads by itself when you open the tab; if your app has just created a table, press Reload tables. On MySQL and MariaDB a figure such as ~240 next to a table is a rough row count, not the exact number.
- Rows shows 50 rows at a time; Next and Previous turn the page. Empty fields show as NULL in italics, and a wide table scrolls sideways.
- Columns lists each column's name, type, whether it may be empty, and its default. Read it before you write SQL, or copy it for your AI so it knows what the table looks like.
- Edit as SQL opens the SQL box with the table's statement ready to change.
The Rows view doesn't sort anything for you. To see the newest rows first, press Edit as SQL and add ORDER BY id DESC before the LIMIT (if the table has an id column).
If the page says "No tables yet. Run your app's migrations first.", your app simply hasn't created its tables; nothing is wrong with the database.
Running your own SQL: the limits
Press SQL under the list of tables, type a statement and press Run SQL. It runs as this database's own user, so it sees this project's data and nothing else. The limits:
- One statement per run. Run several statements one after another.
- Up to 10,000 characters per statement.
- At most 200 rows or 60 KB back. Past that you get no rows at all, just "Result exceeds 200 rows / 60 KB. Add a LIMIT." So add a
LIMITto every SELECT. - Done within 10 seconds. A statement that takes longer is cut off and reported as failed.
A statement that changes data, such as UPDATE or DELETE, answers in a sentence, for example "Done: 1 row(s) affected"; on MySQL and MariaDB an INSERT also tells you the new id. A mistake brings a red message with the database's own reason, such as a table that doesn't exist. Copy it to your AI as it is.

SQL you'll use often (run one at a time)
These work on MySQL, MariaDB and PostgreSQL alike. The table names are examples; use your own, which the Columns view shows.
-- the exact number of rows in a table
SELECT COUNT(*) AS total FROM orders;
-- the 20 latest orders
SELECT * FROM orders ORDER BY id DESC LIMIT 20;
-- find customers by name
SELECT id, name, phone FROM customers WHERE name LIKE '%Somchai%' LIMIT 20;
-- orders per status
SELECT status, COUNT(*) AS total FROM orders GROUP BY status;
-- fix one customer's phone number
UPDATE customers SET phone = '0812345678' WHERE id = 42;
On MySQL and MariaDB, LIKE usually ignores upper and lower case. PostgreSQL's LIKE doesn't; use ILIKE there for the same effect.
Before you change or delete anything: three steps
The SQL box changes real data immediately, and there's no undo. Take these three steps before every UPDATE or DELETE:
- Back up first. Scroll down to the Backups panel below the browser, press Back up now, and wait until the new row says Completed. The button needs the Backups add-on (฿99 a month at the time of writing).
- Look before you change. Run a SELECT with the WHERE you're about to use, such as
SELECT * FROM customers WHERE id = 42;, and check it returns the right rows, and the right number of them. - Turn it into the real statement. Change
SELECT *intoUPDATE … SET …orDELETE, keep the WHERE exactly as it was, and check that the number of rows affected matches step 2.
The page adds one more safety net. DROP, TRUNCATE, an ALTER TABLE that drops, changes or renames something, and a DELETE or UPDATE without WHERE don't run straight away: a warning says the statement removes or changes a whole table's data and no backup is taken first. Press Run SQL again to go ahead, or cancel.
That warning only looks at the shape of the statement, though. A WHERE with the wrong condition runs at once. And once a change has gone wrong, the way back is restoring a backup, which replaces the whole database, so anything that came in after that backup is lost too. How restoring works: Back up and restore your database on BrewInTH.
What the SQL box isn't for
- Large, slow changes. Anything over 10 seconds is cut off. Have your AI write a script and run it on the Commands tab, or let the AI run it itself, for up to 4 hours a run (the Commands tab).
- Importing a whole .sql file. The box takes one statement at a time; let your AI import the file through BrewInTH's file import instead.
- Changing your app's tables, such as adding a column. That belongs in a migration in your code; a change made by hand here may clash with your app's next migration.
Let your AI read the data and write the SQL
If SQL isn't your thing, an AI can help in two ways:
- The AI writes, you run. Copy the table's columns from the Columns view to your AI, say what you want, and paste the statement it gives you into the SQL box.
- The AI runs it. If your AI's token has the Create DBs, run SQL and retrieve credentials permission, it runs SQL through the same route as this page, with the same limits. That permission also shows the AI the database password (token permissions on BrewInTH).
A message for an AI that's already connected to the project; adjust the details to your task:
Please change the phone number of the customer "Somchai Jaidee" in my site's database on BrewInTH to 0812345678.
- Look at the columns of the customers table first, then SELECT the matching row. Always use a LIMIT.
- If more than one row matches, stop and ask me.
- If the account has the Backups add-on, take one database backup before the change.
- UPDATE with WHERE id = that row's id only, then SELECT it again to show me the change.
- Never show passwords or other customers' data in your answer.
Download the database for phpMyAdmin or another host
Sometimes the whole database has to go somewhere else: a copy for yourself, for whoever helps with your site, or for a move to another host. Every row in the Backups panel that says Completed can be downloaded.
- Download gives a file for the engine:
.sql.gzfor MySQL and MariaDB,.pgdumpfor PostgreSQL (open it withpg_restore),.mongo.jsonl.gzfor MongoDB. - For phpMyAdmin/MySQL, on MySQL databases only, gives the same data with newer collation names such as
utf8mb4_0900_ai_cichanged toutf8mb4_unicode_ci. Its name ends in-portable.sql.gz.
Why the second one? MySQL on BrewInTH is a recent version, so its tables use a collation that hosts running an older MySQL or MariaDB often don't know, and an import in their phpMyAdmin tends to stop with "Unknown collation". The portable file takes care of that. In the other phpMyAdmin, pick the database, open Import and choose the file; if that host doesn't take .gz files, unpack it to .sql first.

Making a new copy needs the Backups add-on, but copies you already have stay downloadable even after the add-on ends. Remember the file holds all your customers' data: keep it somewhere safe, and don't drop it into a group chat.
FAQ
Can I connect DBeaver or my own phpMyAdmin to the database?
No. The address in the connection details only works from inside the project. Use the Database browser in the console, let an AI look for you, or download a backup and open it on your computer.
Why is a table missing from the list?
The list shows real tables only, not views, and only names made of English letters, digits and underscores that don't start with a digit; on PostgreSQL, only the public schema. You can still query the others in the SQL box.
PostgreSQL says a table doesn't exist, but I can see it in the list
A table name with capitals, such as the Customer table Prisma creates, needs double quotes: SELECT * FROM "Customer" LIMIT 20;. Without them PostgreSQL looks for a lowercase customer table.
Thai names don't sort in dictionary order
MySQL on BrewInTH sorts Thai by character code, not in dictionary order. To see them in dictionary order on this page, use ORDER BY CONVERT(name USING tis620) COLLATE tis620_thai_ci. In your app, have your AI sort in code with Thai collation rules.
Does a MariaDB database get the phpMyAdmin download?
Not yet. For phpMyAdmin/MySQL appears on MySQL databases only; for MariaDB use Download. If the other host can't import it, copy the error to your AI and let it fix the file (how to report an error to your AI).
Does my site see a change made here straight away?
Yes, because it's the same database your app uses. The one exception is data your app keeps in a cache, such as Redis: the new value shows once the cache expires.
Summary
The Database browser on the Databases tab covers everyday phpMyAdmin work. Pick a table to page through its rows 50 at a time or to read its columns, press SQL to run your own statements one at a time with a LIMIT, and before you change data, press Back up now and run a SELECT with the same WHERE. When the whole database has to go elsewhere, a MySQL database has the For phpMyAdmin/MySQL download. The in-console guide shows the real screens of this tab.
