Skip to content
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

scripts in db/migrate appear to use mysql syntax but Readme.MD refers to Postgres #34

Open
nzrower opened this issue Jun 12, 2019 · 2 comments

Comments

@nzrower
Copy link

nzrower commented Jun 12, 2019

scripts in db/migrate appear to use mysql syntax but Readme.MD refers to Postgres

@nzrower
Copy link
Author

nzrower commented Jun 13, 2019

I don't know how the one time initial setup works in detail, but it appears to behave differently if there are .json files in secrets folder vs there not being there.

When I deleted the offending msql db scripts in folder db/migrate and also had no files in secrets folder I got the sever to run by go run server.go

Leaving issue open to see if the primary authors who know what was intended for this have ideas for improving this.

@kennygrant
Copy link
Owner

The scripts in db/migrate use standard sql where possible, the problem is that the migrate command calls the psql binary to run the migrations. Thus at the moment it is limited to use with postgresql unless you want to run migrations yourself. See fragmenta/migrate.go. So that's why psql is mentioned.

Not really an issue if you're fine running the sql yourself against your db.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants