Opened 16 years ago
Closed 13 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 |
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).
Change History (7)
comment:1 by , 16 years ago
| milestone: | 1.1 |
|---|
comment:2 by , 15 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 14 years ago
| Severity: | → Normal |
|---|---|
| Type: | → Bug |
comment:4 by , 13 years ago
| Cc: | added |
|---|---|
| Easy pickings: | unset |
| UI/UX: | unset |
comment:5 by , 13 years ago
comment:6 by , 13 years ago
| Owner: | changed from to |
|---|
comment:7 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This ticket is obsolete: this problem was solved in r13767.
Note:
See TracTickets
for help on using tickets.
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....