adapted the sqlite driver for v3 (#165)

[maxvw]

When I discovered your project I thought it was perfect, just what I needed! However soon after that I discovered the latest version lacked SQLite support. So I've copied the Ql driver and adapted it to work for SQLite, I think I've covered everything but if I forgot something please let me know!

I wasn't sure which naming convention to use, in the previous version I see it was called sqlite3 but in the new version there was a directory reserved called sqlite. I've opted for the sqlite3 naming as the actual driver is also called sqlite3 so I think that made more sense.

[coveralls]

Coverage increased (+1.6%) to 60.128% when pulling 8b4ce58 on maxvw:v3-sqlite into 3682bcf on mattes:master.

[coveralls]

Coverage increased (+1.6%) to 60.128% when pulling 8b4ce58 on maxvw:v3-sqlite into 3682bcf on mattes:master.

[bt]

Hey @mattes, I desperately need this functionality. Could you please merge this PR in?

Thank you! 😄

[mattes]

can you add the build file (ex https://github.com/mattes/migrate/blob/master/cli/build_ql.go) for this driver, please?

thanks for the PR! will merge after this!

[coveralls]

Coverage increased (+1.6%) to 60.128% when pulling decee4a on maxvw:v3-sqlite into 3682bcf on mattes:master.

[coveralls]

Coverage increased (+1.6%) to 60.128% when pulling decee4a on maxvw:v3-sqlite into 3682bcf on mattes:master.

[maxvw]

@mattes done, that should work now too.

(I had completely overlooked it as I only use the functionality in Go itself, not the command-line version)

[mattes]

merged! thank you so much!

[mattes]

@maxvw I see some errors: https://travis-ci.org/mattes/migrate/jobs/239468284#L1513 Any idea what's going on?

[maxvw]

@mattes on first inspection this seems to be due to the fact that go-sqlite3 is a cgo package, I'm still relatively new to Go and didn't know this was a thing / wasn't aware of the impact that has when it comes to cross-compiling. I'm not sure what the fix would be to make this work right now, from initial reading it sounds like you need to set the correct CC env for each GOOS and also set CGO_ENABLED=1.

Someone mentioning a similar issue: mattn/go-sqlite3#384

But if it makes cross-compiling more challenging people will also have this issue in their own project if they include the migrate library, right? So the question is if that's desired or not. I have not found a better sqlite3 go package unfortunately (this is also the same one you originally used in v1)

[mattes]

ok, thanks! I just enabled CGO based on: mattn/go-sqlite3@98981b4

[maxvw]

@mattes alright nice, hopefully that solves it!