#9706 closed (fixed)
Oracle Slugfield hardcoded to 50 chars
| Reported by: | Eleonora Altana | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This has been noted a few months ago (see comments in #3588), but in trunk the situation is still the same: in the Oracle backend, slug field is created as a NVARCHAR2(50) column.
max_lenght should be onored, as in the char field.
Change History (2)
comment:1 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 16 years ago
Note:
See TracTickets
for help on using tickets.
(In [9548]) Fixed #9706: made SlugField honor max_length in Oracle, matching the other backends.