[wp-trac] [WordPress Trac] #16296: Transient API key length could result in uncacheable data

[WordPress Trac]

#16296: Transient API key length could result in uncacheable data
--------------------------+------------------------------
 Reporter:  archon810     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Database      |     Version:  3.0.4
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+------------------------------
Changes (by solarissmoke):

 * keywords:  transient, caching => dev-feedback
 * component:  Cache => Database


Comment:

 Replying to [ticket:16296 archon810]:
 > Specifically, the transient timeout key was longer due to the presence
 of the word "timeout" in it and was running into the MySQL key length
 limit of 64 characters, getting silently truncated.

 Doesn't get truncated - WP_DB just bails and issues an error notice:

 {{{
 WordPress database error Data too long for column 'option_name' at row 1
 for query INSERT INTO `wp_options`...
 }}}

 and `set_transient()` also returns `false` telling you that something went
 wrong. IMHO this is sufficient warning? We can't truncate keys because the
 user will still be looking for they key they asked to set.

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