[wp-trac] [WordPress Trac] #13310: Extend option_name to varchar(255)

WordPress Trac noreply at wordpress.org
Tue Nov 25 16:23:10 UTC 2014


#13310: Extend option_name to varchar(255)
---------------------------------------------+-----------------------------
 Reporter:  scribu                           |       Owner:
     Type:  defect (bug)                     |      Status:  assigned
 Priority:  normal                           |   Milestone:  Future Release
Component:  Database                         |     Version:  3.4.2
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch 2nd-opinion 4.1-early  |     Focuses:
---------------------------------------------+-----------------------------

Comment (by nerrad):

 Replying to [comment:44 Hube2]:
 > I really think that transients and putting in a new table is a
 completely separate discussion.

 Yeah true, however with the lack of traction that has gone on for this
 "simple" schema change maybe there's other things that should be done that
 will resolve the existing issue.

 Either way, there really should be some feedback as to:

 1. Why this has been lingering for 5 years (yeah network install WP sites
 is the given reason... but why?)
 2. It's looking like this will NOT go in 4.1 because of where we are in
 the 4.1 release cycle... if not WHY? (which will likely lead to the answer
 for number 1.

 So really, if a simple schema change is really not being considered.

 1. What needs to change to make it considered?
 2. Do we need to evaluate whether using the options table for transients
 is what exposed this problem to begin with.  And if so, maybe that reveals
 the need for something different to be done for transients (which would
 yes warrant another ticket likely and then CLOSING this ticket that is
 getting no action).
 3. OR as I also suggested, would adding a timestamp column to the options
 table and introducing a change for transients to use one row instead of
 two be a good interim measure both to incrementally fix the issue raised
 by this ticket and satisfy the holdup for making a "simple" schema change
 on an existing column?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/13310#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list