You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix!: EXPOSED-691 [PostgreSQL] Restrict dropping unmapped sequences to related tables only (#2357)
* fix: [PostgreSQL] Restrict dropping unmapped sequences to related tables only
- Add existingSequences() method that checks for sequences that are directly
related to tables provided as arguments. This is currently only feasible with
PostgreSQL.
- Switch MigrationUtils method to use this instead of sequences() when generating
SQL to drop sequences.
- Adjust tests accordingly.
* fix!: EXPOSED-691 [PostgreSQL] Restrict dropping unmapped sequences to related tables only
- Update KDocs & Breaking changes doc
* fix!: EXPOSED-691 [PostgreSQL] Restrict dropping unmapped sequences to related tables only
- Remove investigative tests
- Update tests with found issue link
Copy file name to clipboardexpand all lines: documentation-website/Writerside/topics/Breaking-Changes.md
+6
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,11 @@
1
1
# Breaking Changes
2
2
3
+
## 0.59.0
4
+
*[PostgreSQL]`MigrationUtils.statementsRequiredForDatabaseMigration(*tables)` used to potentially return `DROP` statements for any database sequence not
5
+
mapped to an Exposed table object. Now it only checks against database sequences that have a relational dependency on any of the specified tables
6
+
(for example, any sequence automatically associated with a `SERIAL` column registered to `IdTable`). An unbound sequence created manually
7
+
via the `CREATE SEQUENCE` command will no longer be checked and will not generate a `DROP` statement.
8
+
3
9
## 0.57.0
4
10
* Insert, Upsert, and Replace statements will no longer implicitly send all default values (except for client-side default values) in every SQL request.
5
11
This change will reduce the amount of data Exposed sends to the database and make Exposed rely more on the database's default values.
0 commit comments