You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated from hydra 1.0.0 to 1.0.1 with a fresh development install but the "migrate sql" command failed to create all needed database schemas - does anyone encounter the same problem?
Using docker-compose starting up a mysql 5.7 instance und using docker environment var for DSN key
the problem occurs during parse operation of the DSN
error output:
time="2019-09-17T08:36:49Z" level=info msg="Establishing connection with SQL database backend" dsn="root:secret@tcp(mysqld:3306)/mysql?parseTime=true://*:*@tcp(mysqld:3306)/mysql?parseTime=true"
time="2019-09-17T08:36:49Z" level=info msg="Successfully connected to SQL database backend" dsn="root:secret@tcp(mysqld:3306)/mysql?parseTime=true://*:*@tcp(mysqld:3306)/mysql?parseTime=true"
Got dsn: mysql://root:secret@tcp(mysqld:3306)/mysql?max_conns=20&max_idle_conns=4Usage:
hydra migrate sql <database-url> [flags]
Flags:
-h, --help help for sql
-e, --read-from-env If set, reads the database connection string from the environment variable DSN or config file key dsn.
-y, --yes If set all confirmation requests are accepted without user interaction.
Global Flags:
--config string Config file (default is $HOME/.hydra.yaml)
--skip-tls-verify Foolishly accept TLS certificates signed by unkown certificate authorities
parse mysql://root:secret@tcp(mysqld:3306)/mysql?max_conns=20&max_idle_conns=4: invalid port ":3306)" after host
The text was updated successfully, but these errors were encountered:
I updated from hydra 1.0.0 to 1.0.1 with a fresh development install but the "migrate sql" command failed to create all needed database schemas - does anyone encounter the same problem?
Using docker-compose starting up a mysql 5.7 instance und using docker environment var for DSN key
the problem occurs during parse operation of the DSN
error output:
The text was updated successfully, but these errors were encountered: