Opened 14 years ago

Closed 12 years ago

#11004 closed Bug (fixed)

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

Reported by: Erik Allik Owned by: elbarto
Component: Core (Cache system) Version: dev
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


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).

Change History (7)

comment:1 Changed 14 years ago by Russell Keith-Magee

milestone: 1.1

comment:2 Changed 14 years ago by Alex Gaynor

Triage Stage: UnreviewedAccepted

comment:3 Changed 12 years ago by Julien Phalip

Severity: Normal
Type: Bug

comment:4 Changed 12 years ago by gerdemb

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

comment:5 Changed 12 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 12 years ago by elbarto

Owner: changed from nobody to elbarto

comment:7 Changed 12 years ago by elbarto

Resolution: fixed
Status: newclosed

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

Note: See TracTickets for help on using tickets.
Back to Top