Bug 1314519 - Specify string column limits
Summary: Specify string column limits
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 20:00 UTC by Partha Aji
Modified: 2019-09-25 21:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 09:25:25 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1501 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 12:28:58 UTC
Foreman Issue Tracker 14025 None None None 2016-04-22 16:50:56 UTC

Description Partha Aji 2016-03-03 20:00:30 UTC
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.

Comment 1 Partha Aji 2016-03-03 20:00:32 UTC
Created from redmine issue http://projects.theforeman.org/issues/14025

Comment 2 Partha Aji 2016-03-03 20:00:35 UTC
Upstream bug assigned to daviddavis@redhat.com

Comment 4 Bryan Kearney 2016-03-03 21:11:30 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14025 has been closed
-------------
David Davis
Applied in changeset commit:katello|924700524dd6990d447030dcfb92caed0c28c3f2.

Comment 6 Kedar Bidarkar 2016-05-25 15:58:07 UTC
Please provide verification steps to test this.

Comment 7 David Davis 2016-05-28 21:39:48 UTC
Try entering a value longer than 255 chars for one of these fields:

https://github.com/Katello/katello/pull/5837/files

It must be a new install. A few example fields include activation key name, content view name, lifecycle environment name, etc

Comment 8 jcallaha 2016-06-16 14:13:51 UTC
Verified in Satellite 6.2 beta Snap 15.2

Forms accepting string input are correctly performing string length validation.

Comment 10 errata-xmlrpc 2016-07-27 09:25:25 UTC
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.

https://access.redhat.com/errata/RHBA-2016:1501


Note You need to log in before you can comment on or make changes to this bug.