sqlite3 messes up between environments (ELF headers)

[javorszky]

So the binaries for sqlite are awesome, however, look at this gif right here:

This happens after database is modified in macos. Sqlite in vagrant then can't read it for some weird reason.

[javorszky]

Also, my database seems to have been wiped. At least there was no user, and I'm sure haven't trashed it.

[ErisDS]

sqlite3 is a native application. It will only work on the environment you compile it on.

I use vagrant and macos as well, and sometimes switch environments - I see the same thing you do, I have to recompile sqlite by running npm install sqlite3.

Your databases should not have been wiped. If this has definitely happened - check the contents, please try to reproduce how it happened and raise that as an issue?

[springmeyer]

@ErisDS - sqlite3 not sqlite. Also npm install sqlite3 works but even better to recommend is npm rebuild which will hunt down all modules with a binding.gyp and re-run their install commands. In the case of sqlite3 it will install the right binary.

[ErisDS]

@springmeyer thanks! I've updated my typo. This is only something encountered by developers running vagrant and so sharing their ghost between 2 environments.

[springmeyer]

@ErisDS sounds good.