Database
Export your app's data
Download rows as CSV or JSON, export the answer to a SQL statement, or take a full SQL file of an app on your own Postgres.
You can take your app's data out of Ahamo three ways, the rows on screen, the answer to a SQL statement, or, for an app on your own Postgres, a full SQL file of its tables and data.
When to use it
- To share a list with a colleague or open it in a spreadsheet, export the rows on screen.
- To pull a specific set of records, run a SQL statement and export the answer.
- To keep a copy of the whole database, or move it elsewhere, export the SQL file.
How to export
Rows on screen. In Data, open a table, then More actions (⋯) › Export this page as .csv or Export this page as .json. This exports the current page of rows (25, 50 or 100).
The answer to a statement. In the SQL console, run the statement and select Export CSV.
The whole database (own Postgres). In Runtime › Data › Backups, select Export now. Ahamo downloads one SQL file with the app's own tables and data, nothing else in your database.
Each SQL file export is recorded in the activity log.
Plans and limits
| Export | Up to | Who |
|---|---|---|
| Rows on screen | One page (100 rows) | People who can read the app's database |
| Statement answer | 500 rows | As in the SQL console |
| SQL file | 2 GB, 10 minutes | People who can publish the app |
Exports contain data only, so uploaded files and sign-in settings are not included.
Troubleshooting
Export now is missing. The app's data is in Ahamo's built-in database. Export rows or statement answers, or move the app to your own Postgres first.
"…transaction pooler (port 6543)…". Use your database's direct or session connection string. A Supabase transaction pooler address is switched to the session pooler for you; other transaction poolers are refused.
"Too large". The database is over 2 GB. Export tables in parts with the SQL console, or use your database provider's own backup tools.