You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: error processing migrations/20180627164200_back_quotes.up.fizz: could not fizz the migration migrations/20180627164200_back_quotes.up.fizz: line 11: no prefix parse function for ILLEGAL found
line 11: expected next token to be ), got IDENT instead
line 12: no prefix parse function for ILLEGAL found
line 12: expected next token to be ), got IDENT instead
line 12: no prefix parse function for ILLEGAL found
line 12: no prefix parse function for ILLEGAL found
line 12: no prefix parse function for , found
line 12: no prefix parse function for ILLEGAL found
line 12: no prefix parse function for ILLEGAL found
line 12: no prefix parse function for , found
line 12: no prefix parse function for , found
line 12: no prefix parse function for , found
line 12: no prefix parse function for ) found
line 13: no prefix parse function for ILLEGAL found
line 14: no prefix parse function for ) found
While this was valid in v4.5.10 and before.
The text was updated successfully, but these errors were encountered:
Updated issue comment with Postgres-specific extension installation so uuid_generate_v1() exists on a clean install.
That update causes an error:
error processing migrations/20180627164200_back_quotes.up.fizz: could not fizz the migration migrations/20180627164200_back_quotes.up.fizz: line 1: expected next token to be ), got IDENT instead
line 2: no prefix parse function for ) found
Example migration file:
20180627164200_back_quotes.up.fizz
Produces the output:
While this was valid in v4.5.10 and before.
The text was updated successfully, but these errors were encountered: