I looked at https://github.com/cakephp/phinx/blob/master/docs/en/migrations.rst#custom-column-types--default-values but still can't really figure out how to apply this to generate mysql virtual columns. The example sql would be

ALTER TABLE `t_calendar_sources` ADD `c_flag_deleted` boolean GENERATED ALWAYS AS (IF((json_unquote(json_extract(`c_attr`,'$.deleted'))) = 'true', 1, 0)) VIRTUAL N

Context

As a reader of online docs, it is not clear when doing diff which database if the "reference" against which a "target" is compared. This makes it tough!

As a reader of online docs, hoping to do a diffchangelog, it is not clear how to set the url and referenceURL parameters if i want to apply the generated diffchangelog against one db to migrate it up to the other. Which is which?

R

$ curl 'http://127.0.0.1:5000/auth/oauth2/token?grant_type=client_credentials' --user 'documentation:KQ()SWK)SQK)QWSKQW(SKQ)S(QWSQW(SJ*HQ&HQW*SQ*^SSQWSGQSG'
{"access_token": "lYoijoYaTgXZi1bLQTs4PuItKsNHNY", "token_type": "Bearer", "expires_in": 3600, "scope": "users:write teams:write auth:write users:read auth:read teams:read"}

Grab the above access_token and access protected resour

I encountered a strange bug: I had a space in front of -- migrate:down, and the migration was getting applied, successfully, except that it wasn't being run (silently failing).

This was pretty bad and took a while for me to fix.

We should likely have stricter parsing of the syntax, if this can silently fail

Describe the bug
Currently the options are not mentioned in the docs but shown in the CLI.
See https://github.com/seppevs/migrate-mongo/blob/master/bin/migrate-mongo.js#L45

To Reproduce
Run migrate-mongo --help

Usage: migrate-mongo [options] [command]

Options:
  -V, --version                   output the version number
  -h, --help                      output usag

The logs are constantly telling me the source is consistent, the show_status command that they are inconsistent:

In pg_lib.py,
check_source_consistent method currently reads:
(pseudo code):
if source_consistent:
if source_consistent[0]:
(update t_replica_tables ...)
log(consistent)
else:
log(inconsistent)
else:
log(consistent)

Line 3306 o

The case "up should deprecate object models of previous versions" fails to throw SQLException as expected.

The problem is caused by Slick 3.1.0 and SQLite. See more in: slick/slick#1402

A client defined a schema as CUBE and REF.

In schemacrawler, this comes back as "CUBE" or "REF", which our code isn't handling (note
SchemaCrawler.java:426 and SchemaRetriever:181)

Hey. I'm looking for a lightweight database migration tool and found this project through the Slick documentation. It seems to be up-to-date and the example looks intriguing. I was wondering if it is a good fit for my project and started reading the source code. That helped my understanding a bit, but the "big picture" is still quite blurry.

I'd like to read some high-level documentation, like

This is a (multiple allowed):

• bug

Using latest phinx 0.11.4

• CakePHP Version: 3.8.9
• Database server Postgres: 12.1
• PHP Version: 7.4
• Platform / OS: docker bref php

What you did

(This is pulled from an issue card created on phinx, I was directed to post the issue here.)

I use postgres with multiple schemas in one dat

The only two changes that are needed are:

Adding an S3 resolvers in project/project/plugin.sbt

addSbtPlugin("com.frugalmechanic" % "fm-sbt-s3-resolver" % "0.14.0")

Excluding the Community Edition flyway-core artifact in project/plugin.sbt and replacing it with the desired edition which will be downloaded from our private repo:

Pro:

s3CredentialsProvider