# 0.30.0 `elements db schema` prints the tables and columns the database has now, `elements db dump` takes `pg_dump` options, and a package download that is cut off continues where it stopped. ## Changes - `elements db schema` prints the structure of the database as SQL: tables, columns, indexes, constraints and functions, with no rows. It takes `-test` and `-remote`. `-all` adds the internal `elements` schema, and `-schemas=` prints only the schemas named. - `elements db dump` passes the options after `--` to `pg_dump`, so a backup can use the compressed custom format: `elements db dump -- -Fc -f backup.dump`. With `-remote` the file is written on your machine. - `elements db drop` and `elements db reset` without `-force` report what they would erase and on which machine, as errors 210013 and 210014. - A failed migration shows the `DETAIL` and `HINT` lines from Postgres under its message, for example which key is duplicated. - `elements db -h` says that `shell` is the default command. - A package download that stalls or loses its connection reconnects and continues from the byte it reached, up to five times. A download that still cannot finish reports how far it got and why, as error 220234. - An agent offers both ways to start the app: you type `elements start`, or you ask the agent to start it. The `AGENTS.md` of a new project and the instructions from `elements create` no longer tell an agent to leave starting the app to you. - The manual's releases topic is now `elements man changelog`. Every release has a page, with its changes and its upgrade steps. - Fixed: `elements db drop` and `elements db reset` without `-force` showed `State: Ok` and a diagnostic code of 0 in the JSON report. - Fixed: `elements db -- -f ` waited for stdin to close before it ran the file, which never happened in an agent's shell. ## Upgrade Nothing to change by hand.