Update dependency ecto_sqlite3 to v0.18.1 #27
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.9.1
->0.18.1
Release Notes
elixir-sqlite/ecto_sqlite3 (ecto_sqlite3)
v0.18.1
Compare Source
Jason
andJSON
.v0.18.0
Compare Source
1.14
support. Elixir1.18
was released and I am only supporting 3 minor versions back.v0.17.6
Compare Source
v0.17.5
Compare Source
v0.17.4
Compare Source
default_transaction_mode
.v0.17.3
Compare Source
insert_all
calls.v0.17.2
Compare Source
:datetime_type
config.v0.17.1
Compare Source
3.12
.v0.17.0
Compare Source
:integer
column type support. Under the hood it is stored the same regardless.3.12
.insert_all
to no longer require a where clause.v0.16.0
Compare Source
exqlite
dependency to0.22
.v0.15.1
Compare Source
v0.15.0
Compare Source
nil
decoding for:decimal
.exqlite
to~ 0.19
.v0.14.0
Compare Source
:utc_datetime
,:utc_datetime_usec
,:naive_datetime
, and:naive_datetime_usec
column dates.insert_all
.v0.13.0
Compare Source
v0.12.0
Compare Source
{:unsafe_fragment, ".."}
as a conflict target.1.12
.v0.11.0
Compare Source
v0.10.4
Compare Source
binary_id
is specified.v0.10.3
Compare Source
v0.10.2
Compare Source
Date
type.v0.10.1
Compare Source
init
file when usingdump_cmd/3
v0.10.0
Compare Source
changed: Add support for Ecto
v3.10
changed: Bring SQLite closer to the Postgres adapter implementation
changed: Enable
AUTOINCREMENT
forserial
andbigserial
.changed: breaking Add support for sqlite strict mode.
With sqlite strict mode support being added, the following field "types" were altered.
TEXT_DATETIME
=>TEXT
TEXT_UUID
=>TEXT
: This is when:binary_id_type
is:string
UUID
=>BLOB
: This is when:binary_id_type
is:binary
This is a breaking change in the sense that rebuilding the schema from scratch will cause those columns to show up differently. Under the hood sqlite does not actually care.
We kept
TEXT_DATETIME
to satisfy the old Ecto2 implementation to keep backwards compatibility.changed: breaking Raise when table prefixes are used.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.