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

Sqlite fails when custom sqliterc exists #66

Open
sandro opened this issue Dec 19, 2020 · 3 comments
Open

Sqlite fails when custom sqliterc exists #66

sandro opened this issue Dec 19, 2020 · 3 comments
Labels

Comments

@sandro
Copy link

sandro commented Dec 19, 2020

Hi, I was having a difficult time getting the tool to work until I realized that my personal ~/.sqliterc file was causing grep to fail in the shmig script. So if you're having issues that look like the following:

➜ shmig status
shmig: creating migrations table: shmig_version
Error: near line 1: table `shmig_version` already exists

Try adding this to your shmig.conf to reset sqlite3 to its default client mode.

ARGS="-list -noheader"

or use -a "-list -noheader" on the command line.

For reference, my .sqliterc is as follows:

.headers on
.mode line
@mbucc mbucc added the bug label Dec 20, 2020
@mbucc
Copy link
Owner

mbucc commented Dec 20, 2020

Marked this as a bug; this should be the default behavior.

@sandro
Copy link
Author

sandro commented Dec 20, 2020

That's great, I didn't want to impose with a PR but good to hear it'll be a default, thank you!

This is a very cool tool, love the concept, thanks for sharing it.

@mbucc
Copy link
Owner

mbucc commented Dec 20, 2020

Thanks for the detailed report, and glad you find it useful.

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

No branches or pull requests

2 participants