Closed gregswift closed 6 years ago
Looks like it's only a matter of changing the last CREATE CUSTOM INDEX
to CREATE CUSTOM INDEX IF NOT EXISTS
Schema updates should be supported, it just so happens that we had none yet, so, there's only the v001.sql
file.
By the way, would you be willing to contribute with a PR?
There ya go
Hi. We just updated to 1.2 of this project... which was super easy btw :D As we updated things we also updated the job to the 1.2 version. The job ran again and got this output:
Generally things seem to be fine so I dont see this as currently beign a problem. But we figured we'd bring it up since schema changing might happen in the future.
Steps we followed to update: