Releases: simonw/datasette-edit-schema
Releases · simonw/datasette-edit-schema
0.8a3
- Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417
0.8a2
- Table names are now tilde-encoded, ensuring tables with unconventional characters like
/
and.
in their names can still be linked to correctly. #61 - Fixed a bug where tables with unconventional names could not be configured as foreign keys. #62
0.8a1
0.8a0
This release introduces support for finely grained per-database and per-table permissions, plus integration with the new Datasette Events 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 thecreate-table
,drop-table
andalter-table
permissions from Datasette core. These can be used to control access on a per-table and per-database level. #22, #55 - Now tracks
create-table
,alter-table
anddrop-table
events using the new Datasette Events system introduced in Datasette 1.0a8. #50 - Primary keys can now also be set as foreign keys, useful for many-to-many relationship tables. #52
- Now runs
VACUUM
usingdb.execute_isolated_fn()
to avoid being caught out by any connection permission handlers. #47 - Tightened up display on mobile screens. #45
- Fixed a bug where the SQL schema for a table was not shown correctly on the edit schema page. #49
- Fixed a 500 error if a table only consists of primary keys. #51
0.7.1
0.7
0.6
New features:
- Create a new table, setting the name of the primary key and adding multiple columns of different types. #5
- Set or change the primary key for a table. #1
- Add and edit foreign key relationships for a table. #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
- Delete table button now asks for confirmation. #41