Datasette-edit-schema

Latest version: v0.7.1

Safety actively analyzes 622882 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

0.8a2

- Table names are now [tilde-encoded](https://docs.datasette.io/en/stable/internals.html#tilde-encoding), ensuring tables with unconventional characters like `/` and `.` in their names can still be linked to correctly. [61](https://github.com/simonw/datasette-edit-schema/issues/61)
- Fixed a bug where tables with unconventional names could not be configured as foreign keys. [62](https://github.com/simonw/datasette-edit-schema/issues/62)

0.8a1

- To rename a table users must now have `drop-table` permission for the old name and `create-table` permission for the new name. [60](https://github.com/simonw/datasette-edit-schema/issues/60)
- Action menu items now have descriptions in addition to labels.

0.8a0

This release introduces support for finely grained per-database and per-table permissions, plus integration with the new [Datasette Events](https://docs.datasette.io/en/latest/events.html) mechanism added in Datasette 1.0a8.

- This release requires Datasette 1.0a9 or higher.
- Finely grained permissions: the `edit-schema` permission is still supported, but you can also control access to this plugin using the `create-table`, `drop-table` and `alter-table` permissions from Datasette core. These can be used to control access on a per-table and per-database level. [22](https://github.com/simonw/datasette-edit-schema/issues/22), [#55](https://github.com/simonw/datasette-edit-schema/issues/55)
- Now tracks `create-table`, `alter-table` and `drop-table` events using the new [Datasette Events](https://docs.datasette.io/en/latest/events.html) system introduced in Datasette 1.0a8. [#50](https://github.com/simonw/datasette-edit-schema/issues/50)
- Primary keys can now also be set as foreign keys, useful for many-to-many relationship tables. [52](https://github.com/simonw/datasette-edit-schema/issues/52)
- Now runs `VACUUM` using `db.execute_isolated_fn()` to avoid being caught out by any connection permission handlers. [47](https://github.com/simonw/datasette-edit-schema/issues/47)
- Tightened up display on mobile screens. [45](https://github.com/simonw/datasette-edit-schema/issues/45)
- Fixed a bug where the SQL schema for a table was not shown correctly on the edit schema page. [49](https://github.com/simonw/datasette-edit-schema/issues/49)
- Fixed a 500 error if a table only consists of primary keys. [51](https://github.com/simonw/datasette-edit-schema/issues/51)

0.7.1

- Fixed a bug where editing a schema raised a 500 error if any of the table column names included a single quote. [43](https://github.com/simonw/datasette-edit-schema/issues/43)

0.7

- Ability to add an index (or a unique index) to a column on a table. [27](https://github.com/simonw/datasette-edit-schema/issues/27)
- Ability to drop an index from a table.

0.6

New features:
- Create a new table, setting the name of the primary key and adding multiple columns of different types. [5](https://github.com/simonw/datasette-edit-schema/issues/5)
- Set or change the primary key for a table. [1](https://github.com/simonw/datasette-edit-schema/issues/1)
- Add and edit foreign key relationships for a table. [7](https://github.com/simonw/datasette-edit-schema/issues/7)
- When altering a table, each column now shows a small sample of example values to help you decide the column's new name and type. [28](https://github.com/simonw/datasette-edit-schema/issues/28)
- Delete table button now asks for confirmation. [41](https://github.com/simonw/datasette-edit-schema/issues/41)

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.