-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): update dependency drizzle-orm to v0.33.0 #702
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/drizzle-orm-0.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
4 times, most recently
from
April 2, 2024 02:01
c7b8eeb
to
f291111
Compare
renovate
bot
changed the title
build(deps): update dependency drizzle-orm to v0.30.6
build(deps): update dependency drizzle-orm to v0.30.7
Apr 3, 2024
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
10 times, most recently
from
April 9, 2024 10:58
8127784
to
4e5e16b
Compare
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
2 times, most recently
from
April 11, 2024 10:05
e07dcc9
to
9d8a962
Compare
renovate
bot
changed the title
build(deps): update dependency drizzle-orm to v0.30.7
build(deps): update dependency drizzle-orm to v0.30.8
Apr 11, 2024
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
3 times, most recently
from
April 15, 2024 23:13
b114a1c
to
007de52
Compare
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
3 times, most recently
from
April 21, 2024 15:35
7ea8731
to
8fde36f
Compare
renovate
bot
changed the title
build(deps): update dependency drizzle-orm to v0.30.8
build(deps): update dependency drizzle-orm to v0.30.9
Apr 21, 2024
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
2 times, most recently
from
April 24, 2024 03:33
d517e8d
to
a785e83
Compare
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
July 23, 2024 17:09
2bf2c9a
to
b64c0b6
Compare
renovate
bot
changed the title
build(deps): update dependency drizzle-orm to v0.32.0
build(deps): update dependency drizzle-orm to v0.32.1
Jul 23, 2024
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
4 times, most recently
from
July 30, 2024 15:50
2e569a0
to
5915819
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
August 5, 2024 18:54
5915819
to
607d838
Compare
renovate
bot
changed the title
build(deps): update dependency drizzle-orm to v0.32.1
build(deps): update dependency drizzle-orm to v0.32.2
Aug 5, 2024
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
August 8, 2024 17:59
607d838
to
3e1381a
Compare
renovate
bot
changed the title
build(deps): update dependency drizzle-orm to v0.32.2
build(deps): update dependency drizzle-orm to v0.33.0
Aug 8, 2024
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
August 8, 2024 21:32
3e1381a
to
475825f
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
August 9, 2024 22:37
475825f
to
358e6f2
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
August 10, 2024 12:40
358e6f2
to
f2f0c2b
Compare
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
2 times, most recently
from
August 24, 2024 10:46
88db423
to
cba6678
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
August 26, 2024 16:14
cba6678
to
53fe8b0
Compare
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
5 times, most recently
from
September 15, 2024 23:15
21c5379
to
c19e36a
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
2 times, most recently
from
September 24, 2024 22:36
95381da
to
56cda38
Compare
renovate
bot
force-pushed
the
renovate/drizzle-orm-0.x
branch
from
October 1, 2024 18:50
56cda38
to
a2bd1cb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.31.0
->0.33.0
Release Notes
drizzle-team/drizzle-orm (drizzle-orm)
v0.33.0
Compare Source
Breaking changes (for some of postgres.js users)
Bugs fixed for this breaking change
If you were using
postgres-js
withjsonb
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:
if you are using 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:
if you are using json:
If nothing works for you and you are blocked, please reach out to me @AndriiSherman. I will try to help you!
Bug Fixes
v0.32.2
Compare Source
AnySQLiteUpdate
- thanks @veloiiv0.32.1
Compare Source
v0.32.0
Compare Source
Release notes for
[email protected]
and[email protected]
New Features
🎉 MySQL
$returningId()
functionMySQL itself doesn't have native support for
RETURNING
after usingINSERT
. There is only one way to do it forprimary keys
withautoincrement
(orserial
) types, where you can accessinsertId
andaffectedRows
fields. We've prepared an automatic way for you to handle such cases with Drizzle and automatically receive all inserted IDs as separate objectsAlso with Drizzle, you can specify a
primary key
with$default
function that will generate custom primary keys at runtime. We will also return those generated keys for you in the$returningId()
call🎉 PostgreSQL Sequences
You can now specify sequences in Postgres within any schema you need and define all the available properties
Example
🎉 PostgreSQL Identity Columns
Source: As mentioned, the
serial
type in Postgres is outdated and should be deprecated. Ideally, you should not use it.Identity columns
are the recommended way to specify sequences in your schema, which is why we are introducing theidentity columns
featureExample
You can specify all properties available for sequences in the
.generatedAlwaysAsIdentity()
function. Additionally, you can specify custom names for these sequencesPostgreSQL docs reference.
🎉 PostgreSQL Generated Columns
You can now specify generated columns on any column supported by PostgreSQL to use with generated columns
Example with generated column for
tsvector
In case you don't need to reference any columns from your table, you can use just
sql
template or astring
🎉 MySQL Generated Columns
You can now specify generated columns on any column supported by MySQL to use with generated columns
You can specify both
stored
andvirtual
options, for more info you can check MySQL docsAlso MySQL has a few limitation for such columns usage, which is described here
Drizzle Kit will also have limitations for
push
command:You can't change the generated constraint expression and type using
push
. Drizzle-kit will ignore this change. To make it work, you would need todrop the column
,push
, and thenadd a column with a new expression
. This was done due to the complex mapping from the database side, where the schema expression will be modified on the database side and, on introspection, we will get a different string. We can't be sure if you changed this expression or if it was changed and formatted by the database. As long as these are generated columns andpush
is mostly used for prototyping on a local database, it should be fast todrop
andcreate
generated columns. Since these columns aregenerated
, all the data will be restoredgenerate
should have no limitationsExample
In case you don't need to reference any columns from your table, you can use just
sql
template or astring
in.generatedAlwaysAs()
🎉 SQLite Generated Columns
You can now specify generated columns on any column supported by SQLite to use with generated columns
You can specify both
stored
andvirtual
options, for more info you can check SQLite docsAlso SQLite has a few limitation for such columns usage, which is described here
Drizzle Kit will also have limitations for
push
andgenerate
command:You can't change the generated constraint expression with the stored type in an existing table. You would need to delete this table and create it again. This is due to SQLite limitations for such actions. We will handle this case in future releases (it will involve the creation of a new table with data migration).
You can't add a
stored
generated expression to an existing column for the same reason as above. However, you can add avirtual
expression to an existing column.You can't change a
stored
generated expression in an existing column for the same reason as above. However, you can change avirtual
expression.You can't change the generated constraint type from
virtual
tostored
for the same reason as above. However, you can change fromstored
tovirtual
.New Drizzle Kit features
🎉 Migrations support for all the new orm features
PostgreSQL sequences, identity columns and generated columns for all dialects
🎉 New flag
--force
fordrizzle-kit push
You can auto-accept all data-loss statements using the push command. It's only available in CLI parameters. Make sure you always use it if you are fine with running data-loss statements on your database
🎉 New
migrations
flagprefix
You can now customize migration file prefixes to make the format suitable for your migration tools:
index
is the default type and will result in0001_name.sql
file names;supabase
andtimestamp
are equal and will result in20240627123900_name.sql
file names;unix
will result in unix seconds prefixes1719481298_name.sql
file names;none
will omit the prefix completely;Example: Supabase migrations format
v0.31.4
Compare Source
v0.31.3
Compare Source
Bug fixed
New Prisma-Drizzle extension
For more info, check docs: https://orm.drizzle.team/docs/prisma
v0.31.2
Compare Source
🎉 Added support for TiDB Cloud Serverless driver:
v0.31.1
Compare Source
New Features
Live Queries 🎉
As of
v0.31.1
Drizzle ORM now has native support for Expo SQLite Live Queries!We've implemented a native
useLiveQuery
React Hook which observes necessary database changes and automatically re-runs database queries. It works with both SQL-like and Drizzle Queries:We've intentionally not changed the API of ORM itself to stay with conventional React Hook API, so we have
useLiveQuery(databaseQuery)
as opposed todb.select().from(users).useLive()
ordb.query.users.useFindMany()
We've also decided to provide
data
,error
andupdatedAt
fields as a result of hook for concise explicit error handling following practices ofReact Query
andElectric SQL
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.