Code

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#9706 closed (fixed)

Oracle Slugfield hardcoded to 50 chars

Reported by: elealty Owned by: nobody
Component: Database layer (models, ORM) Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation:
Needs tests: Patch needs improvement:
Easy pickings: UI/UX:

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.

Attachments (0)

Change History (2)

comment:1 Changed 5 years ago by ikelly

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

(In [9548]) Fixed #9706: made SlugField honor max_length in Oracle, matching the other backends.

comment:2 Changed 5 years ago by ikelly

(In [9549]) [1.0.X] Fixed #9706: made SlugField honor max_length in Oracle, matching the other backends. Backport of [9548] from trunk.

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.