Red Hat Bugzilla – Bug 1314519
Specify string column limits
Last modified: 2016-07-27 05:25:25 EDT
In Rails 4.2 the default limit for PostgreSQL and SQLite adapters
changes to unlimited from 255 characters. MySQL remains at 255 chars.
Existing migrations should be changed to specify the length, e.g.
t.column :name, :string, :null => false, :limit => 255
This will ensure that the schema generated on a new installation exactly
matches the schema from an old installation, so there won't be varying
versions of the schema in the wild.
Created from redmine issue http://projects.theforeman.org/issues/14025
Upstream bug assigned to email@example.com
Moving to POST since upstream bug http://projects.theforeman.org/issues/14025 has been closed
Applied in changeset commit:katello|924700524dd6990d447030dcfb92caed0c28c3f2.
Please provide verification steps to test this.
Try entering a value longer than 255 chars for one of these fields:
It must be a new install. A few example fields include activation key name, content view name, lifecycle environment name, etc
Verified in Satellite 6.2 beta Snap 15.2
Forms accepting string input are correctly performing string length validation.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.