Code

Opened 5 years ago

Closed 2 years ago

#11004 closed Bug (fixed)

cache.set should raise an exception when key is too long

Reported by: RaceCondition Owned by: elbarto
Component: Core (Cache system) Version: master
Severity: Normal Keywords:
Cc: gerdemb Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

At least when using DB caching, the maximum allowed cache key length is 255 because the cache table is created that way. But when cache.set() is not currently aware of this and when caching a value using a key longer than 255 characters, a database error is thrown (which, at least in the case of Postgres, is not very clear about the reason).

Attachments (0)

Change History (7)

comment:1 Changed 5 years ago by russellm

  • milestone 1.1 deleted
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

comment:2 Changed 5 years ago by Alex

  • Triage Stage changed from Unreviewed to Accepted

comment:3 Changed 3 years ago by julien

  • Severity set to Normal
  • Type set to Bug

comment:4 Changed 3 years ago by gerdemb

  • Cc gerdemb added
  • Easy pickings unset
  • UI/UX unset

comment:5 Changed 3 years ago by gerdemb

Not sure why my adding myself to the CC list also unset "UI/UX" and "Easy pickings". This bug does seem like pretty easy pickings though....

comment:6 Changed 2 years ago by elbarto

  • Owner changed from nobody to elbarto

comment:7 Changed 2 years ago by elbarto

  • Resolution set to fixed
  • Status changed from new to closed

This ticket is obsolete: this problem was solved in r13767.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.