[wp-trac] [WordPress Trac] #15058: Validate option and transient name lengths

[WordPress Trac]

#15058: Validate option and transient name lengths
----------------------------------------+-----------------------------
 Reporter:  chrisbliss18                |       Owner:
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  Future Release
Component:  Validation                  |     Version:  3.1
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |
----------------------------------------+-----------------------------

Comment (by chrisbliss18):

 Replying to [comment:21 sc0ttkclark]:
 > Pushing to 256 is great, but still doesn't resolve things when the
 transient key is too long. Why it'd be that long, not sure, but the MD5
 solution is the most versatile to support that, column change or not. I
 believe object caching, when it takes over transients etc, has a charcter
 limit of around 250, give or take a few, depending on what's running it.
 When it hits that limit, it truncates the key.
 >
 > I think md5, which could be increased to a higher limit before it runs
 if option_name ever is expanded, is the best bet here for expanding the
 expected functionality of transients etc.

 I agree that having a solution where "it just works" is ideal. Were you
 able to put together a patch?

 At a minimum, I want it to always work reliably or to return an error and
 generate a notice when a problem will occur. As it is now, we don't get an
 error and it doesn't work, so it is a very bad flaw currently.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/15058#comment:22>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software