View Single Post
  #4  
Old 07-06-2016, 07:42 PM
fzzzty
Fire Beetle
 
Join Date: Aug 2010
Posts: 23
Default

It's in 2014_12_26, it alters a misspelled column name and updates a view to use them, however that view doesn't exist, and the columns have been fixed in the PEQ DB (I dunno when that happened). I'm testing in a branch that disables that update and will do a pull req if it all works (I don't expect it not to), but I wasn't sure if it would cause issues elsewhere not having that view.

The PEQ files include a source_views.sql file with that view in it, but it seems to be old and also uses the misspelled column names, and their readme says it isn't used...

Edit: Here is a link

Edit 2: I got on this path because that DROP VIEW line errors out for me, however the entire migration is basically irrelevant now that it's fixed in the PEQ file, as far as I can tell.
Reply With Quote