-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add change log entry for TEXT column migration
- Loading branch information
1 parent
6b312df
commit 62a459b
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
<!-- Delete the sections that don't apply --> | ||
|
||
### Backwards-incompatible changes | ||
|
||
- Migrate the database to use `TEXT` column types where previously we used `VARCHAR` columns with a (now unnecessary) length limit. **This change requires a database migration on deployment**. In Postgres there is no functional or performance difference between `VARCHAR` and `TEXT` columns. This change simplifies the database schema and reduce the risk of future issues with column length limits. | ||
|
||
### New features | ||
|
||
- | ||
|
||
### Bug fixes | ||
|
||
- In the `cli` tox environment, fix the name of the executable to be `times-square` rather than `timessquare`. | ||
|
||
### Other changes | ||
|
||
- Improved the developer documentation for database migration to concretely provide copy-and-pastable commands for preparinug and running database migrations. |