Developers can now build and validate SQLDB-backed Edge Compute applications locally, and manage larger database backups with new export and import workflows in the telnyx-edge CLI.
.telnyx/sqldb/ by default. Because telnyx-edge dev and local SQLDB commands access the same local database configured in telnyx.toml, you can test schema changes and functions together before deployment. Docker is required for local SQLDB commands.storage sqldb import loads a SQL dump from a local file or a previous export, without splitting files to fit the roughly 4 MiB limit on remote execute --file requests. Imports run as jobs, the CLI reports progress, and interrupting the CLI wait does not cancel a running import.Database-backed Edge Compute workflows previously required iterating against a deployed database and splitting large SQL files to fit remote execution limits. With local development and higher export and import limits, you can test schema changes and functions locally, export database dumps up to 4 GiB for backups, and restore dumps up to 100 MiB through the new import workflow instead of splitting large SQL files into small remote execution requests.
Local SQLDB is isolated from production: local changes are not automatically synced or deployed. Export and import limits are independent: a dump larger than 100 MiB can be exported, but it cannot be restored through the new import command. Imports apply in atomic batches; if a later batch fails, earlier successful batches remain applied.
telnyx-edge storage sqldb execute DB --local --command "SELECT 1" telnyx-edge storage sqldb migrations apply DB --local
telnyx-edge storage sqldb export <database-id> --remote --output ./database.sql telnyx-edge storage sqldb import <database-id> --file ./database.sql
Learn more in the SQLDB CLI guide, the SQLDB migrations guide, and the SQLDB limits reference.