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
It's common to use text in an AR migration to define a wide column that contains many characters. Redshift does not support a text datatype, but it does support varchar up to 65535. Therefore, we should change the definition of text in a migration to generate VARCHAR(65535) instead of VARCHAR(255), which what happens now and likely surprising behavior.
I'm up in the air if we want to throw some sort of warning about this. A 64k wide column probably isn't what you actually want, but you likely want something bigger than 255.
The text was updated successfully, but these errors were encountered:
It's common to use
text
in an AR migration to define a wide column that contains many characters. Redshift does not support atext
datatype, but it does support varchar up to 65535. Therefore, we should change the definition oftext
in a migration to generate VARCHAR(65535) instead of VARCHAR(255), which what happens now and likely surprising behavior.I'm up in the air if we want to throw some sort of warning about this. A 64k wide column probably isn't what you actually want, but you likely want something bigger than 255.
The text was updated successfully, but these errors were encountered: