Brendan Clement 53c2f0b782 docs: correct table and namespace claims the runtime audit contradicted ...

- Python's table_exists was said to work on namespace connections; on
  one from connect_namespace("dir" or "rest") it fails with an
  AttributeError. The page now shows the supported checks: open the
  table and handle the error each connection raises, or read every page
  of a listing.
- Dropping a missing table was said to raise by default. A local
  database raises; a deployment may report success, depending on its
  catalog, and its Python connection takes no ignore_missing.
- A deployment's catalog may refuse cloning altogether; where cloning
  works, it is shallow.
- A dropped column was called unrecoverable. Restoring a version from
  before the drop brings it back until cleanup prunes that version.
- The namespace page stored data in a `data/` directory that does not
  exist, presented a recommended character set as enforced, and its
  Python listing comments showed lists where the calls return response
  objects. Its namespace examples now run as tests.
- The storage tip offered the table's reported options as the effective
  ones; they omit what the table inherits from its connection.

2026-10-09 13:31:48 -07:00

..

monitoring.mdx

docs: bring the open-source documentation into this repository (#4122)

2026-10-07 11:15:00 -07:00

storage.mdx

docs: correct table and namespace claims the runtime audit contradicted

2026-10-09 13:31:48 -07:00

support.mdx

docs: bring the open-source documentation into this repository (#4122)

2026-10-07 11:15:00 -07:00