* Resolves#647 - Fixes typos in Mongo advisory locking parameters
* PR Feedback for #647 - Error out when both params set
* Fixes lint issues with #647
* Additional PR Fixes#647
* Lint fixes again #647
* One more tweak to CONTRIBUTING.md
* One more tweak to CONTRIBUTING.md, again
Co-authored-by: Steve Ramage <[email protected]>
Before this patch, clickhouse.WithInstance() would not select
DefaultMigrationsTableEngine when no MigrationsTableEngine was provided
through the clickhouse.Config{} argument. This behaviour forces the
caller to always provide explicitely the config's MigrationsTableEngine.
This patch make it so DefaultMigrationsTableEngine is used when
MigrationsTableEngine is not provided through clickhouse.Config{}.
Signed-off-by: Alexandre Perrin <[email protected]>
* Added a method to create a mysql database from a connection object
* Calling WithConnection from WithInstance to de-duplicate code
* Adding context and ping to mysql.WithConnection
* Interface type check at compile time
* MSI Auth for SQL Server
Add MSI Auth option to SQL Server connection. Default if no password is provided in connection string.
* Parse resource endpoint from server for msi
update host name parsing to get just the resource endpoint for msi
* Update go-mssqldb
update go-mssqldb to resolve panic issue referenced here: https://github.com/denisenkom/go-mssqldb/pull/642
* Update sqlserver.go
switch from deprecated methods. NewServicePrincipalTokenFromManagedIdentity calls the two methods that are deprecated for us
* Update sqlserver.go
add useMsi param instead of looking for nil password
* Update sqlserver readme
Update sqlserver readme for msi auth. make useMsi a bit safer
* Update sqlserver.go
remove comment
* Update database/sqlserver/README.md
Co-authored-by: Keegan Campbell <[email protected]>
* Update sqlserver.go
refactor resource uri logic into its own method
* Update sqlserver_test.go
add tests for msi connection. can only test whether it fails with useMsi= true, or succeeds with useMsi=false
* Update sqlserver.go
check msi.EnsureFresh return value
* Return error for multiple auth and move query filter
move migrate.FilterCustomQuery(purl).String() into one line out of if/else. return error if both useMsi=true and password are passed
* Update README.md
update readme with warning for useMsi
* Update sqlserver_test.go
Update TestMsiFalse test case as now it should fail when useMsi=false and no password is provided
Co-authored-by: Keegan Campbell <[email protected]>
* used uber atomic bool instead standard in lock/unlock db
* fixing local lock optimization implementation
* fixing mysql local lock optimization implementation
* fixing cockroachdb local lock optimization implementation
* CAS wrapper to automatically restore
* added test for cas with restore
* added atomic lock to sqlite & mongo
* added atomic lock to sqlite & mongo
* fix/refactor test cas restore function
* disable lock for mongo
* mongo local lock before acquiring the db lock
Co-authored-by: a.prinkov <[email protected]>
* clickhouse: make the table engine used for schema_migrations configurable
* clickhouse: tests creation with configurable table engine
* clickhouse: refactor tests to run with multiple table engines
* clickhouse: clarify the use case for the x-migrations-table-engine option
* clickhouse: fix naming consistency for the migrations table engine
* clickhouse: fix tests function wrap pattern
* Postgres and pgx - Add x-migrations-table-quoted url query option to postgres and pgx drivers (#95)
By default, gomigrate quote migrations table name, if `x-migrations-table-quoted` is enabled, then you must to quote migrations table name manually, for instance `"gomigrate"."schema_migrations"`
* Work In Progress
* replace lib/pq dependency with pgx in postgres driver
* fix pgx error handling
pgconn is a low-level library, and errors from queries flow through higher-level pgx library
* update postgres tests to use pgx driver and error reporting
* update quoteIdentifier implementation to match lib/pq
* move changes for pgx support into new driver package
* add pgx driver to CLI
* restore examples used in testing for pgx driver
* replace postgres driver name with pgx in DSN in tests and docs
* consolidate connection string formatting in pgx testing
* lock pgx package at v4
Prior to v4, pgx did not support go modules. Version locking the import is the safest way to ensure we get the (as of now) latest version of the module. Additionally v4 implements some breaking changes to connection and error handling, which are also addressed in this commit.
* update parsed URL scheme instead of using string operation
* add pgx for builds using make
* add pgx to top level docs
* remove autogenerated TOC
* Force MigrationsTable on public schema
* Revert "Force MigrationsTable on public schema"
This reverts commit e5b25e8858ed42d19d420cb8bd16795c060994d2.
* Add example to fix search_path issue
* Use POSTGRESQL_URL in example and fix typo
* Make example simpler by using the `search_path` query parameter of the DB URL
Skipping `GET_LOCK`/`RELEASE_LOCK` is useful when running MySQL as
multi-master. This change simply disables the locking.
The internal client lock is left in place as a sanity check.
This is a copy of the existing sqlite3 driver, except that it imports `_
"github.com/mutecomm/go-sqlcipher/v4"` as database driver. This allows
to use migrate with encrypted sqlite databases.
- Update spanner library to cloud.google.com/go/[email protected]
This prevents erroring on DDL statements like:
ALTER TABLE users ALTER COLUMN created
SET OPTIONS (allow_commit_timestamp = true);
https://github.com/googleapis/google-cloud-go/pull/2656
- Add test case which fails with older version of the library, and
succeeds with this one.
Fixes: #426
- include param in DSN example
- link to README docs on param (option) format
- switch to 'parameter' instead of 'option', in the main README, since
this is preferred
At the moment GCP Spanner backend does not seem to support comments
(issue being tracked at
https://issuetracker.google.com/issues/159730604).
By adding support for parsing the migration DDL with spansql we are
able to support comments and remove them before applying on the
database
