forked from golang-migrate/migrate
-
Notifications
You must be signed in to change notification settings - Fork 15
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
upstream merge #14
Merged
Merged
upstream merge #14
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
refactor: use sort.Slice
* clarify the package name * Adding import and connection string sections * more clarification around the go usage
Update Google Cloud Spanner to 1.27
len(k) is guaranteed to be greater than 1 in this case
* upgrade containerd/containerd to 1.5.8 for vulnerability * upgrade opencontainers/image-spec to 1.0.2 for vulnerability * upgrade dktest to v0.3.8
* Use DELETE FROM instead of TRUNCATE for MySQL * Set isolation level to SERIALIZABLE Co-authored-by: Martin Arrieta <mail@martinarrieta.me>
fix(spanner): Upgrade spanner client to latest, which adds JSON_VALUE support
docs: Include iofs in migration sources
Bump go-sqlite3 to v1.14.10
The current example for the Clickhouse DSN is incorrect and will result in the client trying to use the default username, database, and password regardless of what is set in the DSN. This change fixed the DNS example to be correct for the current versions of the clickhouse-go client.
Incorrect DSN example for Clickhouse
The directory created by `T.TempDir` is automatically removed when the test and all its subtests complete. Reference: https://pkg.go.dev/testing#T.TempDir Signed-off-by: Eng Zer Jun <engzerjun@gmail.com>
test: use `T.TempDir` to create temporary test directory
Exposes the cassandra client's ConnectTimeout parameter through the cassandra database query string. The Cassandra client has a fairly aggressive connect timeout of 600ms, which can cause flakiness in certain network environments or in Cassandra-compatible clusters with a more complex process for establishing connections (i.e. ScyllaDB). The query timeout is already configurable and exposed, but does not impact the connect timeout in the gocql driver. This change allows for configurtion of both.
Expose configuring cassandra connect timeout through query string
Add WithConnection to Postgres similar to MySQL.
Run SQL server tests on Azure SQL Edge
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.
No description provided.