Describe the bug
It looks like for Postgres, using for example table.string("foo", 36).change() in a migration results in the column taking on a varchar field without any length specified. This seems to be due to the what is mentioned in this issue's title.
Expected behavior
Migrating a table to change a column should add the appropriate string length. Compare this to MySQLPlatform.py, for example.
Describe the bug It looks like for Postgres, using for example
table.string("foo", 36).change()
in a migration results in the column taking on avarchar
field without any length specified. This seems to be due to the what is mentioned in this issue's title.Expected behavior Migrating a table to change a column should add the appropriate string length. Compare this to
MySQLPlatform.py
, for example.