-
-
Notifications
You must be signed in to change notification settings - Fork 788
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d486e9b
commit 86a8714
Showing
5 changed files
with
133 additions
and
61 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,24 @@ | ||
## Breaking changes (for SQLite users) | ||
|
||
#### Fixed [Composite primary key order is not consistent](https://github.com/drizzle-team/drizzle-kit-mirror/issues/342) by removing `sort` in SQLite and to be consistant with the same logic in PostgreSQL and MySQL | ||
|
||
The issue that may arise for SQLite users with any driver using composite primary keys is that the order in the database may differ from the Drizzle schema. | ||
|
||
- If you are using `push`, you **MAY** be prompted to update your table with a new order of columns in the composite primary key. You will need to either change it manually in the database or push the changes, but this may lead to data loss, etc. | ||
|
||
- If you are using `generate`, you **MAY** also be prompted to update your table with a new order of columns in the composite primary key. You can either keep that migration or skip it by emptying the SQL migration file. | ||
|
||
If nothing works for you and you are blocked, please reach out to me @AndriiSherman. I will try to help you! | ||
|
||
|
||
## Bug fixes | ||
|
||
- [[BUG] When using double type columns, import is not inserted](https://github.com/drizzle-team/drizzle-kit-mirror/issues/403) - thanks @Karibash | ||
- [[BUG] A number value is specified as the default for a column of type char](https://github.com/drizzle-team/drizzle-kit-mirror/issues/404) - thanks @Karibash | ||
- [[BUG]: Array default in migrations are wrong](https://github.com/drizzle-team/drizzle-orm/issues/2621) - thanks @L-Mario564 | ||
- [[FEATURE]: Simpler default array fields](https://github.com/drizzle-team/drizzle-orm/issues/2709) - thanks @L-Mario564 | ||
- [[BUG]: drizzle-kit generate succeeds but generates invalid SQL for default([]) - Postgres](https://github.com/drizzle-team/drizzle-orm/issues/2432) - thanks @L-Mario564 | ||
- [[BUG]: Incorrect type for array column default value](https://github.com/drizzle-team/drizzle-orm/issues/2334) - thanks @L-Mario564 | ||
- [[BUG]: error: column is of type integer[] but default expression is of type integer](https://github.com/drizzle-team/drizzle-orm/issues/2224) - thanks @L-Mario564 | ||
- [[BUG]: Default value in array generating wrong migration file](https://github.com/drizzle-team/drizzle-orm/issues/1003) - thanks @L-Mario564 | ||
- [[BUG]: enum as array, not possible?](https://github.com/drizzle-team/drizzle-orm/issues/1564) - thanks @L-Mario564 |
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,60 @@ | ||
## Breaking changes (for some of postgres.js users) | ||
|
||
#### Bugs fixed for this breaking change | ||
|
||
- [Open | ||
[BUG]: jsonb always inserted as a json string when using postgres-js](https://github.com/drizzle-team/drizzle-orm/issues/724) | ||
- [[BUG]: jsonb type on postgres implement incorrectly](https://github.com/drizzle-team/drizzle-orm/issues/1511) | ||
|
||
If you were using `postgres-js` with `jsonb` fields, you might have seen stringified objects in your database, while drizzle insert and select operations were working as expected. | ||
|
||
You need to convert those fields from strings to actual JSON objects. To do this, you can use the following query to update your database: | ||
|
||
**if you are using jsonb:** | ||
```sql | ||
update table_name | ||
set jsonb_column = (jsonb_column #>> '{}')::jsonb; | ||
``` | ||
|
||
**if you are using json:** | ||
```sql | ||
update table_name | ||
set json_column = (json_column #>> '{}')::json; | ||
``` | ||
|
||
We've tested it in several cases, and it worked well, but only if all stringified objects are arrays or objects. If you have primitives like strings, numbers, booleans, etc., you can use this query to update all the fields | ||
|
||
**if you are using jsonb:** | ||
```sql | ||
UPDATE table_name | ||
SET jsonb_column = CASE | ||
-- Convert to JSONB if it is a valid JSON object or array | ||
WHEN jsonb_column #>> '{}' LIKE '{%' OR jsonb_column #>> '{}' LIKE '[%' THEN | ||
(jsonb_column #>> '{}')::jsonb | ||
ELSE | ||
jsonb_column | ||
END | ||
WHERE | ||
jsonb_column IS NOT NULL; | ||
``` | ||
|
||
**if you are using json:** | ||
```sql | ||
UPDATE table_name | ||
SET json_column = CASE | ||
-- Convert to JSON if it is a valid JSON object or array | ||
WHEN json_column #>> '{}' LIKE '{%' OR json_column #>> '{}' LIKE '[%' THEN | ||
(json_column #>> '{}')::json | ||
ELSE | ||
json_column | ||
END | ||
WHERE json_column IS NOT NULL; | ||
``` | ||
|
||
If nothing works for you and you are blocked, please reach out to me @AndriiSherman. I will try to help you! | ||
|
||
## Bug Fixes | ||
|
||
- [[BUG]: boolean mode not working with prepared statements (bettersqlite)](https://github.com/drizzle-team/drizzle-orm/issues/2568) - thanks @veloii | ||
- [[BUG]: isTable helper function is not working](https://github.com/drizzle-team/drizzle-orm/issues/2672) - thanks @hajek-raven | ||
- [[BUG]: Documentation is outdated on inArray and notInArray Methods](https://github.com/drizzle-team/drizzle-orm/issues/2690) - thanks @RemiPeruto |
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
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
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